SNAX/XF and SNAX/APN Event Management Programming Manual
SNAX/XF Event Messages
SNAX/XF and SNAX/APN Event Management Programming Manual—426859-001
3-86
81: ZSX1-EVT-LUNS-ERR-CON
Recovery. Depending on the nature of the failure, perform one or more of the following
steps:
1. Use the SCF INFO and STATUS commands to examine the condition of a named
object.
2. In the terminal’s ESS table, examine the named ESSCMD record. If necessary, refer
to the SNAX/XF LU Network Services Manual.
3. Correct any improper specifications in SCF commands or in ESSCMD records in
the terminal’s ESS table.
4. Using SCF, correct the state of any object that is in an improper state. If a gateway
PU or LU is in the Starting state, it must be activated from the host.
5. 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 (GCSC).
When contacting the Global Customer Support Center (GCSC), 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.
2307
Cause. LUNS was unable to get ZSX1-TKN-LUNS-INFO1 words of buffer space
when processing a request on behalf of the LU named ZSX1-TKN-LUNS-OBJ2 under
the line named ZSX1-TKN-LUNS-OBJ1.
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 the LU through SCF. If the problem persists, contact the Global Customer
Support Center (GCSC).
When contacting the Global Customer Support Center (GCSC), 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