SNAX/XF and SNAX/APN Event Management Programming Manual

SNAX/APN Event Messages
SNAX/XF and SNAX/APN Event Management Programming Manual—426859-001
4-88
81: ZSX1-EVT-LUNS-ERR-CON
If the table named in ZSX1-TKN-LUNS-OBJ1 is an ESS table, change the SETESS
command in the SET table’s SNAXUTL input file and rebuild the table.
2319
Cause. An unsolicited logoff has been received for the LU named in ZSX1-TKN-
LUNS-OBJ2, and LUNS must inform the creator of the session, named in
ZSX1-TKN-LUNS-OBJ1. LUNS, however, cannot find the session creator named in
ZSX1-TKN-LUNS-OBJ1.
Effect. The unsolicited logoff is completed.
Recovery. If the problem persists, contact the Global Customer Support Center. Provide
all relevant information as follows:
•
Descriptions of the problem and accompanying symptoms
•
Details from the message(s) generated
•
Supporting documentation such as Event Management Service (EMS) logs, trace
files, and a CPU dump, if applicable
If your local operating procedures require contacting the Global Customer Support
Center (GCSC), please also supply your system number and the numbers and versions
of all related products.
2337
Cause. A SNAX/APN internal error occurred when a READLINK operation was
performed on the LU named ZSX1-TKN-LUNS-OBJ2 under the line named
ZSX1-TKN-LUNS-OBJ1.
The value of ZSX1-TKN-LUNS-INFO1 is the LCB address. The value of ZSX1-TKN-
LUNS-INFO2 is the LCB.LTRAN value (the length, in bytes, of the data transferred).
Effect. The request that was being processed is rejected.
Recovery. Try the request again. If the terminal is locked up, have the operator abort
and restart its LU through SCF. If the problem persists, contact the Global Customer
Support Center, providing all relevant information as follows:
•
Descriptions of the problem and accompanying symptoms
•
Details from the message(s) generated
Note. Error 2312 might be the result of using a RENAME command to change the object-file
name of a LUNS table. When you use this method to rename a table’s object file, the first
record in the file (the descriptor record) remains unchanged. For example, if you rename table
SET1O (table SET1’s object file) with the new name SET2O, the first record in file SET2O still
contains the table’s old file name SET1O. You must use the SNAXUTL SELECTFILE
command to change a table’s object-file name.
Note also that the volume and subvolume elements of the table’s fully qualified file name are
stored in the descriptor record but are not used in the validity check that produces LUNS error
2312.