HP 3000 Manuals HP 3000 Manuals
Message Types (Cont.)
---------------------------------------------------------------------------------------
2093W MESSAGE FORMS DOWN-LOAD VALUE IN COLUMNS 60-62 MUST BE 1-255, ASSUME 1.
CAUSE You specified an incorrect entry for columns 60-62 (the entry may not
be right-justified).
ACTION The compiler assumes 1.
---------------------------------------------------------------------------------------
2094I MESSAGE BUFCHK 'CURRENT DATA CHECK' DISABLED FOR IMAGE FILE.
CAUSE You specified a BUFCHK Continuation line for a TurboIMAGE file. This
sequence is invalid.
ACTION The compiler disables the CURRENT DATA CHECK option for this file
specification.
---------------------------------------------------------------------------------------
2095W MESSAGE KEYFL SPEC CONTAINS INVALID PARAMETER(S), OR IS SPECIFIED FOR A
NON-KSAM FILE.
CAUSE Columns 68-70 contained invalid parameter information or you
specified the KEYFL Continuation line for a non-KSAM file.
ACTION The compiler disregards your entry. Correct the program and
recompile.
---------------------------------------------------------------------------------------
2096W MESSAGE WORKSTN INTERFACE TYPE NOT BLANK, R, OR C, ASSUME BLANK.
CAUSE You entered an incorrect value in column 47 of the File Description
Specification.
ACTION The compiler assumes blank.
---------------------------------------------------------------------------------------
2098W MESSAGE FORMDL MESSAGE NOT SPECIFIED PRIOR TO LOADFM OPTION - ASSUME NO.
DOWNLOADED IS 1.
CAUSE A FORMDL Specification must precede a LOADFM Specification.
ACTION The compiler assumes that one form is to be loaded.
---------------------------------------------------------------------------------------
2100W MESSAGE INVALID ERROR OPTION ON KFATAL RECORD, DEFAULTING TO 0.
CAUSE You entered an option number that was not 0-5.
ACTION The compiler assumes option 0.
---------------------------------------------------------------------------------------
2101T MESSAGE KSTATUS MUST ALSO BE SPECIFIED FOR FILES USING THE KFATAL OPTION.
CAUSE A KSTATUS record for this file was not found, although a KFATAL
record was used.
ACTION Add a KSTATUS record for the file and recompile.
---------------------------------------------------------------------------------------
3001T MESSAGE TO FILENAME (COLUMNS 19-26) INVALID OR UNDEFINED - RECORD IGNORED.
CAUSE You entered an invalid or undefined file name in the To File Name
Field (columns 19-26). (An undefined file name is one that does not
appear in the File Description Specifications.)
ACTION Define the To File Name and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
3002T MESSAGE FROM FILENAME (COLUMNS 11-18) INVALID OR UNDEFINED - RECORD IGNORED.
CAUSE You entered an invalid or undefined file name in the From File Name
Field (columns 11-18). (An undefined file name is one that does not
appear in the File Description Specifications.)
ACTION Define the correct From File Name and recompile.
---------------------------------------------------------------------------------------
3003W MESSAGE E NOT SPECIFIED ON FILE DESCRIPTIONS FOR FROM FILE.
CAUSE You did not enter an E on the File Description Specification (column
39) for the From File Name Field (columns 11-18).
ACTION Enter an E in column 39 of the File Description Specification for the
From File.
---------------------------------------------------------------------------------------
3004T MESSAGE FROM FILE IS NOT AN INPUT FILE - RECORD IGNORED.
CAUSE You specified a non-input file in the From File Name Field (column
11-18).
ACTION Enter the correct file in the From File Name Field and recompile.
---------------------------------------------------------------------------------------
3005W MESSAGE CHAINING OR RECORD ADDRESS FILE AND COLUMNS 33-57 NON BLANK. BLANK
ASSUMED.
CAUSE You entered data in columns 33-57, which should remain blank for
chaining or Record Address Files.
ACTION Remove the data from columns 33-57.
---------------------------------------------------------------------------------------
3006T MESSAGE CHAINING FIELD NUMBER (COLUMN 10) NOT 1-9 - RECORD IGNORED.
CAUSE You entered a character other than one of the digits 0 through 9 in
column 10.
ACTION Specify the correct digit and recompile.
---------------------------------------------------------------------------------------
3007W MESSAGE CHAINING FIELD CODE (COLUMN 9) NOT C-ASSUME C.
CAUSE You did not enter a C in column 9 of the Chaining Field Code Field
(columns 9-10).
ACTION The compiler assumes you entered a C in column 9, and combines this
with the digit in column 10 to form the chaining code. Correct
column 9.
---------------------------------------------------------------------------------------
3008T MESSAGE CHAINING CODE AND FROM FILE PREVIOUSLY SPECIFIED - RECORD IGNORED.
CAUSE You previously specified the chaining code in the Chaining Field Code
Fields (columns 9-10) and the from file in the From File Name Field
(columns 11-18).
ACTION The compiler ignores the specification. Remove the duplicate
chaining description.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
3009T MESSAGE TO FILE NOT A CHAINED OR RANDOM FILE - RECORD IGNORED.
CAUSE You did not specify a chained or direct-access file in the To File
Name Field.
ACTION Specify the correct type of file and recompile.
---------------------------------------------------------------------------------------
3013T MESSAGE RECORD ADDRESS FILE PREVIOUSLY SPECIFIED ON EXTENSION SPECIFICATION -
RECORD IGNORED.
CAUSE You specified a record address file in a previous File Extension
Specification.
ACTION Set up program so that there is only one record address file.
---------------------------------------------------------------------------------------
3014T MESSAGE TO FILENAME (COLUMNS 19-26) MISSING FOR CHAINING OR RAF -
SPECIFICATION IGNORED.
CAUSE You did not enter a file name in the To File Name Field (columns
19-26) for the chaining file or the Record Address File you
specified.
ACTION Specify the file name and recompile.
---------------------------------------------------------------------------------------
3015T MESSAGE TABLE/ARRAY NAME (COLUMNS 27-32) PREVIOUSLY DEFINED - RECORD IGNORED.
CAUSE You previously defined the table/array name in the Table/Array Name
Field (column 27-32).
ACTION Change the name and recompile.
---------------------------------------------------------------------------------------
3016T MESSAGE ENTRIES PER RECORD (COLUMNS 33-35) INVALID - ASSUME 1.
CAUSE You specified an invalid number of entries in one record in the
Entries Per Record Field (columns 33-35). (The number of entries
must be from 1 to 999.)
ACTION The compiler ignores your entry and assumes you entered a 1. Enter
valid numeric characters, right-justified with no embedded blanks,
and recompile.
---------------------------------------------------------------------------------------
3017T MESSAGE ENTRIES PER TABLE/ARRAY (COLUMNS 36-39) INVALID - ASSUME 1.
CAUSE You entered an invalid number of entries in the Entries Per
Table/Array Field (columns 36-39). The number of entries must be
1-9999.
ACTION The compiler ignores your entry and assumes you entered a 1. Enter
valid numeric characters, right-adjusted with no embedded blanks, and
recompile.
---------------------------------------------------------------------------------------
3018W MESSAGE P/B/L/R FIELD (COLUMN 43) INVALID - BLANK ASSUMED.
CAUSE You entered a character other than P, B, L or R, in the Data Format
Field (column 43).
ACTION The compiler ignores your entry and assumes you left it blank. Enter
a valid character in this field.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
3019W MESSAGE FIELD SIZE OF 1 NOT ALLOWED WITH L OR R SPECIFIED IN COLUMN 43 - 2
ASSUMED.
CAUSE You specified a field size of 1 in the Entry Length Field (column
40-42) with an L or R format in the Data Format Field (column 43).
ACTION The compiler ignores your entry and assumes you specified a field
size of 2 characters. Specify a field size of at least 2 characters.
---------------------------------------------------------------------------------------
3020T MESSAGE FIELD SIZE (COLUMNS 40-42) BLANK OR INVALID - 1 ASSUMED.
CAUSE You entered an invalid field size or left the Entry Length Field
(columns 40-42) blank.
ACTION The compiler ignores your entry and assumes you specified a field
size of 1 character. Enter valid numbers, right-adjusted with no
embedded blanks.
---------------------------------------------------------------------------------------
3021W MESSAGE DECIMAL POSITIONS (COLUMN 44) INVALID - ASSUME NUMERIC WITH ZERO
DECIMAL POSITIONS.
CAUSE You entered an invalid number of digit positions to the right of the
decimal point in the Decimal Positions Field (column 44).
ACTION The compiler ignores your entry and assumes a numeric table with zero
decimal position. Enter a digit (0 to 9) in this field.
---------------------------------------------------------------------------------------
3022W MESSAGE P, B, L, OR R SPECIFIED (COLUMN 43) AND BLANK DECIMAL POSITIONS -
ASSUME NUMERIC WITH ZERO DECIMALS.
CAUSE You entered a P, B, L, or R in the Data Format Field (column 43) and
left the Decimal Positions Field (column 44) blank.
ACTION The compiler ignores your entry and assumes a numeric table/array
with zero decimal positions. Either enter a blank in column 43 or a
digit (0-9) in column 44.
---------------------------------------------------------------------------------------
3023T MESSAGE DECIMAL POSITIONS (COLUMN 44) GREATER THAN NUMBER OF DIGITS - ASSUME
EQUAL.
CAUSE You specified more digits to the right of the decimal in the Decimal
Positions Field (column 44) than there are positions.
ACTION The compiler ignores your entry and assumes that the number of
decimal positions equals the number of digit positions. Change
either the decimal positions or the number of digits and recompile.
---------------------------------------------------------------------------------------
3024W MESSAGE SEQUENCE (COLUMN 45) NOT BLANK, A OR D - A ASSUMED.
CAUSE You entered a letter or digit, other than an A or D, in the
Table/Array Sequence Field (column 45).
ACTION The compiler ignores your entry and assumes you entered an A (for
ascending sequence).
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
3025T MESSAGE FIELD NAME (COLUMNS 27-32) BLANK OR INVALID - ENTRY IGNORED.
CAUSE You entered an invalid table or array name or left the Table/Array
Field (column 27-32) blank.
ACTION The compiler ignores your entry. Enter a valid field name and
recompile.
---------------------------------------------------------------------------------------
3026T MESSAGE BINARY FIELD NOT LENGTH 5 OR 10.
CAUSE You specified a binary field which is neither 5 or 10 digits long.
ACTION Redefine the field so that it is either 5 or 10 digits long.
---------------------------------------------------------------------------------------
3027T MESSAGE TO FILE (COLUMNS 19-26) NOT AN OUTPUT FILE - TO FILE IGNORED.
CAUSE You specified the To File as something other than an Output File in
its File Description Specification.
ACTION The compiler ignores To File Name entry. Enter a valid output file
name or blanks and recompile.
---------------------------------------------------------------------------------------
3028W MESSAGE P/B/L/R FIELD (COLUMN 55) INVALID - BLANK ASSUMED.
CAUSE You entered a character other than P, B, L, or R in the Data Format
Field (column 55).
ACTION The compiler ignores your entry and assumes you left the field blank.
Correct this field to the proper field format (P, B, L, or R).
---------------------------------------------------------------------------------------
3029W MESSAGE FIELD SIZE OF 1 NOT ALLOWED WITH L OR R SPECIFIED IN COLUMN 55 - 2
ASSUMED.
CAUSE You specified a field size of 1 in the Entry Length Field (columns
52-54) with an L or R format in the Data Format Field (column 55).
ACTION The compiler ignores your entry and assumes you specified a field
size of 2 characters. Enter a field size of at least two characters.
---------------------------------------------------------------------------------------
3030T MESSAGE FIELD SIZE (COLUMNS 52-54) BLANK OR INVALID - 1 ASSUMED.
CAUSE You entered an invalid field size or left the Entry Length Field
(columns 52-54) blank.
ACTION The compiler ignores your entry and assumes you specified a field
size of 1 character. Enter valid numeric characters, right-adjusted
with no embedded blanks.
---------------------------------------------------------------------------------------
3031T MESSAGE ALPHA FIELD SIZE GREATER THAN 256 - ASSUME 256.
CAUSE You entered an alphanumeric field size in the Entry Length Field
(columns 40-42 or columns 52-54) that is greater than 256 characters.
ACTION The compiler ignores your entry and assumes you entered 256
characters. Enter a field size of 256 or less.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
3032T MESSAGE NUMERIC FIELD SIZE GREATER THAN 15 - ASSUME 15.
CAUSE You entered a numeric field size in the Entry Length Field (columns
40-42 or columns 52-54) greater than 15 digits.
ACTION The compiler ignores your entry and assumes you entered 15 digits.
Either define this field as an alphanumeric field or change the
number of digits to 15 or less.
---------------------------------------------------------------------------------------
3033W MESSAGE DECIMAL POSITIONS (COLUMN 56) INVALID - ASSUME NUMERIC WITH ZERO
DECIMAL POSITIONS.
CAUSE You specified an invalid number of digits to the right of the decimal
point in the Decimal Positions Field (column 56).
ACTION The compiler ignores your entry and assumes numeric data with zero
decimal positions. Enter 0-9 in this field.
---------------------------------------------------------------------------------------
3034W MESSAGE P, B, L, OR R SPECIFIED (COLUMN 55) AND BLANK DECIMAL POSITIONS -
ASSUME NUMERIC WITH ZERO DECIMALS.
CAUSE You specified a P, B, L or R in the Data Format Field (column 55) and
left the Decimal Positions Field (column 56) blank.
ACTION The compiler ignores your entry and assumes a numeric table/array
with zero decimal positions. Either enter a blank in column 55 or
0-9 in column 56.
---------------------------------------------------------------------------------------
3035T MESSAGE DECIMAL POSITIONS (COLUMN 56) GREATER THAN NUMBER OF DIGITS - ASSUME
EQUAL.
CAUSE You specified more positions to the right of the decimal in the
Decimal Positions Field (column 56) than there are digits.
ACTION The compiler ignores your entry and assumes the number of decimal
positions equals the number of digits. Change either the number of
decimal positions or the field length.
---------------------------------------------------------------------------------------
3036W MESSAGE SEQUENCE (COLUMN 57) NOT BLANK, A, OR D - A ASSUMED.
CAUSE You entered a letter or digit, other than an A or D, in the
Table/Array Sequence Field (column 57).
ACTION The compiler ignores your entry and assumes you entered an A (for
ascending sequence).
---------------------------------------------------------------------------------------
3037T MESSAGE FIELD NAME (COLUMNS 46-51) BLANK OR INVALID - ENTRY IGNORED.
CAUSE You entered an invalid table or array name or left the Alternating
Table/Array Name Field (column 46-51) blank.
ACTION Enter the correct name and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
3038T MESSAGE TABLE/ARRAY NAME (COLUMNS 46-51) PREVIOUSLY DEFINED - RECORD IGNORED.
CAUSE You previously used this table or array name in the Alternating
Table/Array Name Field (columns 46-51).
ACTION The compiler ignores the record entry; change the name and recompile.
---------------------------------------------------------------------------------------
3039W MESSAGE NO EXTENSION SPECIFICATION FOR FILE WITH E IN COLUMN 39 OF FILE
SPECIFICATION.
CAUSE The program uses a table, array, chaining file or RAF but there is no
File Extension Specification that describes it.
ACTION Insert the File Extension Specification and recompile the program.
---------------------------------------------------------------------------------------
3040W MESSAGE ENTRIES PER RECORD BLANK AND FILENAME SPECIFIED - ASSUME 1.
CAUSE You did not specify the number of entries per record, yet you
specified the file name in the Table/Array Name Field (column 27-32).
ACTION The compiler ignores the entry and assumes you specified 1 entry per
record. Enter valid numeric characters, right-adjusted with no
embedded blanks.
---------------------------------------------------------------------------------------
3041I MESSAGE EXTENSION SPECIFICATION BLANK - IGNORE RECORD.
CAUSE You did not enter any information in this specification.
ACTION The compiler ignores the record; enter valid file names in the From
File Name Field and the To File Name Field.
---------------------------------------------------------------------------------------
3042W MESSAGE ENTRIES PER RECORD GREATER THAN TABLE SIZE - ASSUME ENTRIES REVERSED.
CAUSE You specified a greater number of entries in one record of the table
(Entries Per Record Field, columns 33-35) than the number of entries
in the entire table (Entries Per Table/Array Field, columns 36-39).
ACTION The compiler ignores your entry and assumes the entries are reversed
(the table size is greater than the entries per record). Enter the
correct number of entries per record and table size, and recompile.
---------------------------------------------------------------------------------------
3043T MESSAGE FROM FILE RECORD LENGTH NOT LARGE ENOUGH TO HOLD ENTRIES PER RECORD.
CAUSE You specified a number of entries per record (columns 33-35) that
exceeds the space allotted by the length of the records in the From
File.
ACTION Enter the number of entries per record and recompile.
---------------------------------------------------------------------------------------
3044T MESSAGE TO FILE RECORD LENGTH NOT LARGE ENOUGH TO HOLD ENTRIES PER RECORD.
CAUSE You specified a number of entries per record (columns 33-35) that
exceeds the space allotted by the length of the records in the To
File.
ACTION Enter the number of entries per record and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
4001W MESSAGE INVALID, MISSING, OR UNDEFINED FILENAME IN COLUMNS 7-14, SPEC IS
DROPPED.
CAUSE You specified a file name in the File Name Field (columns 7-14) that
was invalid or undefined or you omitted this file name completely.
ACTION Include the correct file name and recompile.
---------------------------------------------------------------------------------------
4002W MESSAGE FILENAME IN COLUMNS 7-14 DOES NOT REFER TO 'L' EXTENSION CODE.
CAUSE You specified a file name in the File Name Field (columns 7-14) that
is not defined in the File Description Specifications or you
specified it in the File Description but failed to specify L in
column 39.
ACTION Define the correct file name and recompile.
---------------------------------------------------------------------------------------
4003W MESSAGE LINE NO. ENTRY IN COL 15-17 INVALID, LESS THAN 1. OR GREATER THAN
112.
CAUSE You specified an invalid line number or a number greater than 112 in
the Line Number Field (columns 15-17).
ACTION The compiler ignores your entry and assumes line number 66.
---------------------------------------------------------------------------------------
4004W MESSAGE INVALID OR MISSING ENTRY IN COLUMNS 18-19, ASSUME FL.
CAUSE You entered characters other than OL or FL or a number between 1 and
12 in the Channel Number/OL Field (columns 18-19), or left this field
blank.
ACTION The compiler ignores your entry and assumes you entered FL (for Form
Length).
---------------------------------------------------------------------------------------
4005W MESSAGE LINE NO. ENTRY IN COL 20-22 INVALID, LESS THAN 1, OR GREATER THAN
112.
CAUSE You entered an invalid overflow line or specified a line number
greater than 112 in the Channel Number/OL Field (columns 20-24).
ACTION The compiler assumes line number 66. Correct the entry and
recompile.
---------------------------------------------------------------------------------------
4006W MESSAGE INVALID OR MISSING OL ENTRY IN COLUMN 23-24, ASSUME OL.
CAUSE You entered characters other than OL or FL or a number between 01 and
12 in the Line Number and OL/FL Field (columns 23-24) or left this
field blank.
ACTION The compiler assumes OL. Correct the entry and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
4007W MESSAGE OVERFLOW LINE EXCEEDS FORM LENGTH; ASSUME FORM LENGTH.
CAUSE You specified an overflow line in the Line Number Field (column
20-22) that exceeds the form length in the previous Line Number Field
(columns 15-17).
ACTION The compiler assumes that the form length line and overflow line are
equal.
---------------------------------------------------------------------------------------
4008W MESSAGE LINE NUMBER ENTRY IS INVALID, PREVIOUS SPEC. OR DEFAULT IS USED.
CAUSE You specified an invalid line number.
ACTION The compiler ignores your entry.
---------------------------------------------------------------------------------------
4009W MESSAGE CHANNEL NUMBER ENTRY IS INVALID, LINE NO. ENTRY IGNORED.
CAUSE You specified an invalid channel number.
ACTION The compiler ignores your entry.
---------------------------------------------------------------------------------------
4011W MESSAGE MULTIPLE LINE COUNTER SPECIFICATION FOR SAME FILE IS DROPPED.
CAUSE You included more than one Line Counter Specification for the same
channel, form length or overflow line.
ACTION The compiler ignores the second Line Counter Specification.
---------------------------------------------------------------------------------------
4012W MESSAGE COLUMNS 25-74 SHOULD BE BLANK.
CAUSE You entered data in columns 25-74 when using the Line Number Option
of the Line Counter Specifications.
ACTION The compiler ignores the entries in columns 25-74 and assumes you
left these columns blank.
---------------------------------------------------------------------------------------
4013W MESSAGE NO LINE SPECIFICATION FOR FILE WITH L IN COLUMN 39 OF FILE
SPECIFICATION.
CAUSE You entered L in column 39 of a File Description Specification that
has no associated Line Counter Specification.
ACTION Correct the entry and recompile the program.
---------------------------------------------------------------------------------------
4015W MESSAGE NO ENTRIES IN L-SPEC RECORD.
CAUSE You entered a file name with no other entries in this specification.
ACTION The compiler ignores this specification.
---------------------------------------------------------------------------------------
4016W MESSAGE ENTRIES AFTER 1ST BLANKS ON L-SPEC IGNORED.
CAUSE When processing channel specifications, processing stops when the
first blank line no./channel no. pair is found. The compiler then
checks to see if the remainder of the specification is blank.
ACTION The compiler ignores non-blank trailing entries.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
4017W MESSAGE MULTIPLE FL USAGE; ASSUME COLS 23-24 ARE OL.
CAUSE Columns 18-19 and 23-24 both contain FL.
ACTION The line number in columns 20-22 is used as the OL line.
---------------------------------------------------------------------------------------
4018W MESSAGE MULTIPLE OL USAGE; ASSUME COLS 18-19 ARE FL.
CAUSE Columns 18-19 and 23-24 both contain OL.
ACTION The line number in columns 15-17 is used as the FL line.
---------------------------------------------------------------------------------------
5001T MESSAGE INVALID OR UNDEFINED FILENAME - DISK FILE ASSUMED.
CAUSE You entered, in the File Name Field (columns 7-14), an invalid file
name or a name that is not defined in the File Description
Specifications.
ACTION Specify the correct file name or include a File Description
Specification for it.
---------------------------------------------------------------------------------------
5002T MESSAGE FILE IS NOT AN INPUT, UPDATE, OR COMBINED FILE - INPUT ASSUMED.
CAUSE You entered a file name that does not identify an input, update, or
combined file.
ACTION Correct the File Description Specification to identify an input,
update, or combined file.
---------------------------------------------------------------------------------------
5003T MESSAGE AND/OR LINE CANNOT FOLLOW TRAILER OR LOOK-AHEAD.
CAUSE You entered an AND or OR line after specifying a trailer or
look-ahead record in the Record Indicator/Look-Ahead/Trailer/Data
Structure Field (columns 19-20).
ACTION Remove the AND or OR line.
---------------------------------------------------------------------------------------
5004T MESSAGE AND/OR LINE DOES NOT FOLLOW RECORD IDENTIFICATION LINE.
CAUSE You did not specify a record to which this AND/OR line applies.
ACTION Enter the first line of the record identification for this record.
5005W MESSAGE AND/OR LINE FOLLOWS LINE WITHOUT RECORD IDENTIFICATION CODES.
CAUSE You did not include record identification codes in columns 21-41 on
the previous line.
ACTION Enter the record identification codes (C,Z,D) on the previous line.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
5006W MESSAGE AND/OR LINE AND NUMBER/OPTION (COLUMNS 17-18) NOT BLANK.
CAUSE You entered AND or OR in columns 14-16 and on the same specification
line you entered a value in the Number of Records Field (column 17)
or Option Field (column 18).
ACTION Enter the Number of Records or Option Fields on a different
specification line from the AND/OR line, then recompile.
---------------------------------------------------------------------------------------
5007W MESSAGE AND LINE AND RECORD INDICATOR (COLUMNS 19-20) NOT BLANK.
CAUSE You entered an AND line and a record indicator in the Record
Indicator/Look-Ahead/Trailer/Data Structure Field (columns 19-20).
ACTION Enter a record indicator on a separate specification line from the
AND line, then recompile.
---------------------------------------------------------------------------------------
5009T MESSAGE TRAILER HEADER DOES NOT CONTAIN ALPHA SEQUENCE OR NUMERIC WITH N.
CAUSE You specified a trailer record and the previous record identification
specification contained a numeric sequence entry, but did not contain
N in column 17.
ACTION On the previous record identification specification, enter N in
column 17 or specify an alphabetic sequence entry.
---------------------------------------------------------------------------------------
5010W MESSAGE COLS. 7-14, 17, 18, 21-70 FOR LOOK-AHEAD OR 7-18, 21-70 FOR TR MUST
BE BLANK.
CAUSE You entered data in the wrong fields in the description of a spread
or look-ahead record or entered the file name or group sequence in a
spread record description.
ACTION Remove the data from all columns that should be blank.
---------------------------------------------------------------------------------------
5011T MESSAGE PREVIOUS LOOK-AHEAD FOR FILE.
CAUSE You defined more than one look-ahead record for a file, but only one
is allowed.
ACTION Remove one of the look-ahead records (consolidate them).
---------------------------------------------------------------------------------------
5012W MESSAGE LOOK AHEAD RECORD HAS NON-ALPHA SEQUENCE NUMBER (COLUMNS 15-16).
CAUSE You specified a numeric sequence for a look-ahead record.
ACTION Change the sequence characters (in columns 15-16) to alphabetic
characters.
---------------------------------------------------------------------------------------
5013W MESSAGE ALPHA SEQUENCE (COLUMNS 15-16) FOLLOWS NUMERIC - ASSUME NUMERIC.
CAUSE You listed the numeric sequence entries before the alphabetic entries
in the Group Sequence Field (columns 15-16)
ACTION The compiler ignores your sequence entry and assumes a numeric
sequence. Move the alphabetic sequence specifications so that they
come before the numeric sequence specifications.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
5014W MESSAGE NUMBER/OPTION FIELDS (COLUMNS 17-18) NOT BLANK FOR ALPHA SEQUENCE -
ASSUME BLANK.
CAUSE You entered an option in the Option Field (column 17) or indicated
the number of records in the Number of Records Field (column 18) and
also specified an alphabetic sequence in the Group Sequence Field
(column 15-16).
ACTION The compiler ignores your entry and assumes you left the Number of
Records Field blank. Either change the alphabetic sequence
characters (columns 25-26) to numeric characters or set columns 17-18
blank.
---------------------------------------------------------------------------------------
5015W MESSAGE INVALID SEQUENCE NUMBER (COLUMNS 15-16) - ASSUME ALPHA SEQUENCE.
CAUSE You entered an invalid sequence number in the Group Sequence Field
(column 15-16), and the previous sequence characters were alphabetic.
ACTION The compiler ignores your sequence number and assumes you entered an
alphabetic sequence. Correct the sequence number.
---------------------------------------------------------------------------------------
5016W MESSAGE INVALID SEQUENCE NUMBER (COLUMNS 15-16) - ASSUME NUMERIC SEQUENCE.
CAUSE You entered an invalid sequence number in the Group Sequence Field
(columns 15-16) and the previous sequence characters were numeric.
ACTION The compiler ignores your sequence number and assumes you specified a
numeric sequence. Correct the sequence number.
---------------------------------------------------------------------------------------
5017T MESSAGE SEQUENCE (COLUMNS 15-16) NOT ASCENDING - ASSUME ASCENDING SEQUENCE.
CAUSE Your numeric sequence character group was not higher than the
previous sequence number.
ACTION The compiler ignores your sequence and assumes ascending sequence.
Correct the numeric sequence character group to fall in proper
ascending sequence.
---------------------------------------------------------------------------------------
5018W MESSAGE FIRST NUMERIC SEQUENCE NOT 1 - ASSUME 1.
CAUSE You didn't assign the first sequence as 01 in the Group Sequence
Field (columns 15-16).
ACTION The compiler ignores your sequence number and assumes you entered 01.
Correct the first numeric sequence character group.
---------------------------------------------------------------------------------------
5019T MESSAGE NUMBER FIELD (COLUMN 17) NOT 1 OR N WITH NUMERIC SEQUENCE -ASSUME N.
CAUSE You entered a character other than an N or 1, in the Number of
Records Field (column 17) and specified numeric sequencing.
ACTION The compiler ignores your entry and assumes you entered an N. Correct
the Number of Records entry.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
5021T MESSAGE INVALID RECORD IDENTIFICATION INDICATOR.
CAUSE You used an invalid indicator in the Record Indicator Field (columns
19-20).
ACTION In columns 19-20, enter one of the indicators: 01-99, F0-F9, H0-H9,
KA-KN, KP-KY, L1-L9, LR, MR, OA-OG, OV, 1P, U1-U8.
---------------------------------------------------------------------------------------
5023T MESSAGE INVALID RECORD IDENTIFICATION CODE POSITION FIELD (COLUMNS 21-24,
28-31, OR 35-38) - ASSUME 1.
CAUSE You specified invalid numbers or embedded blanks in the Record
Identification Codes Field (columns 21-24, 28-31, or 35-38).
ACTION Correct the field to include valid numeric characters,
right-adjusted.
---------------------------------------------------------------------------------------
5024T MESSAGE RECORD ID CODE POSITION (COLUMNS 21-24, 28-31, OR 35-38) NOT WITHIN
RECORD LENGTH - ASSUME 1.
CAUSE You specified a record identification code in the Record
Identification Codes Field (columns 21-24, 28-31, or 35-38) that
doesn't fall within the record length defined.
ACTION The compiler ignores the entry and assumes you entered a 1 in the
field. Correct the field so that it falls within the record length.
---------------------------------------------------------------------------------------
5025W MESSAGE NOT FIELD (COLUMNS 25, 32, OR 39) NOT BLANK OR N - ASSUME N.
CAUSE You specified a character other than N in columns 25, 32, or 39.
ACTION Enter an N or a blank in the field.
---------------------------------------------------------------------------------------
5026W MESSAGE C/Z/D FIELD (COLUMNS 23, 33, OR 40) NOT C, Z, OR D - ASSUME C.
CAUSE You entered a letter or digit other than a C, Z, or D, in column 26,
33, or 40.
ACTION The compiler ignores the entry and assumes you entered a C. Change
the entry to C, Z, or D.
---------------------------------------------------------------------------------------
5027I MESSAGE NO FIELD DESCRIPTIONS FOR PREVIOUS RECORD.
CAUSE You followed one record description specification with another,
without an intervening field description specification.
ACTION This entry is probably valid. However, the compiler issues the
message just in case this is an AND/OR line or in case you forgot to
include field descriptions for the previous record.
---------------------------------------------------------------------------------------
5028W MESSAGE COLUMNS 43-70 NON-BLANK FOR RECORD DESCRIPTION.
CAUSE You entered data in columns 43-70 in a record description
specification.
ACTION The compiler ignores the data in columns 43-70. Remove the data from
these columns.
---------------------------------------------------------------------------------------