HP 3000 Manuals HP 3000 Manuals
OCA Program Error Messages
There are two classes of program error messages generated by OCA:
* User input errors that cause syntax and semantic errors
* Internal error messages
User Input Errors
OCA generates and displays to $STDLIST error messages for any syntax and
semantic errors associated with user input. OCA follows these guidelines
when generating this class of error messages:
* Displays file system error messages.
* Echoes user input.
* Attempts to point to the error with a carat (^).
* Numbers the errors in the order they were discovered (usually left
to right).
* Identifies the file that OCA was reading when the error occurred
and prints the name at the end of the error message. ("****" is
printed instead of$STDIN or $STDINX.)
Figure B-9 illustrates incorrect user input at the SCAN prompt, and
the resulting user input errors that are displayed to the screen. The
user responds to the SCAN prompt with the indirect file IFILE. Errors
occur when OCA scans the first line in IFILE, BADFILG;;LIB;&. Next, the
user responds to the SCAN prompt with the file name NOTFILE; a file
system error is displayed.
__________________________________________________________________
| |
| |
| SCAN> ! IFILE;LIB=G -- read from IFILE.PUB.PERS |
| BADFILE;;LIB; ^1 ^2,3 |
| ^4,5 |
| ERROR 1: Missing option. Expected one of LIB, BRIEF, or |
| DETAILED (IFILE.PUB.PERS) |
| ERROR 2: Missing = after LIB (IFILE.PUB.PERS) |
| ERROR 3: Missing G, P, or S after = (IFILE.PUB.PERS) |
| ERROR 4: Missing option. Expecting one of LIB, BRIEF, or |
| DETAILED (IFILE.PUB.PERS) |
| ERROR 5: Extraneous input after command (IFILE.PUB.PERS) |
| SCAN>NOTFILE |
| NONEXISTENT PERMANENT FILE (FSERR 52) |
| NOTFILE |
| ^1 |
| ERROR 1: Unable to open NOTFILE.PUB.PERS **** |
| |
__________________________________________________________________
Figure B-9. Sample OCA Error Message Display
Internal Error Messages
The following section lists internal program error numbers and the
corresponding messages generated by OCA. This error information contains:
* Internal error numbers
* The complete error message
* The probable cause of the error
* Action to take to correct the error
101 MESSAGE INTERNAL ERROR 101: CATREAD failed in REPORT.
Display of message with NLS failed.
Msg_num = nnn Set_num = nnn CATREAD error = nnn
CAUSE Attempting to display a message from the catalog file via the
REPORT procedure. CATREAD failed for some reason. Possible
causes of the CATREAD failure are explained in the MPE V/E
Native Language Support Reference Manual (32414-190001).
ACTION This error is likely to occur if the OCA catalog has been
incorrectly localized. If the catalog name is
OCCAT000.PUB.SYS, then this may be because of a bug in OCA, not
a problem with localization. You should attempt to verify that
the catalog file is not corrupt by restoring it from the
product tape. If this failure persists, please contact a
Hewlett-Packard Support Representative. Include all
information printed by OCA when it aborted.
102 MESSAGE INTERNAL ERROR 102: NLSCANMOVE error.
NLSCANMOVE error nnn Attempting to NLUPSHIFT.
(or)
NLSCANMOVE error nnn Attempting to NLDOWNSHIFT.
CAUSE NLSCANMOVE intrinsic failed attempting to either upshift or
downshift a string. Possible causes of the NLSCANMOV E failure
are explained in the MPE V/E Native Language Support Reference
Manual (32414-90001).
ACTION Ask your System Manager to confirm that NLS has been correctly
configured for your system (especially for the language
associated with the number assigned to the JCW NLUSERLANG). If
you are not using a localized version of OCA then this should
not be an issue. Please contact a Hewlett-Packard Support
Representative. Include all information printed by OCA when it
aborted.
Table B-7. (cont.)
103 MESSAGE INTERNAL ERROR 103: CATREAD failed during NLDISPLAY.
Display of message with NLS failed.
Msg_num=nnn Set_num=nnn CATREAD error=nnn
CAUSE Attempting to display a message from the catalog file via the
NLDISPLAY procedure. CATREAD failed for some reason. Possible
causes of the CATREAD failure are explained in the MPE V/E
Native Language Support Reference Manual (32414-90001).
ACTION This error is likely to occur if the OCA catalog has been
incorrectly localized. If the catalog name is
OCCAT000.PUB.SYS, then this may be because of a bug in OCA, not
a problem with localization. You should attempt to verify that
the catalog file is not corrupt by restoring it from the
product tape. If this failure persists, please contact a
Hewlett-Packard Support Representative. Include all
information printed by OCA when it aborted.
104 MESSAGE INTERNAL ERROR 104: CATREAD failed during NLPROMPT.
Display of message with NLS failed.
Msg_num=nnn Set_num=nnn CATREAD error=nnn
CAUSE Attempting to display a message from the catalog file via the
NLPROMPT procedure. CATREAD failed for some reason. Possible
causes of the CATREAD failure are explained in the MPE V/E
Native Language Support Reference Manual (32414-90001).
ACTION This error is likely to occur if the OCA catalog has been
incorrectly localized. If the catalog name is
OCCAT000.PUB.SYS, then this may be because of a bug in OCA, not
a problem with localization. You should attempt to verify that
the catalog file is not corrupt by restoring it from the
product tape. If this failure persists, please contact a
Hewlett-Packard Support Representative. Include all
information printed by OCA when it aborts.
Table B-7. (cont.)
105 MESSAGE INTERNAL ERROR 105: Unable to retrieve localized string from
OCCATnnn.PUB.SYS. CATREAD error nnn OCA cannot continue.
(or)
String read from catalog is too long. (MAX=nnn Chars.)
String: the actual string read from catalog(nnn)
CAUSE Attempting to CATREAD a localizable string from the OCA
catalog, a problem is encountered. The problem is either a
CATREAD error (which can be diagnosed by looking up the CATREAD
error number in the MPE V/E Native Language Support Reference
Manual (32414-90001)) or a problem with the length of an
internal buffer passed inside of OCA.
ACTION This error is likely to occur if the OCA catalog has been
incorrectly localized. If the catalog name is
OCCAT000.PUB.SYS, then this may be because of a bug in OCA, not
a problem with localization. You should attempt to verify that
the catalog file is not corrupt by restoring it from the
product tape. If this failure persists, please contact a
Hewlett-Packard Support Representative. Include all
information printed by OCA when it aborted.
106 MESSAGE INTERNAL ERROR 106: Unable to find keyword in catalog
message.
Catalog message: actual message read from catalog Keyword:
expected keyword Message number: nnn
CAUSE After reading a localizable message from the catalog, it was
searched for a keyword. This keyword was not found. The
message read from the catalog and the expected keyword are
included in the error message.
ACTION Contact a Hewlett-Packard Support Representative. Include all
information printed by OCA when it aborted.
107 MESSAGE INTERNAL ERROR 107: Cannot Obtain NLUPSHIFT Table For
Language nnn.
NLINFO Error nnn during SETUP.
CAUSE NLS intrinsic NLINFO returned an error when the UPSHIFT table
for language nnn was requested. Possible causes of the NLINFO
failure are explained in the MPE V/E Native Language Support
Reference Manual (32414-90001).
ACTION Ask your system manager to confirm that NLS has been correctly
configured for your system (especially for the language
associated with the number assigned to the JCW NLUSERLANG). If
you are not using a localized version of OCA, then this should
not be an issue. Contact a Hewlett-Packard Support
Representative. Include all information printed by OCA when it
aborted.
Table B-7. (cont.)
108 MESSAGE INTERNAL ERROR 108: Cannot Obtain NLDOWNSHIFT Table For
Language nnn.
NLINFO Error nnn during SETUP.
CAUSE NLS intrinsic NLINFO returned an error when the DOWNSHIFT table
for language nnn was requested. Possible causes of the NLINFO
failure are explained in the MPE V/E Native Language Support
Reference Manual (32414-90001).
ACTION Ask your system manager to confirm that NLS has been correctly
configured for your system (especially for the language
associated with the number assigned to the JCW NLUSERLANG). If
you are not using a localized version of OCA, then this should
not be an issue. Contact a Hewlett-Packard Support
Representative. Include all information printed by OCA when it
aborted.
109 MESSAGE INTERNAL ERROR 109: Unable to get localized yes/no string.
NLINFO error nnn Attempting to get NLS yes/no for language nnn.
CAUSE NLS intrinsic NLINFO returned an error when the localized
yes/no string for language nnn was requested. Possible causes
of the NLINFO failure are explained in the MPE V/E Native
Language Support Reference Manual (32414-90001).
ACTION Ask your system manager to confirm that NLS has been correctly
configured for your system (especially for the language
associated with the number assigned to the JCW NLUSERLANG). If
you are not using a localized version of OCA then this should
not be an issue. Contact a Hewlett-Packard Support
Representative. Include all information printed by OCA when it
aborted.
110 MESSAGE INTERNAL ERROR 110: NLAPPEND Error nnn.
Unable To Open Catalog File OCCATnnn.PUB.SYS.
OCA Cannot Continue.
CAUSE NLAPPEND intrinsic returned error nnn. Possible causes of the
NLAPPEND failure are explained in the MPE V/E Native Language
Support Reference Manual (32414-90001).
ACTION Ask your system manager to confirm that NLS has been correctly
configured for your system (especially for the language
associated with the number you assigned to the JCW NLUSERLANG).
If you are not using a localized version of OCA, then this
should not be an issue. Contact a Hewlett-Packard Support
Representative. Include all information printed by OCA when it
aborted.
Table B-7. (cont.)
111 MESSAGE INTERNAL ERROR 111: CATOPEN Error nnn.
Unable To Open Catalog File OCCATnnn.PUB.SYS.
OCA Cannot Continue.
CAUSE CATOPEN intrinsic returned error nnn when attempting to open
the OCA catalog file. Possible causes of the CATOPEN failure
are explained in the MPE V/E Native Language Support Reference
Manual (32414-90001).
ACTION Make sure the catalog file mentioned in the message exists in
the correct group and account, and has the current file code
(MGCAT). If it does not, then obtain a copy of the correct
formatted catalog file from your System Manager. If you cannot
take care of the problem in this manner, contact a
Hewlett-Packard Support Representative. Include all
information printed by OCA when it aborted.
200 to 299 MESSAGE 200...299 Message (Various Messages)
CAUSE Corruption of internal data structures.
ACTION Contact a Hewlett-Packard Support Representative.
300 MESSAGE INTERNAL ERROR 300: Duplicate/ambiguous keyword in table.
CAUSE An attempt was made to add a duplicate of ambiguous entry to
one of the OCA keyword tables.
ACTION This error is likely to occur if the OCA catalog has been
incorrectly localized. If the catalog name is
OCCAT000.PUB.SYS, then this may be because of a bug in OCA, not
a problem with localization. You should attempt to verify that
the catalog file is not corrupt by restoring it from the
product tape. If this failure persists, please contact a
Hewlett-Packard Support Representative. Include all
information printed by OCA when it aborted.
301 MESSAGE INTERNAL ERROR 301: Attempt to insert too many keywords in
table.
CAUSE One of OCA's internal keyword tables is full and an attempt has
been made to make another entry. This table needs to be
expanded.
ACTION Contact a Hewlett-Packard Support Representative. Include all
information printed by OCA when it aborted.
Table B-7. (cont.)
302 MESSAGE INTERNAL ERROR 302: Bad keyword index.
CAUSE Attempting to access an entry in one of OCAs internal keyword
tables using an invalid index.
ACTION Contact a Hewlett-Packard Support Representative. Include all
information printed by OCA when it aborted.
303 MESSAGE INTERNAL ERROR 303: SL directory entry points to deleted
segment. Bad SL file, n1, detected.
CAUSE OCA has determined that the directory contained in the SL file
it scanned is corrupted. Specifically it determined that a
directory entry points to an entry point which has been deleted
from that SL file. This is not an internal error in OCA, but
rather an internal error in the SL file scanned by OCA.
ACTION Do not contact a Hewlett-Packard Support Representative unless
the SL file corruption persists, and you can determine what is
causing the corruption. In that case, submit the Service
Request against the product which is corrupting the SL file,
not against OCA. The best corrective action is to rebuild the
SL file. If this is not possible (because you do not have
access to the source or the USL file), contact the creator of
the SL file to get a new copy.
304 MESSAGE INTERNAL ERROR 304: I/O error occurred while writing to the
report file (OCALIST).
CAUSE When attempting to write (either via FWRITE or CATREAD) a
message to the formal file designator OCALIST, an I/O error
occurred. This will have occurred either during the generation
of an OCA report or during the printing of OCA HELP text. In
either case, if you specified the ;OFFLINE option, the
characteristics of the file OCALIST can be controlled by
issuing an MPE :FILE equation. If you did not specify
;OFFLINE, then your output is being directed to $STDLIST, and
:FILE equations will be ignored.
ACTION If the ;OFFLINE option was specified, then check to see if a
:FILE equation is in effect by issuing the MPE command :LISTEQ.
Look for a :FILE equation for OCALIST. The most common cause of
this problem is encountering End Of File on OCALIST when
OCALIST is redirected to a disk file. If that is the case, use
the ;DISC= option on the :FILE command to increase the limit on
the disk file. If you did not specify ;OFFLINE or cannot
figure out how to correct the problem with a file equation
contact your Hewlett-Packard Support Representative.
Table B-7. (cont.)
305 MESSAGE INTERNAL ERROR 305: FREADDIR intrinsic failed.
CAUSE The most likely cause of this problem is either program or SL
file corruption (of the program or SL file being scanned, not
of the OCA program file). If you are scanning a program file
when you get this error, you can double check to see if it is
corrupt by attempting to :RUN the program. If it is corrupted,
the MPE loader will probably print a similar message to the one
printed by OCA. If you are scanning a program file with the
;LIB= option and get this error, then the corruption may be in
the SL file, not the program file. The error message should
indicate which file is corrupt. Again, you can verify that the
file is corrupted by running the program with the same ;LIB=
parameter. Hewlett-Packard does not suggest that you attempt
to run the program if it contains any Privileged Mode code and
you get this error from OCA. Privileged Mode code could be
dangerous if the program file is indeed corrupted.
ACTION Do not contact a Hewlett-Packard Support Representative unless
the file corruption persists, and you can determine what is
causing the corruption. In that case, submit the Service
Request against the product which is corrupting the file, not
against OCA. The best corrective action is to rebuild the
program or SL file. If this is not possible (because you do
not have access to the source or the USL file), contact the
creator of the SL file to get a new copy.
306 MESSAGE INTERNAL ERROR 306: FFILEINFO intrinsic failed on filename.
CAUSE The MPE FFILEINFO intrinsic failed when attempting to get
information about the file filename.
ACTION Contact a Hewlett-Packard Support Representative. Include all
information printed by OCA when it aborted.
307 MESSAGE INTERNAL ERROR 307: FCLOSE failed on SL file filename.
CAUSE OCA attempted to close the SL file filename using the MPE
FCLOSE intrinsic. The FCLOSE failed. This message will be
followed by a file system error message which should give you a
better idea as to why the FCLOSE failed.
ACTION Contact a Hewlett-Packard Support Representative. Include all
information printed by OCA when it aborted. Please note that
this error does not invalidate in any way the results which
were printed by OCA. The reports and migration information
contained within the reports will still be accurate.