DSM/Tape Catalog Management Programming Manual

SSI Event Messages
DSM/Tape Catalog Management Programming Manual—520481-003
C-46
4 ZSSI-EVT-FATAL-FAULT,
zssi-val-msg-TCP-CLNTCREATE (17)
•
Overload of CPU—too many demands were made of the CPU, causing it to use up
internal resources (such as memory allocated for TLEs).
Effect. $ZSSI terminates.
Recovery. Recovery depends on the cause of the error:
•
If the configured memory was insufficient, you might need to increase the
PMAP_MAXENTRIES define attribute (default 1000) in the portmapper.
•
If disk space was insufficient, move the data-swap volume to a disk with more
available space.
•
If a CPU overload occurred, you might need to run the process on another CPU
that is not heavily loaded, or you might need to reconfigure the system to increase
the amount of system resources (such as system data space for TLEs and process
control blocks).
4 ZSSI-EVT-FATAL-FAULT, zssi-val-msg-TCP-CLNTCREATE (17)
The attempted RPC TCP connection is not possible due to an error in the client system
network.
ZSSI-TKN-STRING
is an optional token containing the detailed error message generated by the RPC
service itself. In most cases, this message is “Program number not registered,”
which indicates that either the CSI or the $ZSSI is not running.
ZSSI-TKN-ADDRESS
contains the address of the client host.
ZSSI-TKN-PORT
contains the port number of the client where a connection was attempted.
Cause. The attempted TCP connection is not possible. This is an error in the client
system network.
Tokens in Event Message
ZSSI-TKN-PROC-CALLER token-type ZSPI-TYP-STRING.
ZSSI-TKN-MSG token-type ZSSI-TYP-MSG.
ZSSI-TKN-STAT token-type ZSSI-TYP-STAT
ZSSI-TKN-PROC-FAILED token-type ZSPI-TYP-STRING
ZSSI-TKN-STRING <1> token-type ZSPI-TYP-STRING.
ZSSI-TKN-ADDRESS <2> token-type ZRPC-TYP-IP-ADDR.
ZSSI-TKN-PORT <3> token-type ZSPI-TYP-INT.
Message Text
RPC TCP client connection failed: <1>,
Address: <2>, Port: <3>