Subsystem Control Point (SCP) Management Programming Manual

Errors
Subsystem Control Point (SCP) Management Programming Manual—520619-001
A-3
Additional Startup Errors
The SCP program PROGID must be set to the super ID.
When the SCP process attempted to open its $RECEIVE file, the OPEN procedure
returned a file-system error and did not finish successfully.
Additional Startup Errors
An SCP process stops if it encounters any of these conditions during process initiation:
•
A startup parameter specified on the startup line contains a syntax error or a value
out of range (including such errors as specification of a nonexistent backup CPU).
•
A nonexistent file is specified for logging or EMS output.
•
An unrecognized startup parameter is detected on the startup line.
•
Not enough memory is available to start the process.
•
An unrecognized startup parameter is detected in a PARAM statement.
•
A startup parameter specified in a PARAM statement contains a syntax error or a
value out of range (including such errors as specification of a nonexistent backup
CPU).
•
The volume specified in the SWAPVOL parameter is not a local disk drive.
SPI Error Descriptions
These subsections contain descriptions of the ZSCP and ZTRC errors issued by SCP
processes. Each error description includes:
•
Error number and name
•
A list of tokens contained in the error list, followed by a description of any token not
described elsewhere
•
Any text message associated with the error
•
Possible causes of the error condition
•
Effects or repercussions of the error condition
•
Recommended recovery actions
Must be run as super ID
$RECEIVE open error: file-system-error