DSM/Tape Catalog Management Programming Manual

RPC Event Messages
DSM/Tape Catalog Management Programming Manual—520481-003
B-12
5 ZRPC-EVT-RPC-ERR
ZCOM-TKN-SUBJ-FILE
is the only possible value that can be returned as the subject token. ZCOM-TKN-
SUBJ-FILE indicates the name of the socket file in which the error occurred.
ZEMS-TKN-EMPHASIS
is a header token that contains the value ZSPI-VAL-TRUE, indicating that this
event is critical.
In the message text, sockfile corresponds to the value in ZCOM-TKN-SUBJ-FILE.
rpc corresponds to the value in ZSPI-TKN-PROC-ERR within the error list. error
corresponds to the Z-ERROR field in ZSPI-TKN-ERROR within the error list.
errortext is the error text that corresponds to the value of the Z-ERROR field in
ZSPI-TKN-ERROR within the error list.
Cause. An RPC library procedure failed. The value returned for the Z-ERROR field in
ZSPI-TKN-ERROR within the error list indicates the cause of the error. You can
interpret this value as:
•
RPC errors are defined in the $SYSTEM.SYSTEM.ERR04 source file.
•
Values in the range 0 through 255 indicate a file-system error. File-system errors
are defined in the ZSPIDEF.ZFILDDL file.
•
Values greater than 32000 indicate an SPI procedure error. To calculate the true
SPI error value, subtract 32000 from the Z-ERROR value and multiply the result by
-1 (that is, SPI value = - (error -32000). For example, a Z-ERROR value
of 32001 indicates an SPI error of -1 (Invalid Buffer). For definitions of SPI
procedure errors, see the SPI Programming Manual.
The most likely cause of this event is that the TCP/IP process is inaccessible because
either the process was down or the network connection was lost.
Effect. The portmapper drops the request that resulted in this error. If the error
indicates that the NonStop Kernel TCP/IP process was inaccessible (file-system error
201 or 250), the portmapper process records the event, closes all open sockets, and
then periodically tries to reestablish communications with the NonStop Kernel TCP/IP
process for a configurable period of time. If communications are reestablished, the
portmapper process reopens its sockets and proceeds as usual. If communications
have not been reestablished after the configurable period of time, the portmapper
process abends.
Recovery. Operator intervention is required to restart the process. For descriptions of
file-system errors, see the Operator Messages Manual. For descriptions of TCP/IP
error lists, see the TCP/IP Management Programming Manual. For more information
on TCP/IP configuration, see the TCP/IP Configuration and Management Manual.