SNAX/APC Configuration and Management Manual

Event Management
SNAX/APC Configuration and Management Manual—138787
E-2
Subsystem Processes That Report Events
5. EMS logs—include the event (EMS) logs that were active when the problem
occurred.
6. Saveabend file—if SNAX/APC abends or hangs, it is important to get the SAVE file
of the SNAX/APC server. To accomplish this, when SNAX/APC drops into Inspect,
or if it hangs and you invoke Inspect via the DEBUG command, issue the SAVE
command.
7. Configuration/Startup files—if a configuration problem is suspected, the SCF
configuration file or an SCF command display of the following command can be
useful:
INFO PROCESS $apc-process-name, SUB ALL, DETAIL
8. Other files—other files might include APCLMAP, which resides on the SNAX/APC
installation subvolume and is used in formatting traces, and SNAX line trace files
from the underlying access method (SNAX/XF, SNAX/APN, or SNAX/CDF).
SNAX line trace files might be helpful when all else fails or when a low-level
problem (that is, within the lower SNA layers or basic line connectivity) is
encountered. The SNAX line trace should be accompanied by the SCF displays of
the SNAX lines, physical units (PUs) and logical units (LUs) that SNAX/APC
utilizes.
Subsystem Processes That Report Events
Not all event messages received by an application come from SNAX/APC; SNAX/APC
generates event messages for events that occur for the objects under its control. SCP
reports events when SPI messages fail or upon an internal failure of SPI. Event
messages issued by SCP contain the subsystem ID of SCP and an event token prefix of
ZCOM-; those issued by the SNAX/APC subsystem (having a prefix of ZAPC- or
ZCMK-) contain the SNAX/APC subsystem ID. For more information about subsystem
IDs, refer to the SPI Programming Manual. The SNAX/APC subsystem ID is
described in Section 4 of the SNAX/APC Management Programming Manual, “Common
Definitions.” The subsystem ID for SCP is described in the SPI Common Extensions
Manual.
Only the event messages with the prefix ZAPC- are described in this manual.
Common Events: -00001 Through -00999 and -32nnn Series Events
Event messages with the prefix ZCOM- or ZCMK- are common to more than one
Tandem product. The ZCOM- events have numbers ranging from -00001 to -00999.
The ZCMK- event numbers start at -32000. Since the ZCMK- event messages contain
the subsystem ID of SNAX/APC, a list of these events follows. Detailed information on
both the ZCMK- and ZCOM- events can be found in the SPI Common Extensions
Manual and the Operator Messages Manual. Note that the ZCMK- events in the
following list are subject to change, so this list may not contain all current events.