REPORT COM == -}= = ] = =  = =  m = =  = = M }= X 2 e H   # + 3 5 8 9 D U S a e e  3; ) IzzIzzI66l HHl HHl KK"^^"^^"aa%zz%zz%}}')*,*0/3c2553HH36}};8__lAXXB966!HH!HH!KK$^^$^^$aaI&zzI&zzI&EFGJj|^ J LPRMP)W\rX`U#Y]d[ze[\g\\Q ),.0?OS~,!.8EGZgi7breh<Km!npnnnkjm;oo pSpσ ppq`sbsstdtwu'vvEwhxyzHzz&{r{{1||CHXmϘ|"}}}B~~~$8>EK_oxǙЙ 5EZ\q2pN8fŠNȋ8_%Y?͎VʏK 0i:ޒ9jĕ:DTAFT1C-N+P'".NYEAIOFCISR-ABCDEFGHIJKLMNOP?NS_00-- SINENNF0?0??0   *.1234567899PRRP123456789 :CURSOR: ^A=left item ^S=left char ^D=right char ^F=right item ^E=up line ^X=down line ^U=set/clear tab ^I=tab DELETE: DEL=char left ^G=char right ^T=entire column ^Y=entire line INSERT: ^P=line buffer ^V=char right ^B=entire column ^N=entire line OTHER: ^J=rotate help ^W=list form ^C=form done ^K=control break FIELD: ^Q,_=add/extend field ^Z=delete field ^R=define field OTHER: ^J=rotate help ^W=list form ^C=form done ^O=toggle ^ char CURSOR: RETURN=next item ^S=left char ^D=right char ^E=prev item OTHER: ^A=previous field ^F=next field ^G=delete char ^V=insert char ^C=end definition ^R=start over ^Q=locate field ^J=more help OTHER: ^A=previous line ^F=next line ^G=delete char ^V=insert char ^C=end definition ^Q=locate line ^J=more help OTHER: ^A=previous file ^F=next file ^G=delete char ^V=insert char ^C=end definition ^R=start over ^T=top of page ^J=more help OTHER: ^G=delete char ^V=insert char CURSOR: ^E=up line ^S=left char ^D=right char ^X=down line PRINT CNTL: SPACE=always print P=once/page R=once/report :=summaries only 1-9=print at control break n .=non-printing *=user defined _______________________________________________________________________________ LIN=001 CHR=001 HELP SCREEN # LIN=001 CHR=001 NUM=000 LEN=000 POS=000 EDC=xxCTL.AND..OR.<><=>=<>=&+-*/^(),< < F I E L D D E F I N I T I O N > > press ^J for help on any item Field number/name:'Equivalent to field:'Control break level:'Copy attributes of field:'Field source: (File/Calc/Input)' File number/name:' Field number/name:' Index field number/name:' Numeric/String? (N/S)' Enter string expression:  Enter algebraic expression:  UNLESS THEN  Enter input prompt: Right justified? (Y/N)'Enter pad character:'Edit mask? (Y/N)'Edit Mask Condition Codes: F = float character position'T = trail character position 1 = float if first in column'C = trail if first in column - = float if negative'N = trail if negative + = float if positive'P = trail if positive ' = constant if data on one side'" = constant if data on both sides _ = constant or field data'. = decimal alignment position This mask defines positions only: floating, constant or decimal alignment. The next mask provides the actual characters to be used at each position. Enter the edit mask condition codes:This second edit mask is used to define the actual constants that will appear if the conditions of the first mask are met. When these conditions are satisfied, one character will appear in the field for every constant character in the mask. Combinations of floating characters may be used here; for example the characters "CR" used as constants in this mask with a corrsponding "NN" in the previous mask will print a CR after negative quantities. Enter the edit mask constants: When should the field be loaded with a new value: = always R = only at report start P = at each new page 1-9 = after control break * = when the following expression is satisfied Enter load condition ( /R/P/n/*): Enter expression for field load: LOAD WHEN Output field to file? (Y/N)' When should the field be cleared: = always . = never P = at each new page 1-9 = after control break * = when the following expression is satisfied Enter field clear condition ( /./P/n/*): Enter expression for clearing the field: CLEAR IF This part of the program defines file usage. (^J = more help at any item) Enter the number of the next file to define or review:  This part of the program defines file usage. (^J = more help at any item) Enter the name of the associated definition file:  On which disk drive is the definition file located? (-/A/B...)?Access datafile in Sequence or as Reference file? (S/R)? Enter the condition(s) for record inclusion: INCLUDE IF Will the file include more than one volume? (Y/N)?How large should the disk buffer be??Will the datafile name(s) be entered at run time? (Y/N)? Enter the datafile name(s): Disk drive: (?/-/A/B...) File name: 2.9Change disks? (Y/N) Is the file going to be used for Input or Output? (I/O)?Should the file be read in index order? (Y/N)?Error if old version present or Add to it? (E/A)?Should an index file also be written?? < < F I L E D E S C R I P T I O N > > Access: If file exists: No. of buffers: Volume name: OPERATOR ENTERED, MULTI-VOLUMEVolume name:., CHANGE DISKSInclude if: Location: Line= Column= Length=Equivalent to: Control break level: Source:File="Field=Index=CALCULATED = Unless: Then: OPERATOR INPUTPrompt: RIGHT JUSTIFY Editing: EDIT MASKLoad if: Output: If: Clear if:  Enter the condition(s) under which this line should be printed: PRINT WHEN Print line  when Enter the condition(s) for a new page: PAGE WHEN Enter the condition(s) ending the report: END WHEN PAGE WHEN END WHEN < < D E F I N E C O N D I T I O N S > >You have entered the field definition phase by typing a ^R. The <2300> field definition phase is a questionaire which allows you to define how field information is to be derived and processed. In the questions that follow, the answers you give will apply to the current field only. To return to report layout definition, type ^C. This item allows you to specify the order in which fields will be processed during the report generation.This item is used to save time when entering field attributes. If <2330> another field is defined similarly, entering its field number here will cause its attributes to be used by this field also. CAUTION: If you answer Y here and you have already entered a definition for this field, it will be replaced by the new definition.Report field data may be read from a file, calculated from other <2340> fields in the report or entered by the operator. Decide how the data for this field is to be obtained and enter an F, C or I here.Files may be specified by name or number. In order to accept the <2341> entry, REDIT must recognize the name or number, i.e. there must be a file with that name or number in the list of defined files. Enter the name or number of a file that has already been defined or enter ^C^C^F to create a new file definition.Files may be specified by name or number. In order to accept the <2371> entry, REDIT must recognize the name or number, i.e. there must be a file with that name or number in the list of defined files. Enter the name or number of a file that has already been defined or enter ^C^C^F to create a new file definition.Fields may be specified only after the file has been specified. A <2342> field may be selected by number or name if it has been given a name (using FORMGEN) and the form definition file has been successfully read into memory; otherwise only the field number can be used.Fields may be specified only after the file has been specified. A <2372> field may be selected by number or name if it has been given a name (using FORMGEN) and the form definition file has been successfully read into memory; otherwise only the field number can be used.To retrieve data from a reference file, one field in the report must <2343> hold a key value of the file being searched. The report field which holds the key value is called the index field. Enter the name or number of the field in the report to use as an index to the file in selecting records.To update data from a reference file, one field in the report must <2373> hold a key value of the file being accessed. The report field which holds the key value is called the index field. Enter the name or number of the field in the report to use as an index to the file in selecting records for update.A numeric calculated field uses an algebraic expression to derive a <2344> value for the field. The algebraic expression consists of fields, functions and numeric constants combined using the operations: add(+), subtract(-), multiply(*), divide(/), exponentiation(^) A string expression consists of fields, sub-fields and string constants combined using the join(&) operation.A string expression may contain fields, subfields or constants. <2346> Fields are represented by field name or number preceded by "$": $7 Subfields are used to extract a portion of a field. The form is: $field (first character position, number of characters): $7(1,2) Constants are represented by characters enclosed in quotes("): "A01" The expression, $6(1,2) & $7(3,1), combines the first two characters of field 6 with the third character of field 7.An algebraic expression may contain fields, functions and constants <2345> combined with the arithmetic operations: add(+), subtract(-), multiply(*), divide(/) and exponentiation(^). Operations are performed from left to right with parentheses recognized. Fields are represented by name or by field number preceded by a # sign: #7 Constants may contain a decimal point and/or a leading minus: 1.23, -1.005 Recognized functions are: ABS, INT, MAX, MIN, REM, PAGE, FLDThe UNLESS expression provides the facility to omit the calculation <2348> in the line above it. If the UNLESS expression is true, the field value will be determined using the THEN expression (entered next). If the UNLESS expression is false or not entered, the field value will be determined using the expression in the line above it. If multiple UNLESS clauses are present, the field will be calculated using the expression immediately preceding the first missing or false UNLESS. The UNLESS expression must be a comparison of two values. The values compared may be fields, sub-fields, numeric constants, functions, character strings or arithmetic/string expressions. The following comparisons can be made: less than [<] less than or equal to [<=] equal to [=] not equal to [<>] greater than [>] greater than or equal [>=] Examples of comparisons are: $MONTH = "JANUARY" DAY = 1 Comparisons can be combined using the logical operators: .AND. and .OR.The input prompt is a message that will be displayed to the report <2347> program operator so that he/she knows what entry is required. Any message that will fit on a single line can be used. It will be displayed to the report program operator at the top of the screen. The cursor will blink back and forth between the message and the field to be entered.Right/left justification determines on which side of the field the <2351> data will be placed when it does not fill the field. A Y answer will align the field data with the right side of the field.Pad characters are used to fill the field when there aren't enough <2350> data characters to fill it. Any character can be used; the usual choice is the space character.An edit mask allows you to add fixed and floating characters to the <2352> data characters in the field and set a decimal alignment position. Fixed characters occupy fixed positions in the field; floating characters are characters whose position varies depending on how many data characters there are in the field. Decimal alignment is lining up data for output at the decimal point. You cannot put a non-integral calculated value into a field unless it has a decimal alignment position. A Y answer will allow you to enter an edit mask in two steps: positions/conditions and constants.The float codes are used to put character(s) in front of the data; <2353> the trail codes after the data. The codes for constants will insert characters at fixed positions into the data. Decimal alignment overrides right/left justification, putting data into the fields with decimal points aligned at that position. To use the float and trail codes, put one at every position in the field that the floating characters defined in the next mask may occupy. Some examples are: FFFFF, 11_.__NN, FFFF"FF_.__, ---"--_NCharacters that you want to float or trail must be put at the start <2354> or end of positions defined as floating/trailing in the first mask. Fixed characters and the decimal alignment character must be put at the constant and decimal alignment position. Some examples of mask combinations: FFFFF 11_.__NN FFFF"FF_.__ ---"--_N $____ $__.__CR $___,___.__ <__,___>The data generated for this field can be written to a file instead <2370> of or in addition to printing it. This feature can be used to make multiple reports, write audit trails, create data files for other programs, etc. If you choose to output this field, the next few questions will allow you to specify to which file and field the data should be written.Field names are optional. If a field name is entered here, then all <2300> references to this field will use the name as well as the number. A field name must start with a letter. The remaining characters may be letters, numbers, or spaces.Equivalent fields are used only in reports that read more than one <2310> record from a file as the report form is filled out. An example of this is telephone directories which list names and phone numbers in four columns. Assigning equivalence signals the report program that a new record must be read for each set of equivalent fields. To make this field equivalent to a field previously defined, enter the number of the field in the report that is appropriately defined. The field definition will be over for this field and any attributes previously assigned to this field will be lost.This field is a control break field. Control breaks are used to <2320> produce report summary lines and other special effects. This is done by specifying elsewhere in the report what should be done whenever the value of this (or any other control break) field changes. Notice that for this to actually produce summary lines, the input file(s) must be sorted in control break field order, so that when the value of a control break field changes, it is an appropriate time for a summary. Up to nine fields may be used for control breaks. These are given a number called the control break level, such that level 1 is most important and 9 is least important in the sort order. This allows nested summaries such as city (2) within state (1).The load condition specifies how often new values should be entered <2360> into the field. A load condition can be used when a field value is relatively constant or when the field is not on a report detail line (CTL character = space). Using the load condition can speed up report processing. In addition, using the "R" load condition enables the field to be used in an INCLUDE IF expression.The LOAD WHEN expression specifies the conditions under which this <2360> field should be loaded. The expression must be a comparison of two values. The values compared may be fields, sub-fields, numeric constants, functions, character strings or arithmetic expressions. The following comparisons can be made: less than [<] less than or equal to [<=] equal to [=] not equal to [<>] greater than [>] greater than or equal [>=] Examples of comparisons are: $MONTH = "JANUARY" DAY = 1 Comparisons can be combined using the logical operators: .AND. and .OR. An example of combining comparisons is: LOAD WHEN $MONTH="JANUARY" .AND. DAY=1 to load the field with a new value only on the first day of the year.Normally, fields are not cleared during processing. This is of no <2380> consequence since each pass will generate new field values. However, in order to produce counts and accumulated totals for summaries, you must clear the field at a new page or control break. Select one of the clear conditions if this field is a count or total field.The CLEAR IF expression specifies the conditions under which this <2380> field should be cleared. The expression must be a comparison of two values. The values compared may be fields, sub-fields, numeric constants, functions, character strings or arithmetic expressions. The following comparisons can be made: less than [<] less than or equal to [<=] equal to [=] not equal to [<>] greater than [>] greater than or equal [>=] Examples of comparisons are: $MONTH = "JANUARY" DAY = 1 Comparisons can be combined using the logical operators: .AND. and .OR. An example of combining comparisons is: CLEAR IF $MONTH="JANUARY" .AND. DAY=1 to clear the field on the first day of the year. Before a file can be used by ReportStar, you must describe how. <2100> These file usage descriptions are entered here, one per file. They are automatically numbered and saved. Enter the number of the next file description you would like to enter or review or press RETURN to accept the number given.The form definition file is read into memory and incorporated into <2110> the report specification at this step. If you change a definition (with the FORMGEN program), the new version should be put into the report specification. This is done by deleting and re-entering the disk drive. Enter the disk drive (A,B,...) where the data definition file is now located. A dash (-) may be used if it is on the logged drive.If your report uses only one file for input, access should usually <2130> be sequential. If it uses more than one file for input, as long as at least one of them is accessed sequentially, the remainder can be accessed either way. The considerations are: All sequential access files must be in the same order for merging to occur. Merging sequential files can be tricky if there are "missing" records in either file. Consult your reference manual if you are going to do this. For large files, reference file access is slower and requires more memory. Reference file access requires an index file.The report program can write files as it makes the report. These <2120> can be transaction summaries, audit trails, data for additional reports, etc.Sequential input files can be read in index file sequence as well <2135> as data file sequence if an index file is available. This saves a sorting step, but is usually slower and uses more memory. For large files, it is faster to sort them with SUPERSORT and read them in datafile sequence.If nothing is entered here, all records will be included. Otherwise, <2160> a LOGICAL EXPRESSION is used to select records for input or output. A logical expression specifies conditions under which a report process should occur. Each condition is expressed as a comparison of two values. An expression may compare the values of fields, sub-fields, numeric constants, functions, character strings or arithmetic expressions. The following comparisons can be made: less than [<] less than or equal to [<=] equal to [=] not equal to [<>] greater than [>] greater than or equal [>=] Examples of comparisons are: AGE > 30 $GENDER = "F" Comparisons can be combined using the logical operators: .AND. and .OR. An example of combining comparisons is INCLUDE IF AGE > 30 .AND. $GENDER = "F" to include only women over the age of 30 in your report or output file.An input file may be in several volumes. All volumes may be on one <2145> disk (each volume having a unique name) or on several disks (each volume having the same or different names). All volumes must use the same form definition file. The REPORT program inputs each volume one at a time, as it is needed. The report program can also create multi-volume output files. The usual reason for doing this is that the file is larger than the capacity of one disk.If the file is one that you want to re-create every time the report <2125> is run, enter E to report the presence of any old version. If you you want to add to the file whenever the report is run enter A.If the file will be accessed later by DATASTAR or used in REPORT <2133> as a reference file, an index file must also be created. If the file will always be read sequentially, the index is unnecessary. Writing an index along with the data is slower than writing just the data. For large files, it will save time to use SUPERSORT to write the index file.Datafile names can be specified now or entered later when the report <2150> is run. A Y answer here will be require that the datafile name be entered every time the report is run. An N answer permits you to enter the datafile name(s) here and have them built into the report specification. This means that the name(s) of the datafile(s) used must always be the same for this report.Specify the disk drive where this datafile will be found when the <2152> report is run. You may enter a question mark (?) to allow the disk drive to be entered at run time.A file name is 1-8 letters or numbers. <2153>A file type is 0-3 letters or numbers. <2154>A Y answer here will cause the report program to ask the operator <2155> to insert the correct diskette into the drive specified. For a single volume file, it is used to remind the operator which drive to use. For multi-volume files, it is the only way to continue the file on the same drive. To use the change diskette message, this must be the only file in use on this drive (including the error log, the message overlay and the print file).Every file description includes information about the structure and <2105> type of data in the file. This information is stored in the form definition file (.DEF) by the FORMGEN program. If there is no form definition file for this file, you must exit and use FORMGEN to create one; otherwise, you may enter its name here. Note that the data file(s) defined here may later be referred to by description number or form definition name. To remove a file description from the report specification, delete all the characters in the definition name.A disk buffer is an area in memory used to hold data while waiting <2140> for it to be used (in the case of input) or written (for output). The number you assign here determines how many 128 sectors of memory will be used for the buffer area. Always use at least 8, unless this does not leave enough memory to run the report. Only the following entries are acceptable: 1, 2, 4, 8, 16 or 32.The PRINT WHEN expression specifies the conditions under which this <2240> line should be printed. The expression must be a comparison of two values. The values compared may be fields, sub-fields, numeric constants, functions, character strings or arithmetic expressions. The following comparisons can be made: less than [<] less than or equal to [<=] equal to [=] not equal to [<>] greater than [>] greater than or equal [>=] Examples of comparisons are: $MONTH = "JANUARY" DAY = 1 Comparisons can be combined using the logical operators: .AND. and .OR. An example of combining comparisons is: PRINT WHEN $MONTH="JANUARY" .AND. DAY=1 to print the line only on the first day of the year.The PAGE WHEN expression specifies the conditions under which a new <2400> page should be started. The expression must be a comparison of two values. The values compared may be fields, sub-fields, numeric constants, functions, character strings or arithmetic expressions. The following comparisons can be made: less than [<] less than or equal to [<=] equal to [=] not equal to [<>] greater than [>] greater than or equal [>=] Examples of comparisons are: $MONTH = "JANUARY" DAY = 1 Comparisons can be combined using the logical operators: .AND. and .OR. An example of combining comparisons is: PAGE WHEN $MONTH="JANUARY" .AND. DAY=1 to start a new page on the first day of each year.The END WHEN expression specifies the conditions under which the <2400> report should be ended. The expression must be a comparison of two values. The values compared may be fields, sub-fields, numeric constants, functions, character strings or arithmetic expressions. The following comparisons can be made: less than [<] less than or equal to [<=] equal to [=] not equal to [<>] greater than [>] greater than or equal [>=] Examples of comparisons are: $MONTH = "JANUARY" DAY = 1 Comparisons can be combined using the logical operators: .AND. and .OR. An example of combining comparisons is: END WHEN $MONTH="JANUARY" .AND. DAY=1 to end the report on the first day of the year. REDIT Release 1.03 ID # 711303KP-00A Copyright (c) 1982, 1984, MicroPro International Corporation. All rights reserved. ay not be copied or distributed in any form or medium, disclosed to third parties, or used in any manner not provided for in aid License Agreement except with prior written authorization from MicroPro.** Error 01 ** .COM is not present on drive  Specify which drive (A-P) to try next:  ** Error 02 ** Cursor is not in a field,  ignored. Press ESC key:  ** Error 03 ** At line limit,  ignored. Press ESC key:  ** Error 04 ** Cannot delete last line. Press ESC key:  ** Error 05 ** At column limit,  ignored. Press ESC key:  ** Error 06 ** Not enough memory,  ignored. Press ESC key:  ** Error 07 ** Possible fatal program error. Please report occurrence,  ignored. Replace system disk, press RETURN:  ** Warning 08 ** Edit mask may need revision. Press ESC key:  ** Error 09 ** The maximum number of fields is 245,  ignored. Press ESC key:  ** Error 10 ** Can't read report specification file. Replace system disk, press RETURN:   < < < P R I N T C O N T R O L C H A R S > > > *Special Effects* | * Special Effects * | * Printing Changes * (begin and end) | (one time each) | ^A Alternate pitch ^B Bold ^D Double | | ^N Standard pitch ^S Underscore | ^H overprint character | ^C Printing pause ^X Strikeout | ^F Phantom space | ^Y Other ribbon color ^V Subscript | ^G Phantom rubout | * User Patches * ^T Superscript | | ^Q, ^W, ^E, ^R ** Error 11 ** Insufficient memory. Replace system disk, press RETURN:  ** Error 12 ** Directory on disk : full. Replace system disk, press RETURN:  ** Error 13 ** Disk : full. Replace system disk, press RETURN:  ** Error 14 ** Illegal string operand. Item must be: a field name starting with $ or field number in the range $001 to $, a sub-field: field name/number followed by "(number,number)", the function $FILE, or a literal enclosed in quotes. Press ESC key:  ** Error 15 ** Illegal string operand. There are no report fields, so item can only be: the function $FILE, or a literal enclosed in quotes. Press ESC key:  ** Error 16 ** Completion of the current command, ^B, will result in a field being split. Is this what you wanted to do? (Y/N)  YNY** Error 17 ** Completion of the current command, ^T, will remove a field byte. Is this what you wanted to do? (Y/N)  YNY** Error 18 ** Illegal operand. Item must be a field number in the range #001 to #, a numeric constant using only digits 0-9 and optional decimal point, one of the functions: ABS, INT, MAX, MIN, REM, PAGE, FLD, ERR, FERR, CB or a recognized field name. Press ESC key:  ** Error 19 ** Illegal operand. There are no report fields, so item must be: a numeric constant using only digits 0-9 and optional decimal point, one of the functions: ABS, INT, MAX, MIN, REM, PAGE, FLD, ERR, FERR, CB or a recognized file field name (INCLUDE IF only). Press ESC key:  ** Error 20 ** Illegal operator. Item must be one of the following:  Press ESC key:  ** Error 21 ** Unclosed left parenthesis. Press ESC key:  ** Error 22 **  - Illegal character. Press ESC key:  ** Error 23 ** The form definition file, , is not present on drive . Do you want to try Another disk drive or Change diskettes? (A/C)  AAC** Error 24 ** Field  already has this name. Press ESC key:  ** Error 25 ** Insert diskette containing  into drive  and press RETURN. ** Error 26 ** The form definition file, , is not present on drive . Press ESC key:  ** Error 27 ** Entry must be a number in the range 001 to . Press ESC key:  ** Error 28 ** The only entry allowed here is 001. Press ESC key:  ** Error 29 ** Can't recognize field name. Press ESC key:  ** Error 30 ** Intermediate fields cannot be used in ReportStar. Press ESC key:  ** Error 31 ** Can't read form definition file. Press ESC key:  ** Error 32 ** You must enter a file description before it can be used. Press ESC key followed by ^C^C^F:  ** Error 33 ** File  already has this name. Press ESC key:  ** Error 34 ** Expression too long. Press ESC key:  ** Error 35 ** Too many/missing function argument(s). Press ESC key:  This is a two-part program that is used to create a report specification file. The first part of this program consists of a series of questions about the data files used in the report. The answers to these questions will be stored in the report specification file, and used later when the report is produced. You may type ^J at any question for additional information about that item. The second part of this program defines the report format. The first column of each line specifies when and how often that line type will appear in the report; the remainder of the line is an image of what will actually be printed. Any line may contain heading and data descriptions and/or report data. Space for report data is called a field and is indicated by the underline character. An example format is shown below: R INVENTORY REPORT FOR THE WEEK OF ________ P Part Number Quantity Price/thousand Total Value _______ ______ ________ ___________ As you create the layout, you may move freely around the screen using the CURSOR commands that will be displayed at the top of the screen. Type ^J now to begin the first part of the program:Enter name of report specification file (or press RETURN): The report specification file is where the specifications for your report are stored. If you have not yet designed a report, choose a name for the report specification file and enter it here. A report specification name is eight (or less) letters and/or numbers, optionally preceded by a disk drive (letter A-P followed by colon). Press ESC to enter report name or ^C to exit: ** Error 36 ** ":" is not a legal disk drive. A report specification name is eight (or less) letters and/or numbers, optionally preceded by a disk drive (letter A-P followed by colon). Press ESC to enter report name or ^C to exit: ** Error 37 ** "" - illegal character. A report specification name is eight (or less) letters and/or numbers, optionally preceded by a disk drive (letter A-P followed by colon). Press ESC to enter report name or ^C to exit: A report specification name is eight (or less) letters and/or numbers, optionally preceded by a disk drive (letter A-P followed by colon). Press ESC to enter report name or ^C to exit: ERROR 01 No report fields have been specified. ERROR 02 No detail line type (" " or ":") is present. Field  ERROR 03 Input file not specified. Field  ERROR 04 Output file used for input. Field  ERROR 05 Input field not specified. Field  ERROR 06 Index field not specified. Field  ERROR 07 Output file not specified. Field  ERROR 08 Output field not specified. Field  ERROR 09 Equivalent field or its base cannot be a control break. Field   10  Field calculation error: Field   11  UNLESS/THEN error: Field  ERROR 12 Missing edit mask constant. Field  ERROR 13 Edit mask order is not float, data, trail. Field  ERROR 14 Equivalent field is base of an equivalent field. Field  ERROR 15 Number of equivalent fields not constant. Field  ERROR 16 Equivalent field is referenced. Field   17  LOAD IF error: Field   18  CLEAR IF error: File   19  INCLUDE IF error: Line   20  PRINT WHEN error: Ctlb  ERROR 21 Control break not specified. Field  ERROR 22 Illegal line type for equivalent field or its base. WARNING 23 End report condition has not been specified. Field  ERROR 24 Input file used for output. File  ERROR 25 Missing data file volume name. Line  ERROR 26 Dot command error. WARNING 27 Control column order not RP123... ...321RP. Field  ERROR 28 Missing edit mask float/trail constant. Field  ERROR 29 Missing edit mask decimal alignment constant. Field  ERROR 30 Multiple edit mask decimal alignment positions. Field  ERROR 31 Edit mask float/trail constants not packed. Field  ERROR 32 Multiple edit mask float/trial conditionals. File  ERROR 33 Missing sort order. Field  ERROR 34 Equivalent fields with different field lengths. Field  ERROR 35 Equivalent field base is forward referenced. Field  ERROR 36 Multiple outputs to the same field. WARNING 37 Possibly not enough memory to run REPORT program. Field  ERROR 38 Control break field is control break or page dependent.   39  PAGE WHEN error:   40  END WHEN error: Field  ERROR 41 Input field not present in file. Field  ERROR 42 Output field not present in file. Field  ERROR 43 File key different length than index field length. Field  ERROR 44 Load condition not permitted with sequential input. Field  ERROR 45 Base of equivalent field cannot be operator input. Line  ERROR 46 Non-equivalent field(s) on line. ERRORAmissing report field. ERRORBillegal sub-field. WARNINGCrestricted function. ERRORDillegal use if FERR. ERROREreport field reference not "R" LOADed. Enter exit command: A=Abandon form-> start over S=save form -> end edit C=save form -> Continue edit F=no save -> edit File definition X=no save -> edit conditions L=List errors on LST: device SPACE=no save -> Continue edit (A/S/C/F/X/L/SPACE): Enter exit command: A=Abandon form-> start over S=Save form -> end edit C=save form -> Continue edit F=no save -> edit File definition X=no save -> edit conditions R=save form -> Run the report SPACE=no save -> Continue edit (A/S/C/X/R/F/SPACE):   errors and incomplete fields: Item # Error # Error description  Abandon edit without saving form? (Y/N)   ABSINTMAXMINREMPAGEFLD$FILEERRFERRCB Please enter page width (in columns):  Which reports do you want? 1 = Field numbers and ctl chars 4 = Field definitions 2 = Edit masks 5 = Print line and other conditions 3 = File descriptions 6 = Cross reference N = none of the above A = All of the above Enter one or more of 1,2,3,4,5,6,N,A and/or RETURN: A 123456NA REPORT LISTING WITH FIELD AND FILE ATTRIBUTE DEFINITIONSFIELD NUMBERS CONTROL CHARACTERS FILE DEFINITIONS EDIT MASK CONDITIONS EDIT MASK CONSTANTS PRINT LINE AND OTHER CONDITIONS FIELD DEFINITIONS CROSS REFERENCE LISTINGREFERENCEOUTPUT, WRITE INDEX FILEOUTPUTINPUT (INDEX ORDER)INPUTADD TOERRORFIELD NOT PADDED PAD WITH   NEW PAGEREPORT START(ALWAYS)REPORT ENDCONTROL BREAK   +LINE  PRINT CONDITION +FILE INCLUDE CONDITION+INDEX FOR , FIELD +CALCULATION+OUTPUT IF CONDITION+CLEAR IF CONDITION+EQUIVALENT TO+FIELD LOAD CONDITION+NEW PAGE CONDITION+END REPORT CONDITIONN+OUTPUT IF CONDITION+CLEAR IF CONDITION+EQUIVALENT TO+FIELD LOAD CONDITION+NEW PAGE CONDITION+END REPORT CO