DSM/Tape Catalog Messages Manual

Remote Procedure Call Messages
DSM/Tape Catalog Messages Manual — 422947-007
10 - 15
5: ZRPC-EVT-RPC-ERR
ZEMS-TKN-EMPHASIS
is a header token that contains the value ZSPI-VAL-TRUE, indicating that this is a
critical event.
Event-Message Text
In the text message, 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.
Probable 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. This value can
be interpreted as follows:

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 and the Guardian Procedure Errors and
Messages Manual.

Values greater than 32000 indicate an SPI procedure error. The true SPI error
value can be calculated by subtracting 32000 from the Z-ERROR value and
multiplying 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).
SPI procedure errors are defined in the Distributed Systems Management (DSM)
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.
Recommended Action
The recommended action depends on the cause of the error:

If the error indicates that the NonStop 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 TCP/IP process for a configurable period of time. If communications are
reestablished, the portmapper process reopens its sockets and proceeds as usual.
If after the configurable period of time, communications have not been
reestablished, the portmapper process abends, and operator intervention is
required to restart the process.

If any other errors occurred, refer to the locations indicated previously for the
appropriate recovery procedures. All other errors are considered fatal and cause
the portmapper process to log the event and abend.