HP 3000 Manuals HP 3000 Manuals
Message Types (Cont)
---------------------------------------------------------------------------------------
6098W MESSAGE INVALID RESULT INDICATORS FOR 'CLOSE', 'READ', OR 'MSG' OPERATOR.
CAUSE One or more indicators were used in invalid locations in the
Resulting Indicators Field (columns 54-59).
ACTION Delete the incorrect indicator(s).
---------------------------------------------------------------------------------------
6099T MESSAGE EXTRANEOUS OR MISPLACED ELSE STATEMENT.
CAUSE There are too many ELSE statements for the number of IF statements in
your program. Or the ELSE statement might be after the END
statement. This can also occur if the IF statement is in the detail
calculations, and the ELSE statement is in total time calculations.
ACTION Make sure the ELSE statements are located correctly in the program;
delete unnecessary ELSE statements.
---------------------------------------------------------------------------------------
6100W MESSAGE OPERATOR NOT SUPPORTED ON RPG/iX.
CAUSE The RPG/iX compiler detected the RPGCV, ERPGC, or EXTCV operation in
the Calculation Specifications of your program. These operations are
not supported by the RPG/iX compiler.
ACTION Your program must be rewritten to avoid the use of these operations.
---------------------------------------------------------------------------------------
6101T MESSAGE RESULT FIELD IS REQUIRED (COL 43-48).
CAUSE A Calculation Specification using the PARM operation was encountered
(used to pass data to external subroutines), but the data to be
passed was not specified in the Result Field.
ACTION Check statements using the PARM operation for missing Result Field
entries.
---------------------------------------------------------------------------------------
6102W MESSAGE XFOOT OPERATION USES WHOLE ARRAY. INDEX IS IGNORED.
CAUSE An array name with an index was specified for Factor 2 in an XFOOT
operation. The compiler expects an array name without an index.
ACTION To avoid this warning, remove the index from the array in this
operation.
---------------------------------------------------------------------------------------
6103T MESSAGE IPARM OPERATIONS MUST IMMEDIATELY FOLLOW AN INTR OPERATION.
CAUSE An operation other than IPARM was found between an INTR operation and
its associated IPARM operations.
ACTION Remove the improperly located operation.
---------------------------------------------------------------------------------------
6104T MESSAGE INVALID INTRINSIC NAME IN COL. 33 THROUGH 48.
CAUSE The compiler detected an invalid intrinsic name referenced in a
Calculation Specification using the INTR operation.
ACTION Enter a valid intrinsic name in columns 33-48. Refer to the MPE/iX
Intrinsics Reference Manual if necessary.
---------------------------------------------------------------------------------------
6105T MESSAGE COULD NOT OPEN THE INTRINSIC MECHANISM.
CAUSE The compiler could not open the SYSINTR.PUB.SYS file.
ACTION Make sure this file is on your system, and that its READ access is
ANY.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
6106T MESSAGE COULD NOT FIND THIS INTRINSIC IN SYSINTR.PUB.SYS.
CAUSE The intrinsic named in an INTR operation of a Calculation
Specification was not found the intrinsic mechanism file
SYSINTR.PUB.SYS.
ACTION Check the spelling of the intrinsic name used in the INTR operation.
If this is a user-created intrinsic, verify that it was added to the
SYSINTR.PUB.SYS file.
---------------------------------------------------------------------------------------
6107T MESSAGE TYPE MISMATCH IN IPARM OR FACTOR 1 OF INTR.
CAUSE The intrinsic expects a specific data type (alphanumeric or numeric)
for this parameter, but a field of the wrong type was specified.
ACTION Check the types of the fields you are using to make sure they are
correct for the intrinsic.
---------------------------------------------------------------------------------------
6108T MESSAGE COULD NOT EXTRACT PARM INFO FOR THIS PARAMETER.
CAUSE Information for the parameter named in an IPARM operation or in
Factor 1 of an INTR operation was not found in the intrinsic
mechanism file SYSINTR.PUB.SYS.
ACTION Check your program to make sure your parameters match those specified
by the intrinsic.
---------------------------------------------------------------------------------------
6109T MESSAGE MISSING REQUIRED PARAMETER.
CAUSE A parameter that is required by the intrinsic named in an INTR
operation was not provided.
ACTION Check to see which parameters are required for this intrinsic, and
add them to your program.
---------------------------------------------------------------------------------------
6111W MESSAGE COULD NOT CLOSE THE INTRINSIC MECHANISM.
CAUSE The compiler uas unable to close the SYSINTR.PUB.SYS intrinsic
mechanism file.
ACTION Refer to the file information display for the actual file system
error that occurred. Take the appropriate action for the file system
error.
---------------------------------------------------------------------------------------
6112I MESSAGE ALPHANUMERIC FIELD SPECIFIED WHERE NUMERIC WAS EXPECTED.
CAUSE The compiler is informing you that an alphanumeric field is being
passed to an intrinsic that expects a numeric field. This is
allowed. You can, for instance, pass a long real item to the HPINEXT
intrinsic as an 8-byte ASCII string.
ACTION If this is what you intended, you may ignore this information.
---------------------------------------------------------------------------------------
6113T MESSAGE NUMERIC FIELD MUST HAVE 0 DEC PLACES.
CAUSE The number being passed to an intrinsic must be an integer.
ACTION Correct the field definition for this parameter in your program.
---------------------------------------------------------------------------------------
6114W MESSAGE THIS INTRINSIC IS NOT A FUNCTION. FACTOR 1 IGNORED.
CAUSE The intrinsic specified in an INTR operation does not return a value,
but an entry was found in Factor 1 as if a value was expected.
ACTION The Factor 1 entry is ignored. To avoid this warning, remove the
Factor 1 entry from the INTR operation for this intrinsic.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
6115T MESSAGE RESET OP FILE TYPE MUST BE I OR U, DESIG MUST BE D OR F.
CAUSE The file named in a RESET operation does not have the proper type or
designation or both.
ACTION Make sure the File Specification type is I or U, and the designation
is D or F.
---------------------------------------------------------------------------------------
6116T MESSAGE RESET OPERATOR MUST HAVE INDICATOR IN COLS 54-55.
CAUSE The compiler found no indicator specified in columns 54-55 of a
Calculation Specification using the RESET operation.
ACTION Add an indicator in columns 54-55 of the operation. Test this
indicator following the RESET operation to make sure it worked.
---------------------------------------------------------------------------------------
6117T MESSAGE CANNOT RESET KSAM FILE IF READ CHRONOLOGICALLY.
CAUSE A KSAM file named in a RESET operation has C in column 32 of its File
Specification.
ACTION A KSAM file that is being read in chronological order cannot be
reset.
---------------------------------------------------------------------------------------
7001T MESSAGE INVALID FILENAME IN COL 7-14, SPEC IS DROPPED.
CAUSE You used an undefined file in the File Name Field (columns 7-14).
ACTION Define the file name in the File Description Specifications or use a
valid file name in the Output Specifications and recompile.
---------------------------------------------------------------------------------------
7002T MESSAGE 'AND' OR 'OR' LINE NOT PRECEDED BY RECORD DESCRIPTION.
CAUSE You entered an AND or OR line that is not preceded by a specification
that describes the record to which it applies.
ACTION Enter a record description specification before this AND/OR line and
recompile.
---------------------------------------------------------------------------------------
7003T MESSAGE NO RECORD DESCRIPTION ENTRIES DEFINED YET.
CAUSE You did not specify a record description as the first item in your
Output Specification.
ACTION Define a valid record description and recompile.
---------------------------------------------------------------------------------------
7004W MESSAGE INVALID ENTRIES IN COL 32-74 FOR A RECORD DESCRIPTION SPECIFICATION,
ASSUME BLANK.
CAUSE You entered field description information in a record description
specification.
ACTION The compiler assumes that columns 32-74 are blank. Correct the
record description specification and recompile.
---------------------------------------------------------------------------------------
7005W MESSAGE INVALID ENTRIES IN COL 7-22 FOR A FIELD DESCRIPTION SPECIFICATION,
ASSUME BLANK.
CAUSE You entered record description information in a field description
specification.
ACTION Correct the field description specification and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
7006T MESSAGE FILE AND RECORD ENTRIES IN COL 7-31 AND FIELD ENTRIES IN COLS 32-74
ON SAME LINE.
CAUSE You entered both a record description and a field description on the
same line.
ACTION Correct this error and recompile.
---------------------------------------------------------------------------------------
7007I MESSAGE NO FIELD DESCRIPTION ENTRIES FOR PREVIOUS RECORD.
CAUSE You entered a record description specification that is not followed
by field description specifications.
ACTION Supply a field description specification and recompile.
---------------------------------------------------------------------------------------
7008T MESSAGE NO RECORD DESCRIPTION ENTRIES FOR THIS FIELD DESCRIPTION ENTRY, SPEC
IS DROPPED.
CAUSE You entered a field description specification that is not preceded by
a record description specification.
ACTION Insert the record description entry and recompile.
---------------------------------------------------------------------------------------
7009T MESSAGE MORE THAN 20 AND/OR LINES, SPEC IS DROPPED.
CAUSE You exceeded the limit of 20 AND or OR lines in an AND/OR grouping.
ACTION Delete the appropriate number of AND/OR lines and recompile.
---------------------------------------------------------------------------------------
7010W MESSAGE EDIT WORD IN COL 45-70 IS NOT ENCLOSED IN QUOTES, ASSUME BLANK.
CAUSE You did not enclose the edit word in quotation marks.
ACTION Add quotation marks to the edit word and recompile.
---------------------------------------------------------------------------------------
7011W MESSAGE THE NUMBER OF REPLACEABLE CHARACTERS IN THE EDIT WORD IS NOT EQUAL TO
THE FIELD TO BE EDITED.
CAUSE You did not specify an equal number of replaceable characters in the
edit word.
ACTION The compiler makes the number of characters in the source data equal
to the number of replaceable characters in the edit word, either by
truncating or padding with zeros. If you want this result, ignore
this warning message.
---------------------------------------------------------------------------------------
7012W MESSAGE INVALID EDIT CODE IN COL. 38.
CAUSE You entered a character other than X, Y, Z, 1, 2, 3, 4, A, B, C, D,
J, K, L, M, or blank in the Edit Code Field (column 38).
ACTION Enter a correct character and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
7013W MESSAGE EDIT CODE INVALID WITH CONSTANT OTHER THAN '*' OR '$'.
CAUSE You paired the wrong edit code with the constant that appears in
columns 45-70.
ACTION Correct this error and recompile.
---------------------------------------------------------------------------------------
7014W MESSAGE INVALID FIELD NAME IN COL 32-37.
CAUSE You used an invalid or undefined field name in the Field Name Field
(columns 32-37).
ACTION Correct the field name and recompile.
---------------------------------------------------------------------------------------
7015W MESSAGE INVALID LINE TYPE IN COL 15, ASSUME D.
CAUSE You used a character other than H, D, T, or E in the Type Field
(column 15).
ACTION Enter the proper character and recompile.
---------------------------------------------------------------------------------------
7016W MESSAGE INVALID FETCH-OVERFLOW OR RELEASE-FILE IN COL 16, ASSUME BLANK.
CAUSE You made an invalid entry in the Fetch Overflow/Release Field (column
16).
ACTION Correct this error and recompile.
---------------------------------------------------------------------------------------
7017W MESSAGE INVALID SPACE ENTRIES IN COL 17-18, ASSUME BLANK.
CAUSE You made an entry other than 0, 1, 2, 3, or blank in the Space Field
(columns 17-18).
ACTION Correct this entry and recompile.
---------------------------------------------------------------------------------------
7018W MESSAGE INVALID SKIP ENTRIES IN COL 19-22 OR GREATER THAN FORM LENGTH
SPECIFIED, ASSUME BLANK.
CAUSE You made entries other than 01-99, A0-A9, B0-B2 or blank in the Skip
Field (columns 19-22) or the entry in this field exceeds the form
length specified.
ACTION Correct this error and recompile.
---------------------------------------------------------------------------------------
7019W MESSAGE INVALID SKIP ENTRIES IN COL 19-22 OR CHANNEL NUMBER GREATER THAN 12,
ASSUME BLANK.
CAUSE You made invalid skip entries or referred to a channel number greater
than 12 in the Skip Field (columns 19-22).
ACTION Enter the correct skip request or channel number and recompile.
---------------------------------------------------------------------------------------
7020W MESSAGE INVALID NOT ENTRY IN COL. 23, 26, OR 29: ASSUME N.
CAUSE You entered a character other than N or blank in the Not Subfield
(columns 23, 26, or 29).
ACTION Leave the field blank or enter N and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
7022W MESSAGE INVALID OUTPUT INDICATOR IN COL. 24-25, 27-28, 30-31; ASSUME BLANK.
CAUSE You entered an invalid indicator in the Output Indicators Field
(columns 24-25, 27-28, or 30-31).
ACTION Enter a valid indicator and recompile.
---------------------------------------------------------------------------------------
7023W MESSAGE INVALID FIELD LENGTH FOR Y EDIT CODE.
CAUSE You specified a field less than 3 or greater than 6 digits long for
the Y edit code.
ACTION Redefine the field length to 3-6 digits.
---------------------------------------------------------------------------------------
7024W MESSAGE END POSITION NOT LARGE ENOUGH TO CONTAIN *PLACE FIELDS, OR ENTRY IS
INVALID.
CAUSE You entered a value in the End Position Field (columns 40-43), that
is too small to allow output of the *PLACE data without overlapping
the previous field.
ACTION Correct this error and recompile.
---------------------------------------------------------------------------------------
7027W MESSAGE MISSING OR INCORRECTLY SPECIFIED END POSITION IN COL. 40-43; ASSUME
END POSITION 1.
CAUSE You omitted the End Position Field (columns 40-43), or entered a
value in it other than 1 through 9999.
ACTION Enter the appropriate value in columns 40-43 and recompile.
---------------------------------------------------------------------------------------
7028W MESSAGE OUTPUT FILE DESCRIBED AS 'ADD' TYPE, EACH RECORD LINE MUST HAVE 'ADD'
IN COL. 16-18, ASSUME 'ADD'.
CAUSE You did not include ADD in columns 16-18 of each record line for an
output file to which new records are to be appended.
ACTION Correct this error and recompile.
---------------------------------------------------------------------------------------
7029W MESSAGE INVALID BLANK AFTER IN COL 39, ASSUME BLANK.
CAUSE You entered the Blank After Field with a constant, look-ahead field,
or special DATE field.
ACTION Remove this entry from the constant or field description and
recompile.
---------------------------------------------------------------------------------------
7030W MESSAGE INVALID CONSTANT IN COLUMNS 45-70.
CAUSE You entered an invalid constant in the Constant/Edit Word Field
(columns 45-70).
ACTION Define the constant properly and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
7031W MESSAGE INVALID PACKED/BINARY OUTPUT ENTRY IN COL 44, ASSUME BLANK.
CAUSE You made an entry to this field that applies to alphanumeric data but
the entry should apply to numeric data; or you entered a character
other than P, B, L, R, 2, or 4.
ACTION Correct this entry and recompile.
---------------------------------------------------------------------------------------
7032W MESSAGE OVERFLOW INDICATOR INVALID FOR AN EXCPT RECORD.
CAUSE You entered an overflow indicator in the Output Indicators Field
(columns 23-31) on an exception record.
ACTION Delete the overflow indicator and recompile.
---------------------------------------------------------------------------------------
7033W MESSAGE FETCH OVERFLOW INVALID WITH OVERFLOW INDICATOR ENTERED IN COL. 23-31;
ASSUME NO FETCH.
CAUSE You requested Fetch Overflow (column 16) in a line conditioned by an
overflow indicator.
ACTION Correct this error and recompile.
---------------------------------------------------------------------------------------
7034W MESSAGE OVERFLOW INDICATOR USED IS NOT ASSIGNED TO THIS FILE.
CAUSE You used an overflow indicator in the Output Indicators Field
(columns 23-31), but the indicator is not assigned to this file.
ACTION The compiler assumes that you assigned the indicator to this file.
If this is what you intend, ignore this message; otherwise, correct
the record and recompile.
---------------------------------------------------------------------------------------
7035W MESSAGE 1P INDICATOR INVALID WITH TOTAL OR EXCPT RECORDS.
CAUSE You used the first-page indicator to condition a total or exception
record.
ACTION Correct the record description and recompile.
---------------------------------------------------------------------------------------
7036W MESSAGE FETCH OVERFLOW INVALID WITH 1P INDICATOR, ASSUME NO FETCH OVERFLOW.
CAUSE You requested Fetch Overflow (column 16) for a record conditioned
with the first-page indicator.
ACTION Correct the error and recompile.
---------------------------------------------------------------------------------------
7037W MESSAGE 1P INDICATOR INVALID FOR A COMBINED FILE.
CAUSE You entered the first-page (1P) indicator for a combined file.
ACTION Correct the error and recompile.
---------------------------------------------------------------------------------------
7038W MESSAGE INVALID INDICATORS USED IN AN 'AND' RELATIONSHIP WITH 1P.
CAUSE You used an indicator with 1P in an AND relationship.
ACTION Correct this error and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
7039T MESSAGE END POSITION ENTRY IN COL. 40-43 FOR CONSTANT, EDIT WORD, FIELD, OR
ARRAY EXCEEDS RECORD LENGTH.
CAUSE You specified an end position for an output record that exceeds the
maximum length possible for that record. (For instance, position 150
for a printer record that has 132 characters per line.
ACTION Correct the end position to conform with the maximum length possible
and recompile.
---------------------------------------------------------------------------------------
7040W MESSAGE CONSTANTS IN COL. 45-70 INVALID FOR X, Y, OR Z EDIT CODES.
CAUSE You did not leave columns 45-70 blank for an X, Y, or Z edit code.
ACTION Remove the characters in columns 45-70 and recompile.
---------------------------------------------------------------------------------------
7041W MESSAGE DECIMAL POSITIONS INVALID FOR FIELD EDITED BY Y CODE.
CAUSE You applied the Y edit code to a non-integer numeric field.
ACTION Correct this error and recompile.
---------------------------------------------------------------------------------------
7042W MESSAGE NAME OF FIELD TO BE EDITED, BY CODE SPECIFIED IN COL 38, MISSING.
CAUSE You specified an edit code in column 38 but did not enter a field
name in columns 32-37.
ACTION Enter a field name in columns 32-37 and recompile.
---------------------------------------------------------------------------------------
7043T MESSAGE INVALID FILE TYPE FOR OUTPUT RECORD.
CAUSE You directed output to an input or display file.
ACTION Correct this error and recompile.
---------------------------------------------------------------------------------------
7044W MESSAGE T OR E ENTRY IN COL. 15 INVALID FOR COMBINED FILE.
CAUSE You directed total or exception records to a combined file.
ACTION Correct this error and recompile.
---------------------------------------------------------------------------------------
7045W MESSAGE BLANK AFTER ENTRY IN COL 39 INVALID WITH RESERVED WORD OTHER THAN
PAGE; ASSUME BLANK.
CAUSE You entered the Blank After Field with *PLACE, *PRINT, UDATE, UMONTH,
UYEAR, UDAY, or *ERROR.
ACTION Delete the blank after request from column 39.
---------------------------------------------------------------------------------------
7046W MESSAGE BLANK AFTER SPECIFIED FOR A CONSTANT.
CAUSE You tried to blank out a constant instead of a data field.
ACTION Correct this error and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
7047I MESSAGE FORMS POSITIONING SPECIFIED ON CONTROL RECORD, BUT MISSING A RECORD
CONDITIONED BY 1P.
CAUSE You entered a 1 in the Form Positioning Field (column 41) of the
Header Specification, but did not specify an output record
conditioned by the first-page indicator (1P).
ACTION This is an informational message only, no action is necessary.
---------------------------------------------------------------------------------------
7048W MESSAGE 'ADD' IN COL 16-18 NOT ALLOWED ON AND/OR LINES, ASSUME BLANK.
CAUSE You used ADD on an AND or OR line.
ACTION Remove the ADD and recompile.
---------------------------------------------------------------------------------------
7049W MESSAGE INVALID ENTRY IN COL. 17-22 FOR 'AND' LINE, ASSUME BLANK.
CAUSE You entered one or more characters in columns 17-22 on an AND line.
ACTION Remove the characters from these columns and recompile.
---------------------------------------------------------------------------------------
7050W MESSAGE INVALID INDEX IN COLS. 32-37.
CAUSE You used an improper array index in the Field Name Field.
ACTION Correct the invalid index and recompile.
---------------------------------------------------------------------------------------
7053W MESSAGE ALPHANUMERIC DATA CANNOT BE EDITED.
CAUSE You attempted to apply an edit code or edit word to alphanumeric
data, but they can only be used with numeric data.
ACTION Correct this record and recompile.
---------------------------------------------------------------------------------------
7054W MESSAGE PACKED/BINARY IN COLUMN 44 CANNOT APPEAR TOGETHER WITH EDIT CODE OR
EDIT WORD.
CAUSE You attempted to apply a packed binary field to an edit code or edit
word.
ACTION Correct this error and recompile.
---------------------------------------------------------------------------------------
7055W MESSAGE END POSITION SPECIFIED IN COLUMNS 40-43 CANNOT CONTAIN THE WHOLE DATA
ITEM.
CAUSE You did not specify an edit field long enough to hold the entire
edited item.
ACTION Specify the proper field length and recompile.
---------------------------------------------------------------------------------------
7056W MESSAGE PACKED/BINARY IN COLUMN 44 IS NOT BLANK FOR ALPHANUMERIC DATA, ASSUME
BLANK.
CAUSE You specified numeric data (column 44) but defined the field
previously as alphanumeric.
ACTION Correct this error and recompile.
---------------------------------------------------------------------------------------