OSI/TS Management Programming Manual

ZCOM Errors Returned by OSI/AS
Errors and Error Lists
056786 Tandem Computers Incorporated A–3
13: ZOS4-ERR-NO-BKUP This error is returned to the SWITCH PROCESS command when the TSP process has
no backup process running.
Tokens in Error List
ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST.
ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR.
ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING.
ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM.
ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSSCTL.
Token Descriptions
ZSPI-TKN-ERROR
is the standard SPI error list token, as described in the Distributed Systems
Management (DSM) Programming Manual. Its value consists of the OSI/TS
subsystem ID, the version, and the error number ZOS4-ERR-NO-BKUP. This
token is always present in the error list.
ZCOM-TKN-OBJNAME
contains the name of the process that reported the error. This token is always
present in the error list.
ZCOM-TKN-OBJTYPE
indicates the type of the object named in ZCOM-TKN-OBJNAME. The value of
this token is ZCOM-OBJ-PROCESS. This token is always present in the error list.
Probable Cause
There is no backup process active. Check that the configured CPU of the backup
process is up. Another possible cause might be that resources cannot be allocated by
the backup process. Check the Event Management Service (EMS) log for more
information.
Recommended Action
If the backup CPU is down, follow standard procedures to bring it back up. If its
resources cannot be allocated, you must acquire information from the EMS log. Look
for the exact reason.
If the resource problem is persistent, the TSP process must be restarted with a new
resource configuration. A resource could be the CPU, the size of buffer pool, or the
disk used to store the extended segment.
Resource allocation is performed by the PARAM mechanism. Refer to the Event
Management Service (EMS) Manual and the Tandem OSI/TS Manual for more
information.