Explanation
z/OS UNIX initialization
processing seems to be taking an excessive amount of time to complete.
The message identifies the last initialization step to have been successfully
started and therefore, the one most likely responsible for any delays
or hangs.
In the message text:
- procname
- The name of the z/OS UNIX cataloged
procedure.
- text
- One of the following:
- INITIALIZING THE FILE SYSTEM
- Indicates that z/OS UNIX initialization
has started the initialization of the file system, but the file system
initialization has not yet completed.
- CREATING THE BPXOINIT ADDRESS SPACE
- Indicates that z/OS UNIX initialization
has issued a system request to create the BPXOINIT address space,
but the address space has not yet started.
- PROCESSING IN BPXOINIT
- Indicates that BPXOINIT has started processing but BPXOINIT has
not yet started the initialization process (either the initialization REXX EXEC, /etc/init,
or /usr/sbin/init).
- STARTING THE INITIALIZATION PROCESS
- Indicates that BPXOINIT is attempting to fork an address space
in which to run the initialization process (either the initialization REXX EXEC, /etc/init,
or /usr/sbin/init) but the fork has not yet completed.
- RUNNING THE INITIALIZATION PROCESS
- Indicates that BPXOINIT has started the initialization process
(either the initialization REXX EXEC, /etc/init, or /usr/sbin/init) but
the initialization process has not yet completed.
Some commands
can cause hangs in the /etc/rc process, invoked from /etc/init, thus
resulting in the issuance of this message. If the set —v —xcommand
has been added to /etc/rc (it is shipped in the sample /etc/rc), the
system programmer may view /etc/log during a hang in /etc/rc by starting
the shell from a superuser and issuing the command cat /etc/log.
Note that it must be a superuser; a user having permission to BPX.SUPERUSER
is not enough. The last command listed in /etc/log is most likely
the one causing the hang or delay.
- WAITING FOR SECURITY PRODUCT INITIALIZATION
- Indicates that z/OS UNIX initialization
is waiting for the security product to complete initialization.
- WAITING FOR CATALOG ADDRESS SPACE INITIALIZATION
- Indicates that z/OS UNIX initialization
is waiting for the catalog address space to complete initialization.
- WAITING FOR JOB ENTRY SUBSYSTEM INITIALIZATION
- Indicates that z/OS UNIX initialization
is waiting for the job entry subsystem (JES) to complete initialization.
- OMVS IS UNABLE TO CREATE THE BPXOINIT ADDRESS SPACE
- The address space create of the BPXOINIT address space failed
because there were not enough system resources to complete the process.
The OMVS address space initialization could not complete.
System action
The initialization process is allowed
to continue, unless the message indicates that the BPXOINIT address
space could not be initialized. In this case, initialization processing
is discontinued.
Operator response
If the condition persists, contact the system
programmer.
System programmer response
If the message indicates
that the BPXOINIT address space cannot be created, shutdown OMVS and
attempt to correct the system resource problem that could be causing
the failure. Restart OMVS after correcting the problem. Otherwise,
search problem reporting databases for a fix for the problem. If no
fix exists, contact the IBM® Support
Center.
Module
Source
z/OS UNIX System Services kernel (BPX)
z/OS MVS System Messages, Vol 3 (ASB-BPX)
Copyright IBM Corporation 1990, 2014