RPC Server Front-End Messages

This section explains the messages that are issued by the RPC server front-end.

When a message of type "error message" appears, the RPC server environment is terminated abnormally.


RPC0001 PARM string missing

Type Error message.
Explanation The PARM string with the RPC server front-end parameters is not specified on the EXEC card.

RPC0002 Natural driver name too long: name

Type Error message.
Explanation The name of the Natural z/OS batch nucleus in the PARM string is longer than eight characters. The invalid name is shown in the message.

RPC0004 Thread size not numeric or too large: value

Type Error message.
Explanation The value for the thread size in the PARM string is invalid. The invalid value is shown in the message.

RPC0006 Thread number not numeric or too large: value

Type Error message.
Explanation The value for the number of threads in the PARM string is invalid. The invalid value is shown in the message.

RPC0007 Natural driver not found: name

Type Error message.
Explanation The Natural z/OS batch nucleus could not be loaded. Check your STEPLIB concatenation.

RPC0010 Authorized environment for impersonation established

Type Informational message.
Explanation Indicates that impersonation is possible in z/OS mode. This message is issued if the Natural RPC server front-end has been linked with AC=1 and is loaded from an APF authorized library.

RPC0011 Starting Natural RPC server

Type Informational message.
Explanation Normal startup message.

RPC0012 Restarting Natural RPC server

Type Informational message.
Explanation Indicates a problem with the Roll Server. This message is typically issued if an active Natural session has been deleted from the Roll Server.

RPC0013 Terminating Natural RPC server

Type Informational message.
Explanation The Natural RPC server environment is terminated normally.

RPC0014 Natural Security logon failed or missing on Natural STACK

Type Error message.
Explanation If Natural profile parameter AUTO=OFF is specified, a Natural Security logon must be provided with the profile parameter STACK.

RPC0015 Impersonation failed with SAF RC/reason xxxx/yyyy

Type Informational message.
Explanation Informational message in the RPC server trace.

RPC0016 Impersonation failed with CICS RC/reason xxxx/yyyy

Type Informational message.
Explanation Informational message in the RPC server trace.

xxxx is the hexadecimal EIBRESP value and yyyy is the hexadecimal EIBRESP2 value of the CICS command that has failed.

Typical EIBRESP values are:

x'45' (USERIDERR) Unknown user ID.
x'46' (NOTAUTH) Wrong password, expired password, revoked user ID, or no surrogate user.
x'1C' (TRANSIDERR) Unknown transaction ID.
x'12' (NOSPACE) No space to write control record to TS queue.
x'FF' Impersonation task could not be started due to resource contention.

RPC0017 Initializing Natural RPC server environment

Type Informational message.
Explanation Normal startup message to indicate the intialization of the Natural RPC server environment.

RPC0018 Creating Natural RPC server session template

Type Informational message.
Explanation Normal startup message to indicate the creation of a Natural template session that is used by all subsequently started Natural RPC servers.

RPC0019 Terminating Natural RPC server environment

Type Informational message.
Explanation The Natural RPC server environment is terminated normally.

RPC0020 Disconnecting Natural RPC server from transport

Type Informational message.
Explanation This message is issued during abnormal termination of a Natural RPC server.