Subsystem Control Point (SCP) Management Programming Manual

Errors
Subsystem Control Point (SCP) Management Programming Manual—520619-001
A-9
–995 ZCOM-ERR-SERVNAME-INV
–995 ZCOM-ERR-SERVNAME-INV
An invalid communications subsystem process name was specified by ZSPI-TKN-
MANAGER, ZCOM-TKN-XMGR, or ZCOM-TKN-OBJNAME.
Cause. The SCP process did not execute this command message because the
communications subsystem process specified by ZSPI-TKN-MANAGER, ZCOM-TKN-
XMGR, or ZCOM-TKN-OBJNAME did not exist or could not be opened.
Effect. The command is rejected.
Recovery. Correct the manager process name and reissue the request.
–996 ZCOM-ERR-SERV-ERR
A subsystem returned an SPI error in response to a GETVERSION command issued by
the SCP process.
ZCOM-TKN-SERV-ERR
contains the SPI error code returned by the subsystem.
Cause. The subsystem detected an SPI error while decoding or responding to the
GETVERSION command that the SCP process issues as part of its subsystem open
activity. SPI errors are generally caused by some problem with the SPI buffer format or
content. See the Guardian Procedure Errors and Messages Manual.
Effect. The original command issued by the requester is canceled, and SCP includes
this error list in the response. SCP processes also generate the event ZSCP-EVT-BAD-
GETVSN. See Section 6, Event Messages
.
ZSPI-TKN-ERRLIST
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
Corresponding SCF Error Message
Internal Error: invalid name specified in MANAGER or OBJNAME
token
ZSPI-TKN-ERRLIST
ZSPI-TKN-ERROR token-type ZSPI-TYP-ERROR
ZCOM-TKN-SERV-ERR <1> token-type ZSPI-TYP-INT
ZCOM-TKN-OBJNAME <2> token-type ZSPI-TYP-STRING
ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM
ZSPI-TKN-ENDLIST
Corresponding SCF Error Message
Internal Error: SPI return code <1> received on initial
GETVERSION to <2>