HP 3000 Manuals HP 3000 Manuals
Message Types (Cont)
---------------------------------------------------------------------------------------
5029T MESSAGE COLUMN 43 NOT P, B, L, R, 1-9, OR BLANK - ASSUME BLANK.
CAUSE You entered a character other than a P, B, L, R, or 1-9 in the Data
Format Field (column 43).
ACTION The compiler ignores your entry and assumes you left the field blank.
Enter P, B, L, R, 1-9, or blank in column 43.
---------------------------------------------------------------------------------------
5030T MESSAGE FROM FIELD LOCATION INVALID - ASSUME 1.
CAUSE You specified invalid numeric characters or embedded blanks in the
From Field Position (column 44-47).
ACTION The compiler ignores your entry and assumes you entered a 1. Correct
the From Field Position to contain valid numbers, right-adjusted.
---------------------------------------------------------------------------------------
5032T MESSAGE 'FROM' GREATER THAN 'TO' FIELD LOCATION - ASSUME FIELD LENGTH OF 1.
CAUSE You specified that the From Field in the From Field Position Field
(columns 44-47) is greater than the To Field in the To Field Position
Field (columns 48-51).
ACTION The compiler ignores your entry and assumes the From Field length is
1. Correct the From or To Field Positions so that the To Field
Position is greater than or equal to the From Field Position.
---------------------------------------------------------------------------------------
5033T MESSAGE FIELD LOCATION NOT WITHIN RECORD LENGTH.
CAUSE You specified a To Field Position that does not fall within the
record length defined for the file.
ACTION Either correct the record length for the file or change the field
location so that it falls within the record length.
---------------------------------------------------------------------------------------
5034T MESSAGE DECIMAL POSITIONS (COLUMN 52) NOT BLANK OR 0-9 - ASSUME BLANK.
CAUSE You entered a character, other than 0-9, in the Decimal Positions
Field (column 52).
ACTION The compiler ignores your entry and assumes you left the field blank.
Correct the field to reflect the number of decimal positions desired.
---------------------------------------------------------------------------------------
5035T MESSAGE FIELD NAME (COLUMNS 53-58) BLANK OR INVALID - SPECIFICATION DROPPED.
CAUSE You entered an invalid field name or left the Field Name Field
(columns 53-58) blank.
ACTION The compiler ignores this specification. Correct the field name.
---------------------------------------------------------------------------------------
5036T MESSAGE INVALID INDEX FOR FIELD NAME (COLUMNS 53-58) ASSUME INDEX OF 1.
CAUSE You entered invalid numeric characters or embedded blanks for the
array index in the Field Name Field (columns 53-58).
ACTION The compiler ignores the index and assumes you entered a 1. Enter a
numeric character or field for the index.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
5037T MESSAGE VARIABLE ARRAY INDEX (COLUMNS 53-58) IS NOT NUMERIC VARIABLE.
CAUSE You specified a value other than a numeric variable for the variable
array index in the Field Name Field (columns 53-58).
ACTION Specify a numeric variable with zero decimal positions for the array
index.
---------------------------------------------------------------------------------------
5038W MESSAGE VARIABLE ARRAY INDEX (COLUMNS 53-58) DOES NOT HAVE ZERO DECIMAL
POSITIONS - ASSUME 0.
CAUSE You specified a variable array index without specifying zero decimal
positions for it.
ACTION The compiler accepts your entry as if you specified zero decimal
positions for the index. Redefine the index to have zero decimal
positions.
---------------------------------------------------------------------------------------
5039T MESSAGE INDEX CANNOT BE AN ARRAY NAME.
CAUSE You used an array name as an array index.
ACTION Use either a numeric constant or a numeric variable with zero decimal
positions as the array index.
---------------------------------------------------------------------------------------
5040T MESSAGE FIELD NAME (COLUMNS 53-58) IS A NON-ALTERABLE FIELD - RECORD IGNORED.
CAUSE The field named is defined previously as a look-ahead field or UDAY,
UMONTH, UYEAR, or UDATE. These cannot be used in Input
Specifications.
ACTION Specify a different field name.
---------------------------------------------------------------------------------------
5041T MESSAGE PAGE INVALIDLY REDEFINED - MUST BE NUMERIC WITH ZERO DECIMAL
POSITIONS.
CAUSE You redefined PAGE (Field Name Field, columns 53-58) without entering
zero in the Decimal Positions Field (column 52).
ACTION Enter a zero in the Decimal Positions Field (column 52) for the field
PAGE and recompile.
---------------------------------------------------------------------------------------
5042T MESSAGE DECIMAL POSITIONS (COLUMN 52) DIFFERS FROM PREVIOUS SPECIFICATION -
ASSUME PREVIOUS DEFINITION.
CAUSE You entered the same field name that was previously defined with
different decimal positions in the field (column 52).
ACTION The compiler ignores your entry and assumes the decimal position is
the same as the previous definition of this field name. Correct one
or the other entry so that both are the same.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
5043 MESSAGE FIELD SIZE IS NOT A MULTIPLE OF THE NUMBER OF ELEMENTS - NEXT LOWEST
MULTIPLE ASSUMED.
CAUSE You specified an array name, and the field size allows for several
array elements plus a fraction of an array element.
ACTION Correct the field size to contain an integral number of array
elements.
---------------------------------------------------------------------------------------
5044T MESSAGE ARRAY SIZE EXCEEDED - ASSUME TO END OF ARRAY.
CAUSE You specified an array name and the field size allows for more array
elements than the array can hold.
ACTION Correct either the array definition or the number of array elements
defined by the field length.
---------------------------------------------------------------------------------------
5045T MESSAGE FIELD SIZE NOT SAME AS PREVIOUSLY DEFINED - ASSUME PREVIOUS
DEFINITION.
CAUSE You specified a field size that isn't the same as previously defined
for this field.
ACTION The compiler ignores your entry and assumes the field size is the
same as the one previously defined for this field. Correct the size
of either field so that they are the same size.
---------------------------------------------------------------------------------------
5046T MESSAGE FIELD PREVIOUSLY DEFINED AS ALPHA - ASSUME ALPHA.
CAUSE You defined this field as numeric, but it is previously defined as
alphanumeric.
ACTION The compiler assumes that this is an alphanumeric field. Correct the
type of one or the other so that both fields are the same type.
---------------------------------------------------------------------------------------
5047T MESSAGE FIELD PREVIOUSLY DEFINED AS NUMERIC - ASSUME NUMERIC.
CAUSE You defined the field as alphanumeric, but it is previously defined
as numeric.
ACTION The compiler assumes that this is a numeric field. Correct the type
of either field so that both fields are the same type.
---------------------------------------------------------------------------------------
5048T MESSAGE ALPHA FIELD SIZE GREATER THAN 256 - ASSUME 256.
CAUSE You entered an alphanumeric field size greater than 256 characters;
that is, the To Field Position minus the From Field Position plus 1
is greater than 256.
ACTION The compiler ignores your entry and assumes you specified 256
characters. Correct the From Field Position or To Field Position
Fields to reflect a field length of 256 or less.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
5049T MESSAGE DECIMAL FIELD LENGTH EXCEEDS 15 DIGITS - ASSUME 15.
CAUSE You entered a decimal field length that exceeds 15 digits.
ACTION The compiler ignores your entry and assumes you specified 15 digits.
Correct the From Field Position or the To Field Position Fields to
reflect a digit length of 15 or less.
---------------------------------------------------------------------------------------
5050T MESSAGE DECIMAL POSITIONS EXCEED NUMBER OF DIGITS - ASSUME EQUAL TO DIGITS.
CAUSE You specified, in the Decimal Positions Field (column 52), a value
greater than the total number of digits in the field.
ACTION The compiler ignores your entry and assumes the decimal positions are
equal to the number of digits. Correct the number of decimal
positions or the digit size of the field.
---------------------------------------------------------------------------------------
5051T MESSAGE INVALID FIELD RECORD RELATION (COLUMNS 63-64) INDICATOR - BLANK
ASSUMED
CAUSE You specified an invalid record-identifying indicator in the Field
Record Relation Field (columns 63-64).
ACTION The compiler ignores the entry and assumes you left this field blank.
Enter a valid indicator (01-99, H0-H9, L0-L9, LR, MR, OA-OG, OV, 1P,
F0-F9, KA-KN, KP-KY, U1-U8) or leave this field blank.
---------------------------------------------------------------------------------------
5052T MESSAGE CONTROL LEVEL (COLUMNS 59-60) NOT BLANK OR L1-L9 - ASSUME BLANK.
CAUSE You specified invalid characters, other than the control-level
indicators L1-L9, in the Control Level Field (columns 59-60).
ACTION The compiler ignores your entry and assumes you left this field
blank. Enter L1-L9 in the Control Level Field or leave it blank.
---------------------------------------------------------------------------------------
5053T MESSAGE CONTROL LEVEL LENGTH DIFFERS FROM PREVIOUS DEFINITION - ASSUMES
PREVIOUS DEFINITION.
CAUSE You specified a different control-level field length than the length
previously defined for this field.
ACTION The compiler ignores your entry and assumes you specified the same
control-level field length as you previously defined. Correct either
length so that they are the same.
---------------------------------------------------------------------------------------
5054T MESSAGE CONTROL LEVEL (COLUMNS.59-60) OR MATCHING FIELD (COLUMNS.61-62) USED
WITH CHAINED OR DEMAND FILE - ASSUME BLANK.
CAUSE You specified a control-level indicator in the Control Level Field
(columns 59-60), or a matching-record indicator in the
Matching/Chaining Fields (columns 61-62) for a chained or demand
file.
ACTION The compiler ignores your entry and assumes you omitted the
control-level indicator or matching-record indicator. Change the
File Designation Field (column 16) of the File Description
Specification or leave columns 59-62 blank in the Input
Specification.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
5055T MESSAGE CONTROL OR MATCHING FIELD (COLUMNS 59-62) USED FOR TRAILER OR
LOOK-AHEAD RECORD - ASSUME BLANK.
CAUSE You assigned a control-level or matching-record indicator to a spread
record trailer or a look-ahead record.
ACTION The compiler ignores your entry and assumes that you left this field
blank. Change these columns to blank.
---------------------------------------------------------------------------------------
5056T MESSAGE INVALID MATCHING OR CHAINING ENTRY (COLS 61-62) - ASSUME BLANK.
CAUSE You assigned a code other than M1 through M9, C1 through C9, or blank
to the Matching/Chaining Field (columns 61-62).
ACTION The compiler ignores your entry and assumes that you left this field
blank. Change the entry to M1-M9, C1-C9, or blank.
---------------------------------------------------------------------------------------
5057T MESSAGE ARRAY USED FOR MATCHING FIELD - ASSUME NO MATCHING FIELD.
CAUSE You used an array rather than a data field to test for matching
fields.
ACTION The compiler assumes that no matching field entry is used. Remove
the matching field entry for this record. If you need to use this
field as a matching field, redefine it with another name and assign
M1-M9 to this new name.
---------------------------------------------------------------------------------------
5058T MESSAGE FIELD RECORD RELATION PREVIOUSLY USED WITH THIS MATCHING OR CONTROL
LEVEL - ASSUME PREVIOUS.
CAUSE You used the same field record relation previously in this record
with matching or control level fields.
ACTION Either remove the matching-record or control-level indicator, change
the field record relation or move the specification records to a new
place.
---------------------------------------------------------------------------------------
5059T MESSAGE MATCHING LEVEL ALREADY SPECIFIED FOR THIS FIELD RECORD RELATION.
CAUSE The same matching level (M1-M9) has already been used in this record
specification with the same field record relation (may be a blank).
ACTION Change the matching level or the field record relation.
---------------------------------------------------------------------------------------
5060T MESSAGE MATCHING LEVEL LENGTH DIFFERS FROM PREVIOUS DEFINITION - ASSUME
PREVIOUS.
CAUSE The matching field length specified differs from the length
previously defined for this field.
ACTION The compiler assumes the previous length for this field. Change one
field length or the other so that both are the same.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
5061T MESSAGE COMPLETE SET OF MATCHING FIELDS NOT DEFINED FOR LAST GROUP.
CAUSE When you previously specified matching fields in this program, you
specified more levels of matching fields than the current definition.
ACTION Either delete the extra matching levels specified earlier or add
levels to the current definition.
---------------------------------------------------------------------------------------
5063T MESSAGE CHAINING (COLUMNS 61-62) SPECIFIED WITH LOOK-AHEAD FIELD - CHAINING
IGNORED.
CAUSE You requested chaining with a look-ahead record.
ACTION The compiler ignores your entry and assumes a request for look-ahead.
Delete the chaining request from the look-ahead field. Include it in
a regular field definition if it is needed.
---------------------------------------------------------------------------------------
5064T MESSAGE L OR R (COLUMN 43) SPECIFIED WITH CHAINING (COLUMNS 61-62) - CHAINING
IGNORED.
CAUSE You specified a field containing unpacked decimal data with leading
or trailing sign for a chaining field, but such a field cannot be
used for this purpose.
ACTION The compiler ignores your request for chaining. Remove the chaining
specification or the L or R. The field may be redefined as a regular
field (with From Position one larger for L or To Position one smaller
for R) with no L or R for the field.
---------------------------------------------------------------------------------------
5065T MESSAGE ARRAY SPECIFIED AS CHAINING FIELD - IGNORE CHAINING.
CAUSE You specified an array rather than a data field as a chaining field.
ACTION The compiler ignores your request for chaining. Remove the chaining
entry from this record. The field may be redefined as a regular
field (same location but different name) with chaining.
---------------------------------------------------------------------------------------
5066T MESSAGE INCORRECT KEY TYPE FOR CHAINING FILE. SHOULD BE ALPHANUMERIC.
CAUSE A non-alphanumeric key was specified for a KSAM or TurboIMAGE file.
ACTION Use only alphanumeric keys for chaining with these file types (column
31 of the File Description Specification is A). Correct the program
and recompile.
---------------------------------------------------------------------------------------
5067T MESSAGE CHAINING LEVEL (COLUMNS 61-62) ALREADY SPECIFIED FOR THIS FIELD
RECORD RELATION.
CAUSE The same chaining level is already in this specification with the
same field record relation.
ACTION Delete the chaining level (C1-C9) from this record.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
5068T MESSAGE FIELD RECORD RELATION PREVIOUSLY USED IN THIS RECORD FOR CHAINING.
CAUSE All chaining fields for one field record relation were not together.
ACTION Move the record so that it is among the others of the same field
record relation or delete the chaining entry (C1-C9) from this
record.
---------------------------------------------------------------------------------------
5069T MESSAGE INVALID PLUS RESULT INDICATOR (COLUMNS 65-66) - ASSUME BLANK.
CAUSE You entered an invalid indicator or illegal characters in the Plus
Subfield (columns 65-66).
ACTION The compiler assumes that you left this subfield blank. Enter blanks
or a valid indicator (01-99, H0-H9, L0-L9, LR, MR, OA-OG, OV, 1P,
F0-F9, KA-KN, KP-KY, U1-U8) in these columns.
---------------------------------------------------------------------------------------
5070T MESSAGE INVALID MINUS RESULT INDICATOR (COLUMNS 67-68) - ASSUME BLANK.
CAUSE You entered an improper indicator or illegal characters in the Minus
Subfield (columns 67-68).
ACTION The compiler assumes that you left this subfield blank. Enter blanks
or a valid indicator (01-99, H0-H9, L0-L9, LR, MR, OA-OG, OV, 1P,
F0-F9, KA-KN, KP-KY, U1-U8) in these columns.
---------------------------------------------------------------------------------------
5071T MESSAGE INVALID BLANK/ZERO RESULT INDICATOR (COLUMNS 69-70) ASSUME BLANK.
CAUSE You entered an invalid indicator or illegal characters in the Zero or
Blank Subfield (columns 69-70).
ACTION The compiler assumes that you left this subfield blank. Enter blanks
or a valid indicator (01-91, H0-H9, L0-L9, LR, MR, OA-OG, OV, 1P,
F0-F9, KA-KN, KP-KY, U1-U8) in these columns.
---------------------------------------------------------------------------------------
5072T MESSAGE FIELD USED PREVIOUSLY AS INDEX NOT DEFINED AS NUMERIC WITH ZERO
DECIMAL POSITIONS.
CAUSE You used an alphanumeric field or a numeric field containing one or
more decimal positions as an array element index.
ACTION Redefine the index field to be numeric with zero decimal positions.
---------------------------------------------------------------------------------------
5073T MESSAGE TABLE USED AS INPUT FIELD.
CAUSE You specified a table name in the Field Name Field (columns 53-58).
ACTION Delete the reference to the table from the Input Specification.
---------------------------------------------------------------------------------------
5074T MESSAGE MATCHING OR CONTROL LEVEL WITH BLANK FIELD RELATION MUST BE SPECIFIED
FIRST.
CAUSE You specified matching or control-level fields with a field record
relation indicator before the current one (which has a blank field
record relation).
ACTION Move the blank field record relation specification so that it comes
before those that specify an indicator.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
5075T MESSAGE FIRST INPUT SPECIFICATION DOES NOT HAVE FILE NAME.
CAUSE You omitted the file name from the File Name Field (columns 7-14) of
the first Input Specification or entered a field description with no
preceding record description.
ACTION Include the file name on a record description specification.
---------------------------------------------------------------------------------------
5076T MESSAGE FILENAME ALREADY USED FOR INPUT SPECIFICATIONS.
CAUSE You specified a file name that was previously used in a record
description in the Input Specifications and included an intervening
specification for a different file.
ACTION Keep all Input Specifications for a file together, without
intervening specifications for another file.
---------------------------------------------------------------------------------------
5077W MESSAGE NUMERIC SEQUENCE (COLUMNS 15-16) SPECIFIED FOR CHAINED FILE - ASSUME
BLANK.
CAUSE You specified a numeric group sequence for this chained file, in the
Group Sequence Field, where an alphanumeric sequence is required.
ACTION The compiler assumes that you specified an alphanumeric sequence.
Change the sequence number to alphanumeric characters.
---------------------------------------------------------------------------------------
5078I MESSAGE BLANK RECORD - RECORD IGNORED.
CAUSE There is a blank line in the Input Specifications.
ACTION The compiler ignores this line.
---------------------------------------------------------------------------------------
5079T MESSAGE LOOK-AHEAD OR TRAILER RECORD NOT IN A PRIMARY OR SECONDARY FILE.
CAUSE You included a look-ahead record or spread record trailer in a file
other than a primary or secondary file.
ACTION Either change the file designation or remove the look-ahead or
trailer records.
---------------------------------------------------------------------------------------
5080T MESSAGE P, B, L, OR R (COLUMN 43) SPECIFIED FOR ALPHA FIELD - ASSUME BLANK.
CAUSE You specified in the Data Format Field, a numeric format for a field
previously defined as alphanumeric.
ACTION The compiler assumes that you left the Data Format Field blank in
this specification. Either change column 43 to blank or define this
as a numeric field (by entering a digit in the Decimal Positions
Field).
---------------------------------------------------------------------------------------
5081T MESSAGE BINARY FIELD LENGTH IS NOT 2 OR 4 - ASSUME UNPACKED NUMERIC FIELD.
CAUSE You defined an input field length other than 2 or 4 for a binary
field; (2 is two bytes and 4 is four bytes).
ACTION Either correct the field length or change the type of numeric field.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
5082T MESSAGE INDEX SPECIFIED FOR NON-ARRAY - IGNORE INDEX.
CAUSE You specified an index for a data field that is not an array.
ACTION The compiler ignores the index. Either include an array definition
(File Extension Specification) for this field name or delete the
index.
---------------------------------------------------------------------------------------
5083T MESSAGE MATCHING RECORD FILE NOT IN SAME SEQUENCE AS LAST.
CAUSE A file containing matching records has a different sequence than the
last matching record file previously specified.
ACTION Change the Input Sequence Field of the File Description
Specifications (column 18) for files with matching fields to all A
or all D.
---------------------------------------------------------------------------------------
5084T MESSAGE INPUT, UPDATE, OR COMBINED FILE HAS NO INPUT SPECIFICATIONS.
CAUSE You named an input, update, or combined file but failed to specify
the required record characteristics.
ACTION Include the Input Specifications for the input, update, or combined
file or change the file type.
---------------------------------------------------------------------------------------
5085T MESSAGE DIGIT LENGTH OF FIELD IS ZERO - ASSUME 1.
CAUSE You have specified a numeric field containing no digits, but such
fields must contain at least one digit.
ACTION The compiler assumes that you specified a 1-digit field. Redefine
the field to be at least one digit long (fields with L or R in column
43 must be at least 2 bytes long to contain 1 digit).
---------------------------------------------------------------------------------------
5086T MESSAGE CHAINING CODE AND FILE NOT SPECIFIED ON EXTENSION SPECS - IGNORE
CHAINING.
CAUSE You failed to specify a chaining field code in columns 11-18 of the
File Extension Specifications, even though you have defined such a
file in the Input Specifications.
ACTION Either correct the File Extension Specifications or delete the
chaining entries from the Input Specifications.
---------------------------------------------------------------------------------------
5087W MESSAGE ARRAY USED FOR LEVEL FIELD - ASSUME NOT A LEVEL FIELD.
CAUSE You specified an array name in the Control Level Field (columns
59-60), but a field name is required.
ACTION The compiler assumes that you left the Control Level Field blank.
Change the Control Level Field to blanks. If this field must be a
control field, redefine it with a new field name and include the
chaining level.
---------------------------------------------------------------------------------------
5088T MESSAGE LOOK-AHEAD FIELD PREVIOUSLY DEFINED - RECORD IGNORED.
CAUSE You defined a look-ahead field that has already been defined.
ACTION The compiler ignores the line. Rename this field or delete the
specification.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
5089W MESSAGE CHAINING FIELD NUMERIC BUT ALPHA KEYS SPECIFIED ON FILE SPEC.
CAUSE You specified a numeric chaining field in conflict with alphanumeric
searching keys for the TurboIMAGE file.
ACTION Either change the field type or the Record Address Type Field (column
31) of the File Description Specification.
---------------------------------------------------------------------------------------
5090W MESSAGE CHAINING FIELD LENGTH NOT SAME AS KEY FIELD LENGTH FROM FILE SPEC.
CAUSE You specified different lengths for the chaining and key fields; they
must be the same.
ACTION Either redefine the chaining field length, the key length, or include
a conversion routine.
---------------------------------------------------------------------------------------
5091W MESSAGE THE PRECEDING CONTROL LEVEL LENGTH DIFFERS FROM ITS PREVIOUS
DEFINITION.
CAUSE You specified a control field for which the total length differs from
the total length of the same control level defined for a previous
record.
ACTION Change the program to specify the same total length for all
definitions of the same control level, and recompile.
---------------------------------------------------------------------------------------
5092W MESSAGE PRECEDING CHAINING FIELD LENGTH NOT SAME AS KEY FIELD LENGTH FROM
FILE SPEC.
CAUSE You specified a chaining field for which the total length differs
from the Key Field Length Field (columns 29-30) in the File
Description Specification.
ACTION Correct the length and recompile.
---------------------------------------------------------------------------------------
5093T MESSAGE DATA STRUCTURE (DS) SPECIFICATIONS CANNOT BE FOLLOWED BY NON-DATA
STRUCTURE SPECS.
CAUSE You followed a data structure with non-data structure Input
Specifications.
ACTION Rearrange the Input Specifications so that all data structures are at
the end and recompile.
---------------------------------------------------------------------------------------
5094W MESSAGE RESERVED NAME FOR UDS IS 'LDA' - NAME SPECIFIED IN COLUMNS. 7-12 IS
REPLACED BY 'LDA'.
CAUSE You specified a UDS (User Data Structure) in columns 18-20 and
either; (1) specified a name other than LDA or blank in columns 7-12
or (2) specified LDA in columns 7-12, but had already defined LDA as
a field on a prior Input Specification.
ACTION Correct the program and recompile.
---------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
5095T MESSAGE NESTED NUMERICS IN DS NOT SUPPORTED.
CAUSE A numeric field named as a data structure contains numeric subfields.
ACTION Do not use numeric subfields in this case. Correct the program and
recompile.
------------------------------------------------------------------------------------------------
5096W MESSAGE FIELD ALREADY DEFINED AS PART OF A DS-RECORD IGNORED.
CAUSE This field name has already been used in this or a previous data
structure.
ACTION The compiler ignores this field.
------------------------------------------------------------------------------------------------
5097T MESSAGE CANNOT OPEN FILE 'SIGWORK' FOR RSI PROCESSING.
CAUSE Possible system problem. This is an internal file used by the
compiler to pass information to SIGEDITOR.
ACTION Contact your HP Support Engineer.
------------------------------------------------------------------------------------------------
5098T MESSAGE CANNOT WRITE TO FILE 'SIGWORK'.
CAUSE Possible system problem.
ACTION Contact your HP Support Engineer.
------------------------------------------------------------------------------------------------
5099T MESSAGE WORKSTNC FILE MUST USE RII 01-10 ONLY.
CAUSE Invalid record-identifying indicator.
ACTION Use indicators 01 through 10 only.
------------------------------------------------------------------------------------------------
5100T MESSAGE CANNOT CLOSE FILE 'SIGWORK'.
CAUSE Possible system problem.
ACTION Contact your HP Support Engineer.
------------------------------------------------------------------------------------------------
5101T MESSAGE CANNOT CREATE 'SIGEDIT' PROCESS.
CAUSE MPE cannot find the program SIGEDIT in PUB.SYS.
ACTION Be sure the program SIGEDIT is installed in PUB.SYS. If this error
persists, contact your HP Support Engineer.
------------------------------------------------------------------------------------------------
5102T MESSAGE CANNOT ACTIVATE 'SIGEDIT' PROCESS.
CAUSE Process may already be activated, or PH capability may be missing.
ACTION Be sure the group containing the RPG compiler has process-handling
(PH) capability.
------------------------------------------------------------------------------------------------
[REV BEG]
5103T MESSAGE COL. 43 NOT BLANK FOR DS FIELD. ASSUME BLANK.
CAUSE Input Specification column 43 was not blank for a DS field.
ACTION To eliminate this warning, change column 43 to a blank. The compiler
assumes a blank by default.
------------------------------------------------------------------------------------------------
[REV END]
6001T MESSAGE INVALID CONTROL LEVEL IN COL. 7-8, ASSUME LATEST LEVEL.
CAUSE You entered an indicator other than L0-L9 or LR in the Control Level
Field (columns 7-8).
ACTION The compiler assumes that you intended the latest level indicator.
Correct the control level and recompile.
------------------------------------------------------------------------------------------------