HP 3000 Manuals HP 3000 Manuals
Message Types (Cont.)
---------------------------------------------------------------------------------------
6002W MESSAGE AN/OR LINE OUT OF ORDER OR INVALID, IGNORE AN/OR LINE.
CAUSE You entered an AN or OR line, and the preceding line has an entry in
the Operation Field or the preceding line did not have an entry in
the Indicators Field.
ACTION The compiler ignores this line. Put AN/OR line in proper sequence.
---------------------------------------------------------------------------------------
6003T MESSAGE EXCEEDED 24 INDICATORS OR 7 '0R' LINES.
CAUSE You entered more than seven OR lines or more than 24 indicator lines
in one grouping, which is not permitted.
ACTION The compiler ignores the entire grouping. Change the program so that
there are no more than seven OR lines or 24 indicators.
---------------------------------------------------------------------------------------
6004W MESSAGE 'AN' OR 'OR' NOT SPECIFIED IN COLUMNS. 7-8, IGNORE GROUP.
CAUSE The statement before this AN/OR record had conditioning indicators,
but no operation was specified.
ACTION The compiler ignores the entire group. Put the operation in the
previous statement or include AN/OR in this specification.
---------------------------------------------------------------------------------------
6005T MESSAGE OPERATION NOT RECOGNIZED.
CAUSE You entered an invalid operation in the Operation Field (columns
28-32).
ACTION The compiler ignores this operation. Correct it and recompile.
---------------------------------------------------------------------------------------
6006W MESSAGE 'NOT' ENTRY IN COL. 9, 12, OR 15 NOT N OR BLANK, ASSUME N.
CAUSE You entered a character other than N or blank in the Not Subfield
(column 9, 12, or 15).
ACTION The compiler assumes that you entered N.
---------------------------------------------------------------------------------------
6007W MESSAGE INVALID OPERATION INDICATOR, IGNORE INDICATOR GROUP.
CAUSE You entered an invalid operation indicator in the Indicators Field
(columns 9-17).
ACTION The compiler ignores the indicators and performs the operation in any
event. Correct the indicator in the Indicators Field (columns 9-17).
---------------------------------------------------------------------------------------
6008W MESSAGE INDICATOR MISSING FOR 'NOT' IN COL. 9, 12, OR 15, IGNORE NOT.
CAUSE You entered an N (for Not) in columns 9, 12, or 15, but did not enter
an indicator in columns 10-11, 13-14, or 16-17.
ACTION The compiler ignores the N entry.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
6009W MESSAGE INVALID RESULTING INDICATOR, IGNORE INDICATOR GROUP.
CAUSE You entered an invalid indicator in the Resulting Indicators Field
(columns 54-59).
ACTION The compiler ignores this indicator and all others in the group to
which it belongs. Correct the indicator and recompile.
---------------------------------------------------------------------------------------
6010W MESSAGE INVALID FACTOR 1 ENTRY IN COL. 18-27.
CAUSE You entered an invalid name, label, or literal in the Factor 1 Field
(columns 18-27).
ACTION The compiler ignores this operation. Correct Factor 1 to contain a
valid field name or a literal.
---------------------------------------------------------------------------------------
6011T MESSAGE INVALID FACTOR 2 ENTRY IN COL. 33-42.
CAUSE You entered an invalid name, label, or literal in the Factor 2 Field
(columns 33-42).
ACTION The compiler ignores this operation. Correct Factor 2 to contain a
valid field name or a literal.
---------------------------------------------------------------------------------------
6012W MESSAGE INVALID RESULT FIELD ENTRY IN COLUMNS. 43-48.
CAUSE You entered an invalid name in the Result Field (columns 43-48).
ACTION The compiler ignores the operation associated with this entry.
Correct the Result Field so that is contains a valid field name.
---------------------------------------------------------------------------------------
6013W MESSAGE INVALID INDEX IN FACTOR 1 (COL. 18-27).
CAUSE You specified an indexed array in the Factor 1 Field, but did not use
a valid index.
ACTION The compiler assumes an index value of 1. Correct the index so that
it is a valid field (that is a numeric field with zero decimal
positions) or a numeric unsigned literal with no decimal positions.
---------------------------------------------------------------------------------------
6014W MESSAGE INVALID INDEX IN FACTOR 2 (COL. 33-42).
CAUSE You specified an indexed array in the Factor 2 Field, but did not use
a valid index.
ACTION The compiler assumes an index value of 1. Correct the index so that
it is a valid field (that is a numeric field with zero decimal
positions) or a numeric unsigned literal with no decimal positions.
---------------------------------------------------------------------------------------
6015W MESSAGE INVALID INDEX IN RESULT FIELD (COL. 43-48).
CAUSE You specified an indexed array in the Result Field, but did not use a
valid index.
ACTION The compiler assumes an index value of 1. Correct the index so that
it is a valid field name (that is a numeric field with zero decimal
positions) or a numeric unsigned literal with no decimal positions.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
6016T MESSAGE INVALID FILE NAME ENTRY FOR FACTOR 2 (COL. 33-42).
CAUSE You entered an improper file name in the Factor 2 Field.
ACTION The compiler ignores the operation. Correct the file name so that it
appears as defined in the File Description Specifications.
---------------------------------------------------------------------------------------
6017W MESSAGE INVALID DIGIT IN RESULT FIELD LENGTH ENTRY (COL. 49-51).
CAUSE You entered one or more characters other than 0-9 in the Field Length
Field. Embedded blanks are illegal.
ACTION The compiler ignores the field length. Enter a valid field length,
right-justified, without embedded blanks.
---------------------------------------------------------------------------------------
6018W MESSAGE INVALID DIGIT IN DECIMAL POSITIONS ENTRY (COL. 52).
CAUSE You entered a value other than 0 through 9 in the Decimal Positions
Field.
ACTION The compiler assumes zero decimal positions. Enter a digit 0-9 in
column 52.
---------------------------------------------------------------------------------------
6019W MESSAGE RESULT FIELD LENGTH MISSING BUT DEC POS SPECIFIED. IGNORE DEC POS.
CAUSE You specified a number of decimal positions for the Result Field, but
did not specify the field length.
ACTION The compiler assumes there are no decimal positions. Enter a valid
field length or leave the Decimal Positions Field blank.
---------------------------------------------------------------------------------------
6020W MESSAGE HALF ADJUST ENTRY IN COL. 53 NOT H OR BLANK, ASSUME H.
CAUSE You entered a character other than H or a blank in the Half Adjust
Field, which is illegal.
ACTION The compiler assumes that you entered H, specifying Half Adjust.
---------------------------------------------------------------------------------------
6021W MESSAGE FIELD ATTRIBUTE NOT SAME AS PREV DEFN, USE PREV DEFN.
CAUSE You entered a different field length or number of decimal positions
than was previously assigned to the field.
ACTION The compiler uses the previous definition for the field. Correct the
field attributes of the incorrect statement.
---------------------------------------------------------------------------------------
6022W MESSAGE RESULT FIELD HAS INDEX BUT NOT ARRAY NAME, IGNORE INDEX.
CAUSE You entered an array index in the Result Field but did not specify an
array name.
ACTION The compiler ignores the array index. Remove the index, define the
field name as an array on a File Extension Specification or use a
proper array name.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
6023T MESSAGE FILE NAME IN FACTOR 2 NOT DEFINED BY FILE DESC SPECS.
CAUSE You entered a file name in the Factor 2 Field (columns 33-42) that is
not described in the File Description Specifications.
ACTION The compiler ignores the operation. Either define this file name in
a File Description Specification or use another file name.
---------------------------------------------------------------------------------------
6024W MESSAGE SET OPERATOR USAGE NOT CONSISTENT WITH WORKSTATION OPERATION.
OPERATOR IGNORED.
CAUSE Set operator found in a program using a workstation file.
ACTION Compiler ignores the operation.
---------------------------------------------------------------------------------------
6025W MESSAGE FACTOR 1 IS MISSING (COL. 18-27).
CAUSE You omitted Factor 1 from an operation that requires it.
ACTION The compiler ignores the operation. Enter Factor 1 and recompile.
---------------------------------------------------------------------------------------
6026W MESSAGE FACTOR 2 IS MISSING (COL. 33-42).
CAUSE You omitted Factor 2 from an operation that requires it.
ACTION The compiler ignores the operation. Enter Factor 2 and recompile.
---------------------------------------------------------------------------------------
6027W MESSAGE RESULT FIELD IS MISSING (COL. 43-48).
CAUSE You omitted the Result Field from an operation that requires this
field.
ACTION The compiler ignores the operation. Enter information in the Result
Field and recompile.
---------------------------------------------------------------------------------------
6028W MESSAGE A RESULTING INDICATOR MUST BE SPECIFIED FOR THIS OPERATION.
CAUSE You failed to specify a resulting indicator in columns 54-59 for an
operation that requires this indicator.
ACTION The compiler ignores the operation. Specify a resulting indicator
and recompile.
---------------------------------------------------------------------------------------
6030W MESSAGE MISSING ENDSR STATEMENT, ASSUME ENDSR.
CAUSE You omitted the ENDSR operation from an internal subroutine.
ACTION The compiler assumes that an ENDSR statement follows the last
statement with SR in the Control Level Field.
---------------------------------------------------------------------------------------
6031W MESSAGE OPERATION INDICATORS MISSING ON AN/OR LINE.
CAUSE You entered AN or OR in columns 7-8, but did not enter indicators in
the Indicators Field (columns 9-17).
ACTION The compiler uses the indicators specified in the preceding lines.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
6032W MESSAGE INDICATORS IN COL. 9-17 NOT ALLOWED FOR THIS OPERATION. ASSUME BLANK.
CAUSE You entered one or more indicators in columns 9-17, but this
operation cannot be conditioned with indicators.
ACTION The compiler assumes that you left columns 9-17 blank and performs
the operation under all conditions.
---------------------------------------------------------------------------------------
6033W MESSAGE INDICATORS IN COL. 54-59 NOT ALLOWED FOR THIS OPERATION. ASSUME
BLANK.
CAUSE You entered one or more indicators in the Resulting Indicators Field,
but they are not permitted for this operation.
ACTION The compiler assumes that you left the Resulting Indicators Field
blank.
---------------------------------------------------------------------------------------
6034W MESSAGE FACTOR 1 SHOULD BE BLANK FOR THIS OPERATION ASSUME BLANK.
CAUSE You entered the Factor 1 Field but it is prohibited for this
operation.
ACTION The compiler assumes that you left the Factor 1 Field blank.
---------------------------------------------------------------------------------------
6035W MESSAGE FACTOR 2 SHOULD BE BLANK FOR THIS OPERATION ASSUME BLANK.
CAUSE You entered the Factor 2 Field but it is prohibited for this
operation.
ACTION The compiler assumes that you left the Factor 2 Field blank.
---------------------------------------------------------------------------------------
6036W MESSAGE RESULT FIELD SHOULD BE BLANK FOR THIS OPERATION ASSUME BLANK.
CAUSE You entered a field name in the Result Field, but it should remain
blank for this operation.
ACTION The compiler assumes that you left the Result Field blank.
---------------------------------------------------------------------------------------
6037W MESSAGE FIELD USED AS RESULT IS NON ALTERABLE. IGNORE SPEC.
CAUSE You specified a look-ahead field, UDAY, UMONTH, UYEAR, or UDATE in
the Result Field.
ACTION The compiler ignores this operation. Specify a different field name
and recompile.
---------------------------------------------------------------------------------------
6038W MESSAGE PAGE FIELD USED AS RESULT FIELD IS ALREADY REDEFINED. USE PREV DEFN.
CAUSE You entered PAGE in the Result Field and redefined it again by giving
it a new length.
ACTION The compiler uses the previous definition for PAGE.
---------------------------------------------------------------------------------------
6039W MESSAGE NAME ALREADY HAS ANOTHER USE.
CAUSE The same name is used for both a subroutine name and a tag.
ACTION Correct program and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
6040T MESSAGE GOTO OPERATION MAY NOT BRANCH INTO OR OUT OF SUBROUTINE.
CAUSE You specified a GOTO operation in a subroutine that transfers to an
operation outside of it or vice versa.
ACTION The compiler ignores the operation. Correct and recompile.
---------------------------------------------------------------------------------------
6041W MESSAGE DEC POS ENTRY GREATER THAN FIELD LENGTH. ASSUME ZERO POS.
CAUSE The number of decimal positions in the field exceeds the length of
the field.
ACTION The compiler assumes that the field contains no decimal positions.
Correct either the number of decimal positions or the entry length
and recompile.
---------------------------------------------------------------------------------------
6042T MESSAGE NAME REFERENCED SHOULD BE TAG NAME.
CAUSE You entered a GOTO operation that does not reference a TAG label.
(Tags and subroutines cannot have the same name.)
ACTION The compiler ignores the operation. Either rename the tag or rename
the subroutine.
---------------------------------------------------------------------------------------
6043T MESSAGE A SUBROUTINE MAY NOT CALL ITSELF.
CAUSE You included, within an internal subroutine, an operation that
attempts to invoke that subroutine; this type of recursion is
illegal.
ACTION The compiler ignores the operation. Correct and recompile.
---------------------------------------------------------------------------------------
6044T MESSAGE BEGSR STATEMENT MISSING. ASSUME BEGSR.
CAUSE You did not begin an internal subroutine with the BEGSR operation.
ACTION The compiler assumes that the first operation in the subroutine is
BEGSR. Include a BEGSR operation and a recompile.
---------------------------------------------------------------------------------------
6045T MESSAGE BEGSR OUT OF SEQUENCE. IGNORE BEGSR LINE.
CAUSE You included a BEGSR operation within the body of an internal
subroutine, after the first operation.
ACTION The compiler ignores this BEGSR request. Place BEGSR in correct
order and recompile.
---------------------------------------------------------------------------------------
6046I MESSAGE DEBUG OPTION NOT SPECIFIED IN COL.15 OF HEADER SPEC.
CAUSE You included one or more DEBUG operations but did not specify the
Debug option in the Debug Field (column 15) of the Header
Specification.
ACTION The compiler does not execute the DEBUG request.
---------------------------------------------------------------------------------------
6047W MESSAGE FIELD LENGTH AND DEC POS SHOULD BE BLANK. ASSUME BLANK.
CAUSE For a previously defined table or array in the Result Field, you
entered values in the Field Length or Decimal Positions Field.
ACTION The compiler assumes that the Field Length and Decimal Positions
Fields are blank.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
6048W MESSAGE DEC POS ENTRY (COL 52) SHOULD BE BLANK. ASSUME BLANK.
CAUSE You specified a decimal position that should not be specified.
ACTION The compiler ignores this specification.
---------------------------------------------------------------------------------------
6049W MESSAGE HALF ADJUST ENTRY (COL 53) SHOULD BE BLANK. ASSUME BLANK.
CAUSE You specified a half adjust that should not be specified.
ACTION The compiler ignores this specification.
---------------------------------------------------------------------------------------
6050W MESSAGE BEGSR STATEMENT SHOULD HAVE SR OR BLANK IN COL. 7-8; ASSUME SR.
CAUSE You specified a BEGSR operation that did not include SR or a blank in
columns 7-8.
ACTION The compiler assumes that you entered SR in these columns.
---------------------------------------------------------------------------------------
6051W MESSAGE FIELD LENGTH OVER 256 FOR ALPHANUMERIC OR OVER 15 FOR NUMERIC.
CAUSE You specified a field length that exceeds the maximum length allowed
for the Result Field (columns 49-51).
ACTION The specification is ignored. Redefine the field length and
recompile.
---------------------------------------------------------------------------------------
6052W MESSAGE OPERATOR NOT IMPLEMENTED ON THIS VERSION OF RPG.
CAUSE You entered an operator (in columns 28-32) that cannot be executed
with this version of the compiler.
ACTION The compiler ignores this specification.
---------------------------------------------------------------------------------------
6053W MESSAGE PRECEDING OPERATOR WAS NOT A DIV.
CAUSE You specified an MVR (move remainder) operation that is not
immediately preceded by a DIV (divide) operation.
ACTION The compiler ignores this MVR operation. Enter MVR immediately
following the DIV operation and recompile.
---------------------------------------------------------------------------------------
6054T MESSAGE DUPLICATE TAG NAME.
CAUSE You assigned the same label to two or more TAG operations.
ACTION The compiler ignores the second TAG operation. Change one of the TAG
labels and recompile.
---------------------------------------------------------------------------------------
6055T MESSAGE DUPLICATE SUBROUTINE NAME.
CAUSE You assigned the same name to two or more subroutines.
ACTION Change one of the subroutine names and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
6056T MESSAGE SYMBOL NOT DEFINED.
CAUSE You referenced the name of a data area or label of an operation that
is not defined in the program.
ACTION Define the symbol by naming it in the Result Field with a defined
length, by specifying it as a field name on Input Specifications, or
by defining it as an array. Recompile the program.
---------------------------------------------------------------------------------------
6057W MESSAGE FIELD 1 SHOULD BE ALPHANUMERIC FOR THIS OPERATION.
CAUSE You entered a numeric field for Factor 1 (columns 18-27), but it
should be alphanumeric.
ACTION The compiler uses the field as specified. Change the Factor 1 type
and recompile.
---------------------------------------------------------------------------------------
6058W MESSAGE FIELD 2 SHOULD BE ALPHANUMERIC FOR THIS OPERATION.
CAUSE You entered a numeric field for Factor 2 (columns 33-42), but it
should be alphanumeric.
ACTION The compiler uses the field as specified. Change the Factor 2 type
and recompile.
---------------------------------------------------------------------------------------
6059W MESSAGE RESULT FIELD SHOULD BE ALPHANUMERIC FOR THIS OPERATION.
CAUSE You entered a numeric field in the Result Field (columns 43-48), but
it should be alphanumeric.
ACTION The compiler uses the field as specified. Change the Result Field
type and recompile.
---------------------------------------------------------------------------------------
6060W MESSAGE FIELD 2 MUST BE THE SAME TYPE AS FIELD 1.
CAUSE You specified a different data format for Factor 1 than for Factor 2,
which is illegal for this operation.
ACTION The compiler uses the field as specified. Change either the Factor 1
or Factor 2 type and recompile.
---------------------------------------------------------------------------------------
6061W MESSAGE FIELD 1 SHOULD BE NUMERIC FOR THIS OPERATION.
CAUSE You entered an alphanumeric field for Factor 1 (columns 18-27), but a
numeric field is required.
ACTION The compiler uses the field as specified. Change the Factor 1 type
and recompile.
---------------------------------------------------------------------------------------
6062W MESSAGE FIELD 2 SHOULD BE NUMERIC FOR THIS OPERATION.
CAUSE You entered an alphanumeric field for Factor 2 (columns 33-42), but a
numeric field is required.
ACTION The compiler uses the field as specified. Change the Factor 2 type
and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
6063W MESSAGE RESULT FIELD SHOULD BE NUMERIC FOR THIS OPERATION.
CAUSE You entered an alphanumeric field for the Result Field (columns
43-48), but a numeric field is required.
ACTION The compiler uses the field as specified. Change the Result Field
type and recompile.
---------------------------------------------------------------------------------------
6064W MESSAGE RESULTING INDICATOR REQUIRED IN COL 54-55; ASSUME H0.
CAUSE You did not enter the required indicator in the Resulting Indicators
Field (columns 54-55).
ACTION The compiler assumes that you entered the H0 indicator.
---------------------------------------------------------------------------------------
6065W MESSAGE RESULTING INDICATOR REQUIRED IN COL 58-59; ASSUME H0.
CAUSE You did not enter the required indicator in the Resulting Indicators
Field (columns 58-59).
ACTION The compiler assumes that you entered the H0 indicator.
---------------------------------------------------------------------------------------
6066W MESSAGE RESULTING INDICATOR REQUIRED IN COL 56-57; ASSUME H0.
CAUSE You did not enter the required indicator in the Resulting Indicators
Field (columns 56-57).
ACTION The compiler assumes that you entered the H0 indicator.
---------------------------------------------------------------------------------------
6067W MESSAGE ILLEGAL I/O MODE IN IMAGE FILE.
CAUSE You specified an operation that is incompatible with the input/output
mode.
ACTION The compiler ignores the operation. Correct and recompile.
---------------------------------------------------------------------------------------
6068W MESSAGE INCOMPATIBLE FIELD 1 LENGTH.
CAUSE You specified a field length that is different from the Key Length
specified in the File Description Specification. (If packed decimal
keys are used, the key field length is the number of digits divided
by 2 plus 1.)
ACTION The length specified in the File Description Specification is used.
Change either the key length in the File Description Specification or
the Factor 1 Field length.
---------------------------------------------------------------------------------------
6069T MESSAGE FILE SPECIFIED IN FACTOR 2 NOT AN INDEXED DEMAND FILE.
CAUSE You requested a SETLL operation for a file that is not a demand file.
ACTION Change the file type to a demand file.
---------------------------------------------------------------------------------------
6070W MESSAGE FILE BEING READ IS NOT A DEMAND FILE.
CAUSE You used the READ command for a file that is not a demand file.
ACTION If you wish to ignore this warning, demand reads are intermixed with
all other accesses of the file. Otherwise, change the specification
to reflect a demand file.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
6071T MESSAGE CURRENT FIELD USE INCONSISTENT WITH PREVIOUS USE.
CAUSE You either used an alphanumeric field as a numeric field or
vice-versa.
ACTION Change specifications to make all references consistent.
---------------------------------------------------------------------------------------
6072W MESSAGE FILE SPECIFIED IN FACTOR 2 NOT A CHAINING FILE.
CAUSE A CHAIN operation was attempted to a file that is not a chaining
file.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
6073T MESSAGE CAN'T FORCE READ A FILE DESIGNATED BY BLANK IN COL 16 OF FILE SPEC.
CAUSE You specified a FORCE operation for a file which contained a blank in
column 16 of the File Description Specification.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
6074T MESSAGE PARM OPERATIONS MUST IMMEDIATELY FOLLOW AN EXIT OPERATION.
CAUSE You specified a PARM operation which does not follow an EXIT or
another PARM operation.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
6081T MESSAGE LOW OR EQUAL RESULT INDICATOR MUST BE SPECIFIED FOR THIS OPERATION.
CAUSE You must specify a resulting indicator in the Low Subfield (columns
56-57) or the Equal Subfield (columns 58-59).
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
6082T MESSAGE IMAGE FILE LOCKING MODE IS NOT L, B, S, 1, 9, OR R TO ENABLE LOCKING.
CAUSE You specified an incorrect locking mode for using the LOCK/UNLCK
operations. The locking mode is specified in the Open Mode Field
(column 66) of the Database Name (IMAGE) Line of the File Description
Specification.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
6083T MESSAGE FILE NOT DESCRIBED WITH NOLOCK OR LOCK CONTINUATION RECORD TO ENABLE
LOCKING.
CAUSE You are using LOCK/UNLCK operations, but did not enable locking using
NOLOCK/LOCK in the File Description Specification.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
6084T MESSAGE DBNAME IN RESULT FIELD MUST BE SAME NAME SPECIFIED IN IMAGE SPEC FOR
FILE IN FACTOR 2.
CAUSE The database name specified in the Result Field does not match the
name specified in the Database Name (IMAGE) Line for the Factor 2
file.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
6085T MESSAGE LENGTH OF A VARIABLE USED TO INDEX AN ARRAY MUST BE 1 TO 9 DIGITS.
CAUSE You specified an incorrect entry for the length of a variable.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
6087I MESSAGE NO INDICATOR IN COL 58-59. H0 WILL BE SET ON FOR ERRORS NOT FLAGGED
BY INDICATORS IN COL. 54-57.
CAUSE You did not specify an equal indicator, so there is no way to inform
you that an error other than those covered by the high and low
indicators has occurred.
ACTION Specify and use the equal indicator for this operation.
---------------------------------------------------------------------------------------
6088T MESSAGE SORTA OPERATOR ONLY ALLOWED ON NON-ALTERNATING ARRAY.
CAUSE The SORTA operation is not allowed for the array.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
6089T MESSAGE GENERIC KEY ACCESS ONLY ALLOWED WITH KSAM FILES.
CAUSE You specified *EQ, *GT, or *GE in the Result Field for a CHAIN or
SETLL operation on a non-KSAM file.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
6090T MESSAGE GENERIC KEY ACCESS ONLY ALLOWED WITH ALPHANUMERIC OR PACKED KEYS.
CAUSE You specified *EQ, *GT, or *GE in the Result Field for a CHAIN or
SETLL operation on a file whose Record Address Type (column 31) does
not contain A or P.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
6091T MESSAGE PACKED GENERIC KEY MUST BE EXACT SIZE DEFINED IN FILE DESC. SPEC.
CAUSE You specified *EQ, *GT, or *GE in the Result Field and the generic
key size differs from the size defined in the Key Field Length Field
(columns 29-30) of the File Description Specification.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
6096T MESSAGE INVALID STRUCTURED OPERATION - MISSING OR EXTRANEOUS 'END', OR TOO
MANY NESTED LEVELS
CAUSE You specified a structured programming operation IF, ELSE, DOU, or
DOW, and either did not specify a matching END operation or specified
too many END operations, or nested structured operators to more than
100 levels in depth.
ACTION Ensure that you have matched up structured operators and END
statements. Correct the program and recompile.
---------------------------------------------------------------------------------------
6097W MESSAGE INVALID BIT NUMBER IN FACTOR 2 OF 'BITON', 'BITOF', OR 'TESTB'.
CAUSE A character other than 0-7 was used in the Factor 2 Field of these
operations.
ACTION Enter only 0-7 to specify bit positions in the field.
---------------------------------------------------------------------------------------