HP 3000 Manuals HP 3000 Manuals
Message Types (Cont)
---------------------------------------------------------------------------------------
2006W MESSAGE FILE FORMAT IN COLUMN 19 IS INVALID, ASSUME F.
CAUSE You entered an invalid file format in the Record Format Field (column
19).
ACTION The compiler ignores your entry and assumes the records in the file
are fixed-length.
---------------------------------------------------------------------------------------
2007W MESSAGE INVALID BLOCK LENGTH IN COLUMNS 20-23, ASSUME EQUAL TO RECORD LENGTH.
CAUSE You entered a block length in the Block Length Field (columns 20-23)
other than 1-9999 or blank.
ACTION The compiler ignores your entry and assumes the block length and
record length are equal. Correct the block length if necessary.
---------------------------------------------------------------------------------------
2008W MESSAGE INVALID RECORD LENGTH IN COLUMNS 24-27, ASSUME RECORD LENGTH OF 80.
CAUSE You entered a record length in the Logical Record Length Field
(columns 24-27) other than 1 through 9999.
ACTION The compiler ignores your entry and assumes the record length is 80
characters. Correct the record length.
---------------------------------------------------------------------------------------
2009T MESSAGE INVALID MODE OF PROCESSING ENTRY IN COLUMN 28.
CAUSE You entered a character other than L or R in the Processing Mode
Field (column 28).
ACTION The compiler ignores your entry and assumes sequential processing.
Enter a correct value (L or R) for the processing mode.
---------------------------------------------------------------------------------------
2010T MESSAGE INVALID LENGTH OF KEY FIELD OR RECORD ADDRESS FIELD IN COLUMNS 29-30.
CAUSE You entered a key length other than 1-99 or blank in the Record
Address or Key Field Length Fields (columns 29-30).
ACTION The compiler ignores your entry and assumes that the key length is
equal to 3.
---------------------------------------------------------------------------------------
2011W MESSAGE INVALID RECORD ADDRESS TYPE ENTRY IN COLUMN 31, ASSUME BLANK.
CAUSE You entered a character other than A, P, K, or I in the Record
Address Type Field (column 31).
ACTION The compiler ignores your entry and assumes you left it blank, for a
direct-access file not processed by a chaining file or RAF. For
example, to specify processing with a chaining file or RAF by record
number, change the entry to I.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
2012W MESSAGE INVALID ENTRY IN COLUMN 32, ASSUME BLANK.
CAUSE You entered a character other than I, X, S, T, M, 1-9, D, or C in the
File Organization/Additional I/O Area Field (column 32).
ACTION The compiler ignores your entry and assumes you left it blank,
requesting two buffers.
---------------------------------------------------------------------------------------
2013W MESSAGE INVALID OVERFLOW INDICATOR IN COLUMNS 33-34, ASSUME BLANK.
CAUSE You entered an invalid overflow indicator in the Overflow Indicator
Field (columns 33-34).
ACTION The compiler ignores your entry and assumes you left this field blank
(no indicator assigned). To specify an indicator, enter OA-OG or OV.
---------------------------------------------------------------------------------------
2014W MESSAGE INVALID KEY FIELD LOCATION IN COLUMNS 35-38.
CAUSE You entered an invalid value in the Key Field Starting Location Field
(columns 35-38).
ACTION The compiler ignores your entry and assumes a key field starting
location of 0.
---------------------------------------------------------------------------------------
2015T MESSAGE IF YOU WISH TO PROCESS YOUR OWN LABELS, COLUMN 53 MUST BE E OR 2-9.
CAUSE You entered a character other than E or the digits 2-9 to process
your own labels.
ACTION The compiler assumes no user label processing. To process labels,
enter E or 2-9.
---------------------------------------------------------------------------------------
2016W MESSAGE COLUMNS 48-49 ARE NOT BLANK.
CAUSE You entered invalid data in columns 48-49 (not used by RPG).
ACTION The compiler ignores your entry and assumes you left these columns
blank.
---------------------------------------------------------------------------------------
2017W MESSAGE INVALID ENTRY IN COLUMN 53.
CAUSE You entered a character, other than an S, E, or 2 through 9, in the
Disk Labels Field (column 53).
ACTION The compiler assumes that you left the entry blank.
---------------------------------------------------------------------------------------
2018W MESSAGE COLUMNS 60-65 ARE NOT BLANK.
CAUSE You entered characters in these fields but did not enter K (for
Continuation line) in column 53.
ACTION The compiler ignores your entry and assumes you left these columns
blank.
---------------------------------------------------------------------------------------
2019W MESSAGE COLUMN 66 IS NOT 'A' OR BLANK, ASSUME BLANK.
CAUSE You entered a character, other than an A in the File Addition Field
(column 66).
ACTION The compiler ignores your entry and assumes you left this field
blank. To specify appending new records, change this entry to A.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
2020W MESSAGE COLUMN 67 IS NOT BLANK.
CAUSE This column is not used, but you entered a character in it.
ACTION The compiler assumes that this column is blank.
---------------------------------------------------------------------------------------
2021W MESSAGE COLUMN 70 IS NOT BLANK.
CAUSE This column is not used, but you entered a character in it.
ACTION The compiler assumes that this column is blank.
---------------------------------------------------------------------------------------
2022W MESSAGE COLUMN 73-74 ARE NOT BLANK.
CAUSE This column is not used, but you entered a character in it.
ACTION The compiler assumes that this column is blank.
---------------------------------------------------------------------------------------
2023W MESSAGE INVALID FILE CONDITIONING INDICATOR IN COLUMN 71-72, ASSUME BLANK.
CAUSE You entered an invalid file conditioning indicator in the File
Conditioner Field (columns 71-72). You may only enter U1-U8.
ACTION The compiler ignores your entry and assumes you left this field
blank.
---------------------------------------------------------------------------------------
2024W MESSAGE MULTIPLE PRIMARY FILE DEFINED IN COLUMN 16, ASSUME SECONDARY.
CAUSE You defined more than one primary input file in the File Designation
Field (column 16).
ACTION The compiler assumes that any primary file defined after the first
primary file is a secondary file.
---------------------------------------------------------------------------------------
2025T MESSAGE IF 'SPECIAL' IN COLUMN 40-46, A ROUTINE NAME MUST BE IN COLUMN 54-59.
CAUSE You didn't enter a subroutine name in the Name of Label Exit Field
(column 54-59) to process user labels or files on SPECIAL devices.
ACTION Enter a routine name in column 54-59 or remove SPECIAL from column
40-46 and recompile.
---------------------------------------------------------------------------------------
2026W MESSAGE INVALID NUMBER OF EXTENTS IN COLUMN 68-69, SYSTEM DEFAULT VALUE IS
USED.
CAUSE You entered a number of extents less than 1 or greater than 15 in the
Extents Field (columns 68-69).
ACTION The compiler ignores your entry and by system default assigns eight
extents.
---------------------------------------------------------------------------------------
2027T MESSAGE FILE DESIGNATION ENTRY IN COLUMN 16 INVALID FOR OUTPUT OR DISPLAY
FILE, ASSUME BLANK.
CAUSE You entered a value in the File Designation Field (column 16) that is
invalid for the output or display file.
ACTION The compiler ignores your file designation entry and assumes you left
it blank. Set the File Designation Field to blank or change the file
type to I, U, or C.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
2028W MESSAGE END OF FILE ENTRY IN COLUMN 17 INVALID FOR FILE TYPE.
CAUSE You entered a character in the End-of-File Field (column 17) for file
type O or D, or for file designation C, T, or D.
ACTION The compiler assumes you entered a blank.
---------------------------------------------------------------------------------------
2029W MESSAGE ENTRY IN COLUMN 18 INVALID FOR TYPE OF FILE OR MODE OF PROCESSING,
ASSUME BLANK.
CAUSE You entered a letter or digit, other than an A or D, in the Input
Sequence Field (column 18) that is invalid for the file type or mode
of processing.
ACTION The compiler assumes you entered a blank.
---------------------------------------------------------------------------------------
2030W MESSAGE OVERFLOW INDICATOR IN COLUMN 33-34 PREVIOUSLY ASSIGNED, ASSUME BLANK.
CAUSE You previously assigned an overflow indicator in the Overflow
Indicator Field (column 33-34).
ACTION The compiler ignores your entry and assumes you left this field
blank. If you wish overflow processing, enter an unused overflow
indicator.
---------------------------------------------------------------------------------------
2031W MESSAGE INVALID OR BLANK EXTENSION CODE ENTRY IN COLUMN 39 FOR TABLE OR
RECORD ADDRESS FILE, ASSUME E.
CAUSE You entered a character other than an E or L in the Extension Code
Field (column 39) for a table file or Record Address File.
ACTION The compiler ignores your entry and assumes you entered an E to
define a table file or RAF in a File Extension Specification.
---------------------------------------------------------------------------------------
2032W MESSAGE EXTENSION CODE IN COLUMN 39 IS INVALID, ASSUME BLANK.
CAUSE You entered a letter or digit, other than an E or L, in the Extension
Code Field (column 39).
ACTION The compiler ignores your entry and assumes you left it blank.
---------------------------------------------------------------------------------------
2033W MESSAGE RECORD LENGTH IS LARGER THAN BLOCK LENGTH, ASSUME BLOCK LENGTH EQUAL
TO RECORD LENGTH.
CAUSE You specified a record length larger than the block length.
ACTION The compiler ignores your entry and assumes the block length is equal
to the record length.
---------------------------------------------------------------------------------------
2034W MESSAGE BLOCK LENGTH IS NOT A MULTIPLE OF RECORD LENGTH, ASSUME UNBLOCK.
CAUSE You specified a block length that is not a multiple of the record
length.
ACTION The compiler ignores your entry and assumes there is no blocking (the
physical and logical record lengths are identical).
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
2035I MESSAGE NO FILE DESCRIPTION SPECIFICATION FOUND.
CAUSE You did not enter a File Description Specification in the source
program.
ACTION The compiler assumes that no file I/O will be used by the program.
---------------------------------------------------------------------------------------
2036W MESSAGE NO PRIMARY FILE SPECIFIED IN COLUMN 16, ASSUME FIRST SECONDARY FILE
AS PRIMARY.
CAUSE You didn't specify a primary file in the File Designation Field
(column 16).
ACTION The compiler assumes that the first secondary file is the primary
file.
---------------------------------------------------------------------------------------
2037W MESSAGE COLUMNS WHICH SHOULD BE BLANK FOR CONTINUATION LINE ARE NOT BLANK,
ASSUME BLANK.
CAUSE You made an entry in these columns on a File Description Continuation
line.
ACTION The compiler assumes these columns are blank.
---------------------------------------------------------------------------------------
2038W MESSAGE CONTINUATION LINE IS NOT ALLOWED AT THIS POINT.
CAUSE The first line in the File Description Specifications is a
continuation line.
ACTION The compiler ignores this continuation line.
---------------------------------------------------------------------------------------
2039W MESSAGE CONTINUATION ENTRY IN COLUMN 54-59 IS REPEATED FOR A FILE, SECOND
ENTRY IGNORED.
CAUSE You repeated a continuation line entry; for example, you specified
RDEXIT in two continuation lines for the same file.
ACTION The compiler ignores the second entry.
---------------------------------------------------------------------------------------
2040W MESSAGE ENTRY IN COLUMN 54-59 OF A CONTINUATION RECORD IS INVALID OR MISSING.
CAUSE You entered invalid information in the Option Type Field (columns
54-59) or left this field blank.
ACTION The compiler ignores this continuation line.
---------------------------------------------------------------------------------------
2041W MESSAGE INVALID FILENAME IN COLUMN 7-14, SPEC IS DROPPED.
CAUSE You entered an invalid file name in the File Name Field (column
7-14).
ACTION The compiler drops the specification; redefine the file name and
recompile.
---------------------------------------------------------------------------------------
2042T MESSAGE ONLY ONE RECORD ADDRESS FILE PER PROGRAM IS ALLOWED, ASSUME
SECONDARY.
CAUSE You already specified one Record Address File in the program.
ACTION The compiler assumes the second file designated is a secondary file.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
2043W MESSAGE A RECORD ADDRESS FILE CANNOT BE A 'SPECIAL' FILE.
CAUSE You specified a Record Address File as a SPECIAL file.
ACTION The compiler assumes this file is not a special file.
---------------------------------------------------------------------------------------
2044I MESSAGE NO PRIMARY OR SECONDARY FILE SPECIFICATION IN COLUMN 16.
CAUSE In a program that uses multifile input, you defined no primary or
secondary input files.
ACTION Make the appropriate file definitions and recompile the program.
---------------------------------------------------------------------------------------
2045W MESSAGE THIS CONTINUATION RECORD IS NOT ALLOWED FOR A NON-IMAGE FILE, SPEC IS
DROPPED.
CAUSE You entered a File Description Continuation line that is only
permitted for an TurboIMAGE file.
ACTION The compiler ignores this record.
---------------------------------------------------------------------------------------
2046W MESSAGE ILLEGAL DATA BASE NAME IN COLUMNS 60-65.
CAUSE You entered an invalid TurboIMAGE database name.
ACTION Enter a correct TurboIMAGE database name.
---------------------------------------------------------------------------------------
2047W MESSAGE ILLEGAL OPEN MODE IN COLUMN 66, ASSUME 2.
CAUSE You entered a character other than 1, 2, 3, or blank in the Open Mode
Field (column 66).
ACTION The compiler assumes Mode 2, Update Shared. Enter the correct mode.
---------------------------------------------------------------------------------------
2048W MESSAGE ILLEGAL INPUT/OUTPUT MODE IN COLUMN 67.
CAUSE You entered a character other than 2 through 8, S, B, C, or R, in the
Input/Output Mode Field (column 67).
ACTION The compiler assumes Mode 2. Enter the correct mode.
---------------------------------------------------------------------------------------
2049W MESSAGE RECORD ADDRESS TYPE IN COLUMN 31 MUST BE 'A', 'P', 'K', OR 'I' FOR
IMAGE FILE, ASSUME 'A'.
CAUSE You entered an improper character in the Record Address Type Field
(column 31).
ACTION The compiler assumes you entered A (alphanumeric keys).
---------------------------------------------------------------------------------------
2050W MESSAGE RECORD ADDRESS TYPE IN COLUMN 31 MUST BE 'I' FOR DIRECT FILE.
CAUSE The TurboIMAGE file is a direct-access file, but you specified a
record address type other than I (retrieve by record number).
ACTION The compiler assumes Mode I. Enter the correct mode, if necessary.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
2051T MESSAGE MODE OF PROCESSING IN COLUMN 28 MUST BE 'R' FOR DIRECT FILE, ASSUME
R.
CAUSE The TurboIMAGE file is a direct-access file, but you specified a
processing mode other than R (random).
ACTION The compiler assumes you entered R. Enter the correct mode if
necessary.
---------------------------------------------------------------------------------------
2052T MESSAGE RECORD ADDRESS TYPE IN COLUMN 31 MUST BE BLANK FOR SEQUENTIAL OR TAG
FILE, ASSUME BLANK.
CAUSE The TurboIMAGE file is a sequential or TAG file, but you specified a
record address type other than blank (sequential).
ACTION The compiler assumes you left this field blank. Enter the correct
record address type.
---------------------------------------------------------------------------------------
2054T MESSAGE L IN COLUMN 28 CAN ONLY BE USED WITH C OR R IN COLUMN 67 FOR PREVIOUS
FILE.
CAUSE You specified L (for sequential processing between limits for this
file) but a conflicting Input/Output Mode for the previous file.
ACTION The compiler assumes column 28 is blank. Enter the correct
input/output mode in column 28.
---------------------------------------------------------------------------------------
2055T MESSAGE ITEM NAME MISSING FOR 'L' IN COLUMN 28 FOR PREVIOUS FILE.
CAUSE You did not supply the required ITEM Continuation line.
ACTION The compiler terminates your job at the end of compilation; enter the
ITEM line.
---------------------------------------------------------------------------------------
2056T MESSAGE ITEM NAME MISSING FOR INPUT/OUTPUT MODE 5, 6, C, OR R FOR PREVIOUS
FILE.
CAUSE You did not provide the corresponding ITEM Continuation line for this
chained file.
ACTION The compiler terminates your job at the end of compilation. Enter
the ITEM Continuation line and recompile.
---------------------------------------------------------------------------------------
2058T MESSAGE DATA BASE NAME MISSING FOR PREVIOUS FILE.
CAUSE You did not provide a Database Name Record for this file.
ACTION The compiler terminates your job at the end of compilation. Enter
the Database Name line and recompile.
---------------------------------------------------------------------------------------
2059T MESSAGE FORMS, BATCH, AND TRACE FILES MAY ONLY BE SPECIFIED FOR WORKSTN FILE.
CAUSE You included a FORMS BATCH or TRACE Continuation line for a
non-WORKSTN file.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
2060T MESSAGE TRACE FILE NAME MUST BE NON-BLANK AND BEGIN IN COLUMN 60.
CAUSE The TRACE file name is missing or does not begin in column 60.
ACTION Enter the name beginning in column 60.
---------------------------------------------------------------------------------------
2061W MESSAGE WORKSTN FILE MUST BE UPDATE OR COMBINED. ASSUME UPDATE.
CAUSE A file on device WORKSTN is not declared as update or combined.
ACTION The compiler assumes the WORKSTN file is an update file.
---------------------------------------------------------------------------------------
2062W MESSAGE WORKSTN FILE MUST BE DEMAND OR PRIMARY, ASSUME PRIMARY.
CAUSE A file on device WORKSTN is not declared as demand or primary.
ACTION The compiler assumes WORKSTN file is primary.
---------------------------------------------------------------------------------------
2063W MESSAGE WORKSTN FILE MUST HAVE VARIABLE LENGTH RECORDS, ASSUME VARIABLE.
CAUSE A file on device WORKSTN has fixed length records.
ACTION The compiler assumes the WORKSTN file has variable length records.
---------------------------------------------------------------------------------------
2064W MESSAGE COLUMN 52 MUST BE BLANK FOR FILES NOT ON DEVICE WORKSTN.
CAUSE Column 52 is not blank for the non-WORKSTN file.
ACTION The compiler assumes column 52 is blank.
---------------------------------------------------------------------------------------
2065W MESSAGE INVALID ENTRY IN COLUMN 52, ASSUME BLANK.
CAUSE Column 52 contains an invalid entry for the WORKSTN file.
ACTION The compiler assumes column 52 is blank.
---------------------------------------------------------------------------------------
2066W MESSAGE COLUMN 51 MUST BE BLANK FOR FILES NOT ON DEVICE WORKSTN.
CAUSE Column 51 is not blank for the non-WORKSTN file.
ACTION The compiler assumes column 51 is blank.
---------------------------------------------------------------------------------------
2067W MESSAGE INVALID ENTRY IN COLUMN 51, ASSUME BLANK.
CAUSE Column 51 contains an invalid entry for the WORKSTN file.
ACTION The compiler assumes column 51 is blank.
---------------------------------------------------------------------------------------
2068W MESSAGE FILE ON DEVICE $STDIN MUST BE INPUT, ASSUME INPUT.
CAUSE A file declared on device $STDIN is not an input file.
ACTION The compiler assumes $STDIN is the input file.
---------------------------------------------------------------------------------------
2069W MESSAGE FILE ON DEVICE $STDLIST MUST BE OUTPUT OR DISPLAY, ASSUME OUTPUT.
CAUSE A file that uses device $STDLST is not an output or display file.
ACTION The compiler assumes the $STDLST file is an output file.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
2070W MESSAGE KEY FIELD/RECORD ADDRESS FIELD LENGTH MUST BE ENTERED FOR THIS FILE.
CAUSE No key field length is entered for a chaining type file.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
2071W MESSAGE KEY FIELD STARTING LOCATION MUST BE ENTERED FOR THIS FILE.
CAUSE No key field starting location is entered for a chaining file.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
2072I MESSAGE DEVICE NAME NOT LEFT-JUSTIFIED IN FIELD, ASSUME JUSTIFIED.
CAUSE You specified a device name that is not left-justified in the Device
Class Name Field (columns 40-46).
ACTION The compiler left justifies the entry.
---------------------------------------------------------------------------------------
2073W MESSAGE FILE SPECIFIED AS CHAINED ACCESS MUST BE RANDOM PROCESSED, ASSUMED R
IN COLUMN 28.
CAUSE You specified a file as chained access, but did not specify random
processing.
ACTION The compiler assumes you entered R in column 28.
---------------------------------------------------------------------------------------
2074W MESSAGE INPUT/OUTPUT MODE MUST BE 5, 6, 7, 8, C, OR R FOR RECORD LEVEL
LOCKING, ASSUME 1 IN COLUMN 66.
CAUSE You specified R (Record Locking) in column 66, but used an incorrect
Input/Output Mode in column 67. This sequence is invalid.
ACTION The compiler assumes you entered 1 (database locking per record) in
column 66.
---------------------------------------------------------------------------------------
2075W MESSAGE LOCKING MODE INCONSISTENT FOR DATA BASE, FIRST MODE IS B, MODES AFTER
ARE DIFFERENT, ASSUME B.
CAUSE You specified different locking modes following an initial locking
mode of B. This sequence is invalid.
ACTION The compiler assumes the mode B for all accesses.
---------------------------------------------------------------------------------------
2076W MESSAGE LOCKING MODE INCONSISTENT FOR DATA SET, FIRST MODE IS S, MODES AFTER
ARE DIFFERENT, ASSUME S.
CAUSE You specified different locking modes following an initial locking
mode of S. This sequence is invalid.
ACTION The compiler assumes the mode S for all accesses.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
2077W MESSAGE LOCKING MODE INCONSISTENT, MODE FOLLOWING FIRST LOCK MODE ARE
DIFFERENT; ASSUME FIRST MODE.
CAUSE You specified different locking modes following an initial locking
mode. This sequence is invalid.
ACTION Correct the program for locking mode consistency and recompile.
---------------------------------------------------------------------------------------
2078T MESSAGE LOCKING MODE IS INCONSISTENT, FIRST MODE IS S, THE FOLLOWING MODE IS
B.
CAUSE You specified different locking modes following an initial locking
mode.
ACTION Correct the program for locking mode consistency and recompile.
---------------------------------------------------------------------------------------
2079T MESSAGE LOCKING MODE INCONSISTENT, MODES FOLLOWING FIRST LOCK MODE ARE OF
HIGHER PRECEDENCE.
CAUSE You specified different locking modes following an initial locking
mode.
ACTION Correct the program for locking mode consistency and recompile.
---------------------------------------------------------------------------------------
2080T MESSAGE FILE DESCRIBED AS AN OUTPUT CHAIN FILE MUST BE A DIRECT FILE, NOT A
KSAM, IMAGE, OR INDEXED FILE.
CAUSE You specified a file as OC in columns 15-16; therefore, column 32
must be specified as a direct file.
ACTION Correct the program to specify blank, D, or 1-7 in column 32, and
recompile.
---------------------------------------------------------------------------------------
2081I MESSAGE FOR UPDATE-ADD FILE WITHOUT 'UPDATE-PROTECT CHECK', ENSURE THAT NO
UPDATE IS INTERRUPTED BY AN ADD.
CAUSE You specified a file as update without specifying the update-protect
check option in column 28 of the Header Specification.
ACTION Add the update protect check option (U or X in column 28) or ensure
that the program does not attempt to add a record while an update
operation is in progress.
---------------------------------------------------------------------------------------
2082W MESSAGE COLUMN 50 MUST BE BLANK FOR FILES NOT ON DEVICE WORKSTN.
CAUSE You specified an incorrect entry for column 50.
ACTION The compiler assumes blank.
---------------------------------------------------------------------------------------
2083W MESSAGE INVALID ENTRY IN COLUMN 50, ASSUME BLANK.
CAUSE You specified an incorrect entry for column 50.
ACTION The compiler assumes blank.
---------------------------------------------------------------------------------------
2084W MESSAGE COLUMN 32 FOR WORKSTN FILE MUST BE BLANK, ASSUME BLANK.
CAUSE You specified an incorrect entry for column 32.
ACTION The compiler assumes blank.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
2085W MESSAGE BUFCHK SPEC ONLY ALLOWED FOR SEQUENTIAL, DIRECT, AND INDEXED FILES,
SPEC IS DROPPED.
CAUSE You specified a BUFCHK Continuation line for a file that is not a
sequential, direct, or indexed file.
ACTION The compiler ignores the BUFCHK Continuation line.
---------------------------------------------------------------------------------------
2086W MESSAGE BUFCHK SPEC COLUMN 60 (CURRENT DATA CHECK) MUST BE BLANK OR N, ASSUME
BLANK.
CAUSE You specified an incorrect entry for column 60.
ACTION The compiler assumes blank.
---------------------------------------------------------------------------------------
2087W MESSAGE BUFCHK SPEC COLUMN 61 (NO-READ CHECK) MUST BE BLANK OR N, ASSUME
BLANK.
CAUSE You specified an incorrect entry for column 61.
ACTION The compiler assumes blank.
---------------------------------------------------------------------------------------
2088I MESSAGE BUFCHK 'NO-READ CHECK' DISABLED FOR NON-UPDATE FILE.
CAUSE You specified the NO-READ CHECK option in column 28 of the Header
Specification and a BUFCHK Continuation line with a blank in column
61 for a non-update file. This sequence is invalid.
ACTION The compiler disables the NO-READ CHECK option for this file.
---------------------------------------------------------------------------------------
2089W MESSAGE BUFCHK SPEC COLUMN 62 (UPDATE-PROTECT CHECK) MUST BE BLANK OR N,
ASSUME BLANK.
CAUSE You specified an incorrect entry for column 62.
ACTION The compiler assumes blank.
---------------------------------------------------------------------------------------
2090I MESSAGE BUFCHK 'UPDATE-PROTECT CHECK' DISABLED FOR NON-UPDATE FILE.
CAUSE You specified the UPDATE-PROTECT CHECK option in column 28 of the
Header Specification and a BUFCHK Continuation line with a blank in
column 62 for a non-update file. This sequence is invalid.
ACTION The compiler disables the UPDATE-PROTECT CHECK option for this file.
---------------------------------------------------------------------------------------
2091I MESSAGE BUFCHK 'CURRENT DATA CHECK' DISABLED FOR ALL NON-LOCKING FILES HAVING
A 'BUFCHK' CONTINUATION REC.
CAUSE You specified the CURRENT DATA CHECK option in column 28 of the
Header Specification, and a BUFCHK Continuation line for files for
which locking is not specified.
ACTION The compiler disables the CURRENT DATA CHECK option for the file(s).
---------------------------------------------------------------------------------------