Subsystem Control Point (SCP) Management Programming Manual

Event Messages
Subsystem Control Point (SCP) Management Programming Manual—520619-001
6-20
22 ZSCP-EVT-TIMEOUT-MSG-REJ
Cause. The SCP RCB is full. The SCP process is receiving new command messages
more quickly than pending commands are being processed.
Effect. The SCP process issues this event message and stops reading command
messages until table space becomes available (as pending command messages are
completed).
Recovery. Divide the processing load by starting and opening additional SCP
processes. If the event begins to repeat, notify the system manager.
22 ZSCP-EVT-TIMEOUT-MSG-REJ
The SCP process received and discarded system message -22.
ZSCP-TKN-TAG
contains the timeout command-message tag number.
Cause. The SCP process received and discarded system message –22. When a
SIGNALTIMEOUT timer finishes, system message –22 is returned on SCP’s
$RECEIVE file with a tag matching the tag assigned by the file system at the time of the
SIGNALTIMEOUT call. This event indicates that the tag returned in the system
message does not match any existing SIGNALTIMEOUT tag.
Effect. The system-message tag is ignored. The SCP process issues the event message
and continues processing.
Recovery. If the event begins to repeat, notify the system manager.
23 ZSCP-EVT-SCB-FULL
The SCP process cannot open an additional subsystem.
Cause. The SCP process cannot open an additional subsystem. An SCP process records
information about each open subsystem process in an internal table called the server
control block (SCB) table. This table can contain a maximum of 256 entries, so an SCP
process can maintain up to 256 concurrent subsystem process opens. When an SCP
Tokens in Event Message
ZSCP-TKN-TAG <1> token-type ZSPI-TYP-INT.
Message Text
Bad timeout tag: <1>
Tokens in Event Message
(contains only standard event-message tokens)
Message Text
Subserver open table full