 |
» |
|
|
|
The following messages are returned from GENCAT: - 1
- MESSAGE
FREAD ERROR ON SOURCE FILE.
- CAUSE
A failure by FREAD when reading a source message catalog.
- ACTION
Re-create the source message catalog.
- 2
- MESSAGE
INPUT FILE MUST HAVE AT LEAST ONE RECORD.
- CAUSE
The file has an EOF of zero (0).
- ACTION
Place at least one record in the file.
- 3
- MESSAGE
INPUT FILE MUST CONTAIN FIXED LENGTH RECORDS ONLY. - CAUSE
File does not have a fixed record length. - ACTION
Create the file with a fixed record length.
- 4
- MESSAGE
INPUT FILE MUST BE ASCII FILE ONLY. - CAUSE
Source and maintenance files must have records that are in ASCII format. - ACTION
Create the source and maintenance files with ASCII format.
- 5
- MESSAGE
INPUT FILE RECORD SIZE MUST BE BETWEEN 40 AND 256 BYTES. - CAUSE
The record size of a source or maintenance file is greater than 256 bytes (128 words) or less than 40 bytes (20 words). - ACTION
Create a source and maintenance file with a record size greater or equal to 40 bytes or less than or equal to 256 bytes.(Note that this record length includes any line numbers in the file.)
- 6
- MESSAGE
SET NUMBERS MUST BE BETWEEN 1 AND 255. - CAUSE
A set number in a maintenance or source file is not greater than or equal to 1, or not less than or equal to 255.The set number may be negative or it may not be numeric. - ACTION
Change set number to a value between 1 and 255 inclusive.
- 8
- MESSAGE
SET NUMBERS MUST BE IN ASCENDING SEQUENCE. - CAUSE
A set number is less than or equal to the previous set number in the source file.Error can be detected at format time or during a maintenance function. - ACTION
Change numbers to strict ascending sequence.
- 9
- MESSAGE
MESSAGE NUMBERS MUST BE BETWEEN 1 AND 32766. - CAUSE
A message number value is not between 1 and 32,766 inclusive. - ACTION
Change message number value to a value that is between 1 and 32,766 inclusive.
- 10
- MESSAGE
MESSAGES MUST EITHER CONTAIN ALL NUMBERED OR ALL POSITIONAL PARAMETER SUBSTITUTION CHARACTERS.MIXES NOT ALLOWED. - CAUSE
During the scan of the message, GENCAT detected a mix of parameter substitution characters.For example, a messagecontained numeric substitution characters as well as positional substitution characters. - ACTION
Change the parameter substitution characters either to all numeric substitution or all positional substitution characters.(Note that this is for each message only.)
- 11
- MESSAGE
MESSAGE NUMBERS MUST BE IN ASCENDING SEQUENCE. - CAUSE
A message number was processed that is less than or equal to the previous message number.The message numbers within a set are not in ascending sequence. - ACTION
Arrange the messages within the set so that their numbers are in strict ascending order.
- 12
- MESSAGE
MESSAGE CONTAINS NON-BLANK CHARACTER IMMEDIATELY FOLLOWING
MESSAGE NUMBER. NON-BLANK CHARACTER ASSUMED TO BE A BLANK.
- CAUSE
GENCAT detected a non-blank character immediately following the
message number in a message. GENCAT replaces this character with
a blank. - ACTION
Insert a blank between the message number and the message text.
- 13
- MESSAGE
EXPECTED ONE OF THE FOLLOWING INPUTS:
0, 1, 2, 3, 4, OR A RETURN.
- CAUSE
GENCAT detected an incorrect input in response to the
first menu (which prompts for a function).
- ACTION
Respond only with 0, 1, 2, 3, 4, or a Return.
- 14
- MESSAGE
EXPECTED ONE OF THE FOLLOWING INPUTS:
0, 1, 2, 3, OR A RETURN.
- CAUSE
GENCAT detected an incorrect input in response to the menu
that prompts for the type of merging it is to perform.
- ACTION
Respond only with 0, 1, 2, 3, or a Return.
- 15
- MESSAGE
EXPECTED AN EXISTENT FILE AS INPUT.
- CAUSE
The file does not exist on the system.
- ACTION
Either create the file or input the name of a file
that does exist on the system.
- 16
- MESSAGE
EXPECTED A UNIQUE, NON-EXISTENT FILE NAME AS INPUT. - CAUSE
The file already exists on the system. The name of the file
should be one that does not exist on the system.
- ACTION
Purge the file or input the name of a file that does not
exist on the system.
- 17
- MESSAGE
EXPECTED A RESPONSE OF "YES" OR "NO" AS INPUT.
- CAUSE
GENCAT requires a response of either YES, yes,
NO, or no to the prompt of SAVE COLLISIONS?.
- ACTION
Respond with YES, yes, NO, or no.
- 18
- MESSAGE
INPUT FILES MUST HAVE EQUAL RECORD SIZES FOR THIS FUNCTION.
- CAUSE
Source and maintenance files must have equal record sizes if
the maintenance file is to modify the source file.
- ACTION
Create a maintenance file that has a record size equal to
the record size of the source file.
- 20
- MESSAGE
THE CONSTRUCT OF $DELSET IS NOT ALLOWED IN THE SOURCE.
- CAUSE
The construct $DELSET, which may be used in a maintenance
file, was detected in a source file during a maintenance function.
- ACTION
Remove $DELSET construct from the source file.
- 21
- MESSAGE
ONLY FIVE (5) POSITIONAL PARAMETER SUBSTITUTIONS ALLOWED
PER MESSAGE.
- CAUSE
GENCAT detected more than five (5) parameter substitution
characters in one message. Up to five parameter substitution
characters are allowed per message.
- ACTION
Only five (5) or fewer parameter substitution characters
per message.
- 22
- MESSAGE
MAINTENANCE FILE MUST BE NUMBERED FOR LINE-NUMBER
MERGES.
- CAUSE
The maintenance file is an unnumbered file. The maintenance
file must be a numbered file if it is to be used in a
line-number merge.
- ACTION
Number the maintenance file if the file is to be used in a
line-number merge.
- 23
- MESSAGE
SOURCE FILE MUST BE NUMBERED FOR LINE-NUMBER MERGES.
- CAUSE
The source file is an unnumbered file. The source file must
be a numbered file if it is to be used in a line-number merge.
- ACTION
Number the source file if the file is to be used in a
line-number merge.
- 24
- MESSAGE
SOURCE FILE CANNOT CONTAIN FORMS OF $EDIT.
- CAUSE
During a line-number merge, GENCAT examines the source
file for $EDIT and $EDIT VOID= constructs. These are
not allowed since if collision files are to be used,
an ambiguity would exist if the $EDIT and $EDIT VOID=
were left in the source file.
- ACTION
Remove all occurrences of $EDIT and $EDIT VOID= from
the source file.
- 25
- MESSAGE
SEQUENCE NUMBER IN $EDIT VOID RECORD CONTAINS TOO MANY
DIGITS. EIGHT IS THE MAXIMUM.
- CAUSE
The value following the $EDIT VOID= may have a maximum
of eight place holders.
- ACTION
Re-evaluate this value and correct it, as it represents a
line number.
- 26
- MESSAGE
FILE IS NOT A FORMATTED FILE.
- CAUSE
GENCAT can only expand formatted catalogs (for example, files
formatted by GENCAT).
- ACTION
Format the file using GENCAT.
- 27
- MESSAGE
SET RECORD IS REQUIRED BEFORE A MESSAGE RECORD IS FORMATTED.
- CAUSE
A message was found before the set number was defined.
- ACTION
Place the message in a set or place a set number before the
message.
- 28
- MESSAGE
VALUE IN RIGHT BYTE OF KANJI CHARACTER IS INVALID.
- CAUSE
Your message contains special escape sequences provided by
HP that are used for research and development activities.
These special escape sequences are not supported by Hewlett-Packard
and Hewlett-Packard assumes no responsibility for their use.
- ACTION
For messages 28 through 32, consult your Hewlett-Packard
representative, or remove all occurrences of the form
esc$<terminator> or ESC(<terminator> from your message
catalog. Where ESC is the escape character,
<terminator>
is "@" or "A" through "Z".
- 29
- MESSAGE
SCAN COMPLETED WITH NO CLOSING KANJI ESCAPE SEQUENCE.
EXPECTS A CLOSING KANJI ESCAPE SEQUENCE TO TERMINATE KANJI
CHARACTER SEQUENCE.
- CAUSE
See Message Number 28.
- ACTION
See Message Number 28.
- 30
- MESSAGE
INCOMPLETE KANJI CLOSING ESCAPE SEQUENCE DETECTED.
- CAUSE
See Message Number 28.
- ACTION
See Message Number 28.
- 31
- MESSAGE
VALUE IN LEFT-BYTE OF KANJI CHARACTER IS INVALID.
- CAUSE
See Message Number 28.
- ACTION
See Message Number 28.
- 32
- MESSAGE
VALUE IN PARAMETER SECTION OF KANJI ESCAPE SEQUENCE IS
INVALID. EXPECTED A STRING OF DIGITS.
- CAUSE
See Message Number 28.
- ACTION
See Message Number 28.
|