Contents
000
INVALID WORD OR SYNTAX
VMRGRW is unable to determine the meaning of the underlined word in context. Omitting a period from an earlier statement is often the cause of this message. Other possibilities are:
- A COMPUTE operation is not PLUS, MINUS, TIMES, or OVER.
- A field name is longer than nine characters.
- STOP was not followed by the AFTER or PASS parameter.
001
NOT A KEYWORD
VMRGRW requires the underlined word to be a control statement parameter, but it is not. Likely causes are:
- A parameter was misspelled.
- A period was omitted from an earlier statement.
- The syntax of the control statement is incorrect.
002
NOT A FIELD NAME OR LITERAL
VMRGRW requires the underlined word to be a field name or a literal, but it is not. Likely causes are:
- A field name was misspelled.
- You did not enclose a literal (constant) with quotes.
- A period was omitted from an earlier statement.
- The syntax of the control statement is incorrect.
003
IGNORED DUE TO PREVIOUS ERROR
The underlined part of the statement was not scanned.
004
LITERAL EXCEEDS 78 CHARACTERS
A literal (constant) exceeds the maximum length, possibly because a closing quotation mark was omitted.
005
LITERAL TABLE FILLED
VMRGRW is unable to process your statement because a work area is filled. An extremely large number of DEFINE, REDEFINE, or COMPUTE statements could be responsible. Using too many literals can also contribute to this error.
006
SHOULD BE NUMERIC, IS NOT
The underlined field must be numeric, with no more than 16 digits.
007
DUPLICATE/INVALID FIELD NAME
In a DEFINE, REDEFINE, or COMPUTE statement, the first field name is either in use as a statement parameter or previously defined field, or invalid as a field name. Field names cannot be longer than nine characters, cannot include disallowed special characters, and cannot be enclosed in quotes.
008
INVALID FIELD FORMAT
The specified field format was not A/N, P/D, Z/D, BINS, BINP, BIT, or P/N.
009
NO FIELD LENGTH
In a DEFINE or REDEFINE statement, neither a valid END nor a valid LENGTH value was included.
010
INVALID DISPLAY LITERAL
In a COMPUTE, DEFINE, or REDEFINE statement, the DISPLAY parameter was not followed by a valid literal, possibly because the literal was not enclosed in quotation marks.
011
TOO MANY CONTROL FIELDS
In a SORT or PRINT TOTAL statement, there can be a maximum of 12 control fields.
012
TOO MANY FIELDS SPECIFIED
This message results from one of the following conditions:
- More than 300 fields were defined through DEFINE or REDEFINE statements. This limit applies to the total number of predefined fields built into VMRGRW plus any fields you have defined or redefined.
- More than 60 fields or literals were specified on a WRITE statement.
- More than 40 fields or literals were specified on a PRINT statement.
- More than 20 fields or literals were specified on a PRINT HEADING statement.
- More than 30 pairs of fields were specified on a MOVE statement.
013
TOO MANY TOTAL FIELDS
In a PRINT TOTAL statement, there can be a maximum of 13 fields.
014
PRINT LINE LENGTH EXCEEDED
In a PRINT statement, more than 132 characters were specified on a line.
015
NOT A VALID FILE NAME
In a FILE statement, the specified name is either a VMRGRW reserved word, or the specified fileid is invalid for CMS.
016
INVALID HEXADECIMAL CONSTANT
You used an expression that begins X', but some character before the closing quote is not a valid hexadecimal digit (0-9 or A-F).
017
TOO MANY CONDITIONS
In a SELECT, IGNORE, or IF statement, there can be a maximum of 12 conditions.
018
INVALID FIELD TYPE
In a COMPUTE statement, the field format is not P/D or Z/D. In a DECODE statement, the field format is not A/N or BIT.
019
INVALID CONDITION TEST MIX
In a SELECT or IGNORE statement, an attempt was made to compare an alphanumeric field with a non-alphanumeric field.
020
INVALID CONTROL FIELD
This message is sent if one of the following occurs in a CONTROL statement:
- The START column is not numeric or is greater than 79.
- The END column is not numeric or is greater than 80.
- The END column is not greater than the START column.
- The SPACE value is not 1 or 2.
021
CONTROL FIELDS TOO LONG
In a PRINT TOTAL statement, the total length of control fields exceeds 256 characters.
022
NO PRECEDING WRITE/SUMMARIZE
A SORT statement must be preceded by a WRITE statement or a SUMMARIZE statement.
023
FIELD TOO LONG FOR TYPE
The length of the field exceeds the maximum allowable length for that field type, as shown in the table about Field Types in Building the Control File.
024
MISSING FILE STATEMENT
The control file does not have a FILE statement.
025
FIELD NOT CARRIED IN RECORD
The underlined field was not specified on the most recent WRITE or SUMMARIZE statement and so is not available.
026
NO PRECEDING SORT
Two WRITE statements were found without an intervening SORT statement. This situation is allowed only if both WRITE statements are IF-dependent.
027
NOT A FIELD NAME
The specified field name was never defined and doesn't exist in the input file.
028
NOT A LITERAL
The underlined word is not a literal, but VMRGRW syntax requires a literal at this point. This might have occurred because you omitted quotation marks or coded '1' or 'X'.
029
UNEQUAL LENGTHS
When one VMRGRW step contains several WRITE statements (each one conditional on some IF test), each WRITE statement must specify fields or literals that add up to the same total length.
032
UNPAIRED QUOTES -- CARD IGNORED
A literal extends beyond one record, or a quote is missing.
033
TOO MANY FILE LINES
There can be only one FILE statement in a control file.
034
REFERS TO MORE THAN ONE LOCATION
The underlined field name occurs twice in a WRITE or SUMMARIZE statement.
042
END IS LESS THAN START
In a DEFINE or REDEFINE statement, the END value of the field is less than the START value of the field.
044
CANNOT BE IF-DEPENDENT
A SORT, SELECT, or SUMMARIZE statement is IF-dependent. That is, the statement appears between an IF statement and an END IF statement.
045
CANNOT FOLLOW PREVIOUS STATEMENT
A SORT statement must be immediately preceded by a WRITE, SUMMARIZE, or END STEP statement.
046
UNEQUAL REPLACE LENGTHS
In a DECODE statement, all of the REPLACE fields must be the same length.
047
FILE NOT FOUND
The file named (or defaulted to) on your FILE statement cannot be found on any accessed disk.
048
PERIOD MUST BE LAST CHARACTER
The last statement in your control file did not end with a period.
049
TASK TABLE OVERFLOW IN COMPILE
VMRGRW is unable to process your statement because a work area was filled. An extremely large number of VMRGRW statements could be responsible.
054
NEED ARITHMETIC OPERATION HERE
In a COMPUTE statement, the word designating the operation is not PLUS, MINUS, TIMES, or OVER.
055
COMPUTE TYPE MUST = Z/D OR P/D
In a COMPUTE statement, the TYPE specified for the computed field must be Z/D or P/D.
056
DISPLAY MUST BE SPECIFIED HERE
In a COMPUTE statement, the DISPLAY parameter must be specified immediately after the calculation is defined, as shown below:
COMPUTE TOTAL AS PART1 PLUS PART2 DISPLAY '999' HD.
057
PERIOD REQUIRED AT THIS POINT
VMRGRW processed a parameter that should be the last for the current statement (for example, the HD parameter in COMPUTE) but did not find a period immediately following it.
058
THIS WORD HAS MAX LENGTH OF 8
All words in a FILE statement have a maximum length of eight characters.
059
NO INPUT DEFINED FOR THIS STEP
A processing step (other than the first) has no input because the previous step produced no output. This can occur only if the previous step was terminated by an END STEP statement. The END STEP statement should be preceded by a WRITE or SUMMARIZE statement so that output is available for the next step.
060
CANNOT ADD ALPHA/BIT FIELDS
An alphanumeric (TYPE A/N) or bit (TYPE BIT) field was specified in a PRINT TOTAL or SUMMARIZE statement. These fields cannot be added and are invalid in these statements except as control fields.
061
NOT ALLOWED AFTER 'NOW'
Only MOVE or COMPUTE can follow the NOW keyword.
062
FILE CMD MUST BE ALONE ON CARD
The period at the end of your FILE statement must be the last non-blank in the record. This restriction does not apply to other statements.
063
PREV FIELD IS NOT BIT OR ALPHA
You used a numeric field in a Bit Test as part of an IF, SELECT, or IGNORE statement. For example:
IF fldname HAS ANY BITS OFF X'04'.
The field (fldname) you supplied must be TYPE A/N or TYPE BIT.
064
INVALID BIT MASK
You used a Bit Test as part of an IF, SELECT, or IGNORE statement, and the mask value is invalid. The mask must be formatted as 'ab' or X'ab', where a and b are valid hexadecimal digits (that is, 0-9 and A-F).
065
NAME USED TWICE IN PRINT TOTAL
In a PRINT TOTAL statement, you specified the same field more than once.
066
TOO MANY WORDS IN FILE COMMAND
Your FILE statement includes more than 13 words, including the keyword FILE.
067
INVALID FOR PREV-DEFINED FIELD
In a DEFINE statement for a previously defined field, you can use only the DISPLAY parameter or new heading literals (including the HD parameter).
068
SELECT/IGNORE MUST BE TOGETHER
All SELECT and IGNORE statements in your control file must be entered consecutively. They cannot be separated by any other statements.
069
FIELD LENGTH INVALID FOR TYPE
In a DEFINE or REDEFINE statement, the length of the field (given directly by LENGTH or indirectly by END) is not consistent with the TYPE given for the field.