CRE Programmer's Guide

CRE Services
Common Run-Time Environment (CRE) Programmer’s Guide—528146-004
2-14
Initialization Errors
Initialization Errors
Several kinds of errors can occur during CRE initialization. If an error occurs before the
CRE has set up its environment, the CRE invokes PROCESS_STOP_ and specifies
option ABEND with the appropriate error text, as listed in Table 2-4 on page 2-14.
If a process receives an open message before process initialization is complete, the
CRE returns file-system error 100 (FENOTREADY). In this rare situation, the
application returning error 100 must retry the open until the process has received the
close message from its creator process.
Table 2-4. CRE Initialization Errors
Error Text Cause of Error
Backup heap allocation failed Invalid heap or heap control block.
EXECUTION-LOG has invalid
filename (filename)
Text for PARAM EXECUTION-LOG does not specify a
valid external file name.
Invalid environment The CRE cannot locate the Master Control Block
(MCB), or the version level of the MCB is newer than
the release level of the CRE.
Invalid environment - Unable to
obtain minimum process heap
space
CRE could not obtain adequate process heap space.
Invalid startup message volume
value (text)
Invalid volume/subvolume field value; message text
appears when the field value is printable.
Log filename unknown CRE cannot determine the name of the standard log
file.
Missing startup message (nnnnn) $RECEIVE read failed, or the wrong message was
sent. File-system error nnnnn appears when
available.
Not closed by ancestor (nnnnn) $RECEIVE read failed. File-system error nnnnn
appears when relevant.
Not opened by ancestor (nnnnn) FILE_OPEN_ failed. File-system error nnnnn appears
when relevant.
Premature takeover Backup process took over before process memory
was fully initialized.
Signal during initialization Signal or trap occurred before standard log file
initialization was complete.
STDERR assigned invalid filename
(text)
Text in Assign message for STDERR does not specify
a valid external file name. Message text appears
when available; otherwise, file-system error nnnnn
appears if relevant.
Unable to initialize signal handling Native CRE could not initialize default signal handler.
Unable to open $RECEIVE (nnnnn) FILE_OPEN_ failed. File-system error nnnnn appears
when relevant.