Operator Messages Manual
Chapter 85 SCP (Subsystem Control Point) Messages
The Subsystem Control Point (SCP) processes send the messages
in this chapter. The subsystem ID displayed by these messages includes
SCP as the subsystem name. Fatal events (1-17) cause the SCP process or its backup to stop.
If SCP stops and SAVEABEND is selected as a run option, a save file
is created in the subvolume from which SCP was run. The save file
is named ZZSAnnnn, where nnnn is a numeric value assigned by the system.
You can examine the save file using Inspect.  |  |  |  |  | NOTE: Negative-numbered messages are common to most subsystems. If
you receive a negative-numbered message that is not described in this
chapter, see Chapter 15. |  |  |  |  |
1 SIGNALTIMEOUT for shutdown failed | Cause An SCP call to the SIGNALTIMEOUT procedure failed. An SCP process
calls SIGNALTIMEOUT before stopping so unexecuted commands can be
processed. The SCP process passes the length of the delay and the
SIGNALTIMEOUT procedure, then initiates the delay. The procedure can fail due to a shortage of time-list elements
(TLEs). TLEs are system resources configured during system generation.
The system allocates one TLE for each call to a timeout procedure.
If all configured TLEs are allocated, a procedure call requiring a
TLE fails. Effect The SCP process issues this message, stops its backup process
if there is one, and calls the ABEND or PROCESS_STOP_ procedure. The
file system returns error 201 (nonexistent process) to every application
that is awaiting a response from the SCP process. The process that
created the SCP process receives system message -101, indicating process
abnormal deletion. Recovery Direct command messages to another SCP process, or hold them
until another SCP process is started. For more information on SIGNALTIMEOUT
errors, see the Guardian Procedure Errors and Messages
Manual. |
2 ALLOCATESEGMENT failed: error | Cause An SCP call to the ALLOCATESEGMENT or SEGMENT_ALLOCATE_ procedure
failed. The SCP process calls these procedures to allocate extended
data segments in memory. The cause of the failure is related to the
specific error returned in this message. Effect The SCP process issues this message and calls the ABEND or PROCESS_STOP_
procedure. The backup SCP process receives system message -101, indicating
process abnormal deletion. The backup process takes over. Recovery If there is no backup process, direct command messages to another
SCP process or hold them until another SCP process is started. Errors
-5 and -6 indicate a data pages (memory) resource problem, which might
mean that the system is overloaded. For ALLOCATESEGMENT and SEGMENT_ALLOCATE_
error codes, see the Guardian Procedure Errors and Messages
Manual. |
3 USESEGMENT failed | Cause The SCP process called the USESEGMENT procedure to access a
segment, but the procedure failed because the specified segment has
not been allocated. Effect The SCP process issues this message, stops the backup process
if there is one, and calls the ABEND or PROCESS_STOP_ procedure. The
file system returns error 201 (nonexistent process) to every application
that is awaiting a response from the SCP process. The process that
created the SCP process receives system message -101, indicating process
abnormal deletion. Recovery If there is no backup process, direct command messages to another
SCP process or hold them until another SCP process is started. If
the problem recurs, contact your service provider and provide all
relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
4 Backup received invalid checkpoint | Cause An SCP call to the CHECKPOINT procedure failed. The CHECKPOINT
procedure checkpoints data into the CHECKMONITOR data area of the
backup process. Effect The backup process does not have the information it needs to
take over if the primary process stops. The SCP process stops the
backup process if there is one, and calls the ABEND or PROCESS_STOP_
procedure. The file system returns error 201 (nonexistent process)
to every application that is awaiting a response from the SCP process.
The process that created the SCP process receives system message -6
or -101, indicating process abnormal deletion. Recovery Direct command messages to another SCP process or hold them
until another SCP process is started. The SCP process might need more
data pages. Try restarting the SCP process using a larger value for
the SEGPAGES or DATAPAGES startup parameter. If the problem recurs,
contact your service provider and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, and a processor dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
5 $RECEIVE READUPDATE error: error | Cause An SCP call to the READUPDATE procedure returned the indicated
error. The SCP process calls READUPDATE to communicate with another
process using the file $RECEIVE. Effect The SCP process issues this error message and calls the ABEND
or PROCESS_STOP_ procedure. The backup SCP process receives system
message -101, indicating process abnormal deletion. The backup process
takes over. If there is no backup process, the file system returns error
201 (nonexistent process) to every application that is awaiting a
response from the SCP process. The process that created the SCP process
receives system message -101, indicating process abnormal deletion. Recovery If there is no backup process, direct command messages to another
SCP process or hold them until another SCP process is started. If
the problem recurs, contact your service provider and provide all
relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
6 AWAITIO on $RECEIVE error: error | Cause An SCP call to the AWAITIO procedure failed on the file $RECEIVE
with the indicated error. SCP calls AWAITIO to complete an I/O operation
initiated by a procedure such as READUPDATE. AWAITIO returned a condition
code other than CCE, possibly due to an error in the SCP program. Effect The SCP process issues this error message and calls the ABEND
or PROCESS_STOP_ procedure. The backup SCP process receives system
message -101, indicating process abnormal deletion. The backup process
takes over. If there is no backup process, the file system returns error
201 (nonexistent process) to every application that is awaiting a
response from the SCP process. The process that created the SCP process
receives system message -101, indicating process abnormal deletion. Recovery If there is no backup process, direct command messages to another
SCP process or hold them until another SCP process is started. If
the problem recurs, contact your service provider and provide all
relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
7 Internal table error; type type; error: error | Cause The SCP process could not access an internal table required
for processing. A common cause is a table overflow. Effect The SCP process issues this message and calls the ABEND or PROCESS_STOP_
procedure. The backup SCP process receives system message -101, indicating
process abnormal deletion. The backup process takes over. If there is no backup process, the file system returns error
201 (nonexistent process) to every application that is awaiting a
response from the SCP process. The process that created the SCP process
receives system message -101, indicating process abnormal deletion. Recovery If there is no backup process, direct command messages to another
SCP process or hold them until another SCP process is started. If
the problem recurs, contact your service provider and provide all
relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
8 SWITCH command failed | Cause A SWITCH command issued to the SCP process failed because of
a problem with the CHECKPOINT procedure, which SCP calls to complete
the SWITCH command. Effect The backup process does not receive the most recent checkpoint
information. The SCP process issues this message and calls the ABEND
or PROCESS_STOP_ procedure. The backup SCP process receives system
message -101, indicating process abnormal deletion, and resumes processing
from a previous checkpoint. If there is no backup process, the file system returns error
201 (nonexistent process) to every application that is awaiting a
response from the SCP process. The process that created the SCP process
receives system message -101, indicating process abnormal deletion. Recovery If there is no backup process, direct command messages to another
SCP process or hold them until another SCP process is started. If
the problem recurs, contact your service provider and provide all
relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
9 CHECKPOINT data has overflowed | Cause An SCP call to the CHECKPOINT procedure failed. The SCP process
tried to checkpoint too much data (the stack size, the counts for
all of the buffers, and the total size of all of the file sync blocks). Effect The backup process does not receive the most recent checkpoint
information. The SCP process issues this message and calls the ABEND
or PROCESS_STOP_ procedure. The backup SCP process receives system
message -101, indicating process abnormal deletion, and resumes processing
from a previous checkpoint. If there is no backup process, the file system returns error
201 (nonexistent process) to every application that is awaiting a
response from the SCP process. The process that created the SCP process
receives system message -101, indicating process abnormal deletion. Recovery If there is no backup process, direct command messages to another
SCP process or hold them until another SCP process is started. If
the problem recurs, contact your service provider and provide all
relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
10 Internal error in backup | Cause The SCP backup process encountered an internal error. Effect The backup process stops immediately. The primary process is
notified with a system message -101, indicating process abnormal deletion,
and starts another backup process. If there is a process control block (PCB) problem, a memory
allocation problem, a swap file problem, or a communication problem
with a processor-monitor process, the SCP process keeps trying to
create a backup process. If there is any other problem, the SCP process
abandons its attempt to create a backup process. Recovery Contact your service provider and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
11 Unrecoverable SPI error: error | Cause An SCP call to one of the operating system Subsystem Programmatic
Interface (SPI) procedures failed. The SCP uses the SPI interface
to communicate with management applications, the Event Management
Services (EMS) collector, and subsystems. Effect The SCP process calls the ABEND or PROCESS_STOP_ procedure and
stops. The backup process created the SCP process. It receives system
message -101, indicating process abnormal deletion. The backup process
resumes processing. If there is no backup process, the file system returns error
201 (nonexistent process) to every application that is awaiting a
response from the SCP process. The process that created the SCP process
receives system message -101, indicating process abnormal deletion. Recovery If there is no backup process, direct command messages to another
SCP process or hold them until another SCP process is started. If
the problem recurs, contact your service provider and provide all
relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
12 Internal queue error; type type; error: error | Cause The SCP process encountered an internal queue error during command
processing. Effect The SCP process calls the ABEND or PROCESS_STOP_ procedure,
and stops. The backup process created the SCP process. It receives
system message -101, indicating process abnormal deletion. The backup
process resumes processing. If there is no backup process, the file system returns error
201 (nonexistent process) to every application that is awaiting a
response from the SCP process. The process that created the SCP process
receives system message -101, indicating process abnormal deletion. Recovery If there was no backup process, direct command messages to another
SCP process or hold them until another SCP process is started. If
the problem recurs, contact your service provider and provide all
relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
13 Request CANCELTIMEOUT failed; tag: tag | Cause An SCP call to the CANCELTIMEOUT procedure failed. CANCELTIMEOUT
cancels a timer (requested by SIGNALTIMEOUT) by using the tag that
resulted from the SIGNALTIMEOUT procedure. In this case, the CANCELTIMEOUT
tag is invalid and does not match any timer currently executing. The
tag can contain a positive value identifying a specific timer, or
-1 indicating all timers set by the calling process. Effect The SCP process calls the ABEND or PROCESS_STOP_ procedure,
and stops. The backup process created the SCP process. It receives
system message -101, indicating process abnormal deletion. The backup
process resumes processing. If there is no backup process, the file system returns error
201 (nonexistent process) to every application that is awaiting a
response from the SCP process. The process that created the SCP process
receives system message -101, indicating process abnormal deletion. Recovery If there was no backup process, direct command messages to another
SCP process or hold them until another SCP process is started. If
the problem recurs, contact your service provider and provide all
relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
14 Pool error; type: type; error: error | Cause The SCP process encountered an internal memory-pool error. The
memory pool, usually allocated in extended data segments, is not available
for processing. Effect The SCP process calls the ABEND or PROCESS_STOP_ procedure,
and stops. The backup process created the SCP process. It receives
system message -101, indicating process abnormal deletion. The backup
process resumes processing. If there is no backup process, the file system returns error
201 (nonexistent process) to every application that is awaiting a
response from the SCP process. The process that created the SCP process
receives system message -101, indicating process abnormal deletion. Recovery If there was no backup process, direct command messages to another
SCP process or hold them until another SCP process is started. If
the problem recurs, contact your service provider and provide all
relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
15 Internal error in buffer space calculation | Cause The SCP process miscalculated the amount of space required for
a response buffer, possibly due to an SCP program error. Effect The SCP process calls the ABEND or PROCESS_STOP_ procedure,
and stops. The backup process created the SCP process. It receives
system message -101, indicating process abnormal deletion. The backup
process resumes processing. If there is no backup process, the file system returns error
201 (nonexistent process) to every application that is awaiting a
response from the SCP process. The process that created the SCP process
receives system message -101, indicating process abnormal deletion. Recovery If there was no backup process, direct command messages to another
SCP process or hold them until another SCP process is started. If
the problem recurs, contact your service provider and provide all
relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
16 Internal buffer error | Cause The SCP process received a system message that it could not
process. The SCP process code does not include processing of a system
message with this message number. This message was not anticipated. Effect The SCP process calls the ABEND or PROCESS_STOP_ procedure,
and stops. The backup process created the SCP process. It receives
system message -101, indicating process abnormal deletion. The backup
process takes over, becomes the primary process, and resumes processing. If there is no backup process, the file system returns error
201 (nonexistent process) to every application that is awaiting a
response from the SCP process. The process that created the SCP process
receives system message -101, indicating process abnormal deletion. Recovery If there was no backup process, direct command messages to another
SCP process or hold them until another SCP process is started. If
the problem recurs, contact your service provider and provide all
relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
17 SIGNALTIMEOUT for deletedelay failed | Cause An SCP call to the SIGNALTIMEOUT procedure failed. SIGNALTIMEOUT
is called to set a timer associated with the DELETEDELAY startup parameter,
which specifies the time interval between when the last command message
for a communications subsystem is forwarded and when the SCP process
closes the communications subsystem. In some cases, the SCP process initiates a delay (timeout) before
stopping so any unexecuted command messages can finish. The SCP process
passes a time parameter to the SIGNALTIMEOUT procedure that indicates
the length the delay; the SIGNALTIMEOUT procedure then initiates the
delay. This error commonly results from an insufficient number of time-list
elements (TLEs). TLEs are a system resource configured during system
generation. A TLE is allocated for every timeout procedure. If all
TLEs are allocated, a procedure call requiring a TLE fails. Effect The SCP process stops the backup process, if there is one, and
calls the ABEND or PROCESS_STOP_ procedure. The file system returns
error 201 (nonexistent process) to every application that is awaiting
a response from the SCP process. The process that created the SCP
process receives system message -101, indicating process abnormal
deletion. Recovery If there was no backup process, direct command messages to another
SCP process or hold them until another SCP process is started. If
the problem recurs, contact your service provider and provide all
relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
18 No request matches cancel: tag: tag | Cause The SCP process received a CANCEL request that did not correspond
to any existing command message. Management applications call the
CANCEL procedure to cancel an outstanding command issued to the SCP
process. Effect The SCP process ignores the tag, issues this error message,
and continues processing. Recovery Your application should stop canceling outstanding command messages. |
19 REPLY error: error | Cause The SCP process uses the READUPDATE procedure to read incoming
command messages from its $RECEIVE file. If no response is required,
the SCP process completes the command message using the REPLY procedure.
If the REPLY procedure does not complete with condition code CCE (condition
code equal), the command-message originator is left with an uncompleted
command message. Effect The SCP process issues this event message and continues processing.
SCP uses the FILEINFO or FILE_GETINFO_ procedure to obtain the file-system
error related to the failure. Recovery If your application is accumulating uncompleted command messages,
it should look for this error message. Recovery depends on the file-system
error. If the event begins to repeat, notify the system manager. |
20 Application open table full | Cause The SCP process access control block (ACB, containing SCP process
openers) is full. Too many processes are trying to use the SCP process.
The ACB can contain a maximum of 1000 entries, so a single SCP process
can support no more than 1000 openers. Effect The SCP process issues this error and stops reading command
messages until space is reclaimed in the table (when an opener of
the SCP process closes it). Recovery Divide the processing load by starting and opening additional
SCP processes. If the error begins to repeat, notify the system manager. |
21 Request table full | Cause The SCP process command message control block (RCB) is full
(contains 255 command messages). The SCP process is receiving new
command messages more quickly than pending commands are being processed. Effect The SCP process issues this error 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 error begins to repeat, notify the system manager. |
22 Bad timeout tag: tag | 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 that matches the tag assigned
by the file system at the time of the SIGNALTIMEOUT call. This error
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
error message and continues processing. Recovery If the error begins to repeat, notify the system manager. |
23 Subserver open table full | 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 process
receives a request for a subsystem process that is not already open,
it creates a new entry in the table. If the table is full, the SCP
process searches the table for an entry it can delete. An SCP process
searches for an entry that has expired with respect to its DELETEDELAY
time; an SCP process searches for an entry for a subsystem process
for which there is no request pending. In either case, if the SCP
process cannot find an entry to delete, it issues this error. Effect The SCP process rejects the command that required the new subsystem
open and issues this error message. Recovery Divide the processing load by starting additional SCP processes.
If the error begins to repeat, notify the system manager. |
24 Memory pool full | Cause The memory pool used by the SCP process for processing incoming
command messages is full. The SCP process allocates (in extended data
segments) and manages pool space. When the pool space is full, the
SCP process stops accepting incoming command messages. Pool space
becomes available as command messages or traces are completed. The
SCP process is processing too many command messages or needs more
extended data segments for pool space. Effect The SCP process issues this message and rejects additional requests
until pool space becomes available. Recovery Divide the processing load by starting additional SCP processes.
Make more pool space available by restarting the SCP process and specifying
a larger value for the SEGPAGES or DATAPAGES startup parameter. |
25 SIGNALTIMEOUT for backup failed; no backup | Cause An SCP call to the SIGNALTIMEOUT procedure failed. SIGNALTIMEOUT
generates a timer for backup process creation. If the procedure fails,
the timer is not created, and the backup process is not created. The
procedure can fail due to a shortage of time-list elements (TLEs).
TLEs are system resources configured during system generation. The
system allocates one TLE for each call to a timeout procedure. If
all configured TLEs are allocated, a procedure call requiring a TLE
fails. Effect There is no backup process. If there is a process control block
(PCB) problem, a memory allocation problem, a swap file problem, or
a communication problem with a CPU-monitor process, the SCP process
keeps trying to create a backup process. If there is any other problem,
the SCP process gives up attempting to create a backup process. If
there is no backup process, the SCP process is not executing in fault-tolerant
mode. Recovery Do not let the SCP process try indefinitely to create a backup
process, but it should have a backup. If the problem recurs, contact
your service provider and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
26 No backup; fs: error; response | Cause An SCP process call to the NEWPROCESS procedure failed when
trying to start a backup process. Effect The SCP process issues this event and, depending on the error,
either continues to try creating a backup or gives up, as indicated
by the specified response. If the error is caused by a process control block (PCB) problem,
a memory allocation problem, a swap file problem, or a communication
problem with a processor-monitor process, the SCP process keeps trying
to create a backup process. If there is any other problem, the SCP
process gives up trying to create a backup process. If there is no
backup process, the SCP process is not executing in fault-tolerant
mode. Recovery If the SCP process gives up trying to create a backup process,
notify the system manager. The SCP process should have a backup process.
For NEWPROCESS error information, see the Guardian Procedure
Messages and Errors Manual. |
27 Checkpoint write failed; error error | Cause An SCP checkpoint write to the backup process failed. The CHECKPOINT
procedure might have failed because the primary SCP process could
not communicate with the backup process. Effect The SCP process issues this error message. If the backup process
exists, it is stopped and started again. If it does not exist, it
is started again. If the error is caused by a process control block (PCB) problem,
a memory allocation problem, a swap file problem, or a communication
problem with a processor-monitor process, the SCP process keeps trying
to create a backup process. If there is any other problem, the SCP
process gives up trying to create a backup process. If there is no
backup process, the SCP process is not executing in fault-tolerant
mode. The CHECKPOINT procedure returns a status code. If the procedure
failed because the primary SCP process could not communicate with
the backup, the status code contains a file-system error identifying
the cause of the failure. Recovery For information on the specified error, see Appendix B. If the problem
recurs, contact your service provider and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
28 OPEN to backup failed; error error | Cause The OPEN or FILE_OPEN_ procedure returned an error when SCP
attempted to open its backup process. Effect If the backup process exists, it is stopped and restarted. If
there is no backup process, one is started. Recovery The SCP process should have a backup process. If the problem
recurs, contact your service provider and provide all relevant information: Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as Event Management
Service (EMS) logs, trace files, the saveabend file, and a processor
dump, if applicable
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
29 SCPTRACE error (error); trace suspended | Cause The SCP process issues this noncritical event message when there
is a problem with tracing (initiated with a TRACE command). The error
code indicates the cause. Effect The SCP process issues this error message, turns tracing off,
and continues processing. Recovery Determine a recovery action based on the Subsystem Programmatic
Interface (SPI) error code. |
30 CPU changed from (cpu1) to (cpu2) because reason | Cause The SCP process issues this noncritical event message when its
backup process takes over from the primary process. Effect The new primary SCP process starts a backup process and continues
message processing. Recovery Informational message only; no corrective action is needed. |
31 Process terminated because cause‑text | Cause The primary SCP process stopped in a sufficiently orderly manner
to issue this error before stopping. The cause text indicates the
cause. Effect The SCP process no longer exists. Recovery Restart an SCP process. |
32 Backup process terminated | Cause A backup SCP process stopped in response to a STOP, PROCESS_STOP_,
or ABEND procedure call. Effect The backup process no longer exists. Recovery Informational message only; no corrective action is needed. |
33 State changed from old-state to new-state | Cause The summary state of the SCP process changed. When an SCP process starts executing a STOP, ORDERLY command,
its summary state changes from STARTED to STOPPING. The process continues
to report the STOPPING summary state while it is kept open by another
process. When an SCP process receives a START command while still in
the STOPPING summary state, its summary state changes to STARTED.
In effect, a STOP, ORDERLY command that is in progress is canceled
by a START command. Effect The SCP process functions in a manner appropriate for the new
summary state. Recovery Informational message only; no corrective action is needed. |
34 Could not handle reply: error. | Cause The SCP process received a reply for a requester that no longer
exists, has a new identity, or has canceled its original request.
If the error value is CANCELED, the requester canceled the request
to which this is the response. If the error value is UNKNOWN, the
SCP process might have closed and reopened the subsystem in its attempts
to work around a shortage of space in the server control block (SCB)
table. Effect The response is discarded and processing continues. Recovery If the command was canceled, check the status of objects that
might have been affected by the corresponding command to determine
if any processing was completed before the cancellation finished.
If the cause is unknown, the SCP process might be overloaded. Try
starting another SCP process to share the processing load. |
35 Security Violation: PAID: access-id, Cmd: command, For: proc | Cause An unauthorized requester issued a sensitive command. SCP processes
accept sensitive commands from requesters that belong to the super-user
ID, requesters with the same group as the creator access ID of the
SCP process handling the request, or requesters that belong to groups
specified by SCP in its GETVERSION response. Effect The command is rejected. Recovery Reissue the request from an authorized requester. |
36 Device name (DCT
Entry index) not responding to DEVICEINFO. | Cause The object failed to respond within 10 minutes of SCP’s
DEVICEINFO call. Effect The object is ignored—SCP continues processing with the
next object specified in the command. Recovery Informational message only; no corrective action is needed.
You might want to use alternate methods to determine the status of
the object. |
37 Device mgr-process error: detail | Cause The SCP process encountered an error on its initial GETVERSION
request to the subsystem manager process. The errors can result from
requester-SCP-server software version incompatibilities or from an
incorrect subsystem manager name in the request. Effect The subsystem is unavailable, and the SCP process rejects the
original request that prompted its attempt to open the subsystem.
The corresponding ZCOM error is generated with this message. For more
details on these errors, see the Subsystem Control Point
(SCP) Management Programming Manual. Recovery Check the software versions for incompatibilities and make sure
that the request contains the correct name of the subsystem manager
process. |
38 Bad PUTMEMORY call: error | Cause Not enough buffer space is available, so the SCP process cannot
allocate memory for processing a request. Effect SCP generates this event then abends. The message, with header PUTMEMORY problem, is generated in the event log. Recovery Restart the SCP process. |
39 Device name had File
Sys Err with SCP. FS error: 31 | Cause SCP cannot open a request for a subsystem due to insufficient
space in the Program File Segment (PFS). Effect SCP displays the error message and abends the SCF command that
is expected to finish. Recovery Start a new SCP process other than the current one and send
the request to the new SCP process. |
|