SPI Common Extensions Manual

ZCMK Definitions
SPI Common Extensions Manual—427508-001
B-8
Errors During Startup
The use of a disk file as the logging file is probably the most common choice.
Specifying a disk file as the log file assumes that the file already exists. The types of
operations performed on such files preclude the use of an edit file. Typically, an entry-
sequenced file with a record size of at least 132 bytes is adequate for log output. You
can create such a file with the File Utility Program (FUP):
FUP CREATE filename,TYPE E,REC 132, EXT (pri,sec)
If you inhibit logging (by omitting the LOG parameter or its filename argument),
emergency output—output that precedes the abnormal termination of the process—is
directed to the home terminal.
If the specified logging file cannot be accessed, the process does not start.
Errors During Startup
Error conditions detected during startup might prevent successful startup of a
ZCMK-based process.
Fatal Errors
A ZCMK-based process stops if it detects any of:
•
A lapse of more than 30 seconds in the startup messages protocol
•
A startup parameter in the startup line containing a syntax error or a value out of
range (including such errors as specification of a nonexistent backup CPU)
•
A nonexistent file specified for logging or EMS output
•
An unrecognized startup parameter in the startup line
•
Insufficient memory to start the process
•
The requested character map (specified in the CHARMAPNAME parameter) or
character-map file (specified in the CHARMAPFILE parameter) could not be found
(applies only to subsystems that support character mapping)
Warnings
These conditions are treated as warnings during process startup (startup proceeds, but
some capabilities might be partially or totally disabled):
•
An unrecognized startup parameter is detected in a PARAM statement. The
parameter is ignored without comment.
•
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). Most syntax errors are ignored without comment.
•
The volume specified in the SWAPVOL parameter is not a local disk drive. A
substitute volume is assigned, and its identity is revealed in a warning message.