If an unrecoverable machine check occurs in the control program, the message DMKMCH610W MACHINE CHECK SUPERVISOR DAMAGE --or-- DMKMCT610i MACHINE CHECK SUPERVISOR DAMAGE appears on the processor console. The control program is terminated and
enters a wait state 001 or wait state 013. If the machine check handler cannot diagnose a certain machine check,
the integrity of the system is The message DMKMCH611i MACHINE CHECK SYSTEM INTEGRITY LeST --or-- DMKMCT611i MACHINE CHECK SYSTEM INTEGRITY LOST appears on the processor console. The control program is terminated and
enters wait state 001 or wait state 013. Hardware errors are probably the cause of these severe machine checks. The system operator should run the CPEREP program and save the
output for the installation hardware maintenance personnel.
If the generated system cannot run on the real machine because of
insufficient storage, CP enters the disabled wait state with code OOD in
the PSi. The insufficient storage condition occurs if: • The generated system is larger than the real machine size
--or-- • A hardware malfunction occurs which reduces the available amount of
real storage to less than that required by the generated system The message DMKCPI955i INSUFFICIENT STORAGE FOR VM/370 appears on the processor console.
If CP cannot continue because consecutive hardware errors are
occurring on one or more V8/310 paging devices, the message D8KPAG415E CONTINUOUS PAGING ERRORS FROM DASD xxx appears on the processor console and CP enters the disabled wait state
with code OOF in the PSi. If more than one paging device is available, disable the device cn
which the hardware errors are occurring and IPt the system again. If
the VM/370 system is encountering hardware errors on its only paging
device, move the paging volume to another physical device and IPL again.
Bote: This error condition may occur if the VM/370 paging volume was not properly formatted. 28 IB!

The following procedure should be followed by the processor operator
to record the needed information.
1. Using the alter/display mode of the processcr console, display the
real PSW and CSW. Also, display the general registers and the
control registers.
2. Press the SYSTEM RESTART button in order to get a system abend dump.
3. IPL the system.
Examine this information and attempt to find what caused the wait. If you cannot find the cause, attempt to reconstruct the situation that
existed just before the wait state was entered.
If you determine that CP is in an enabled wait state, but that no IIO interrupts are occurring, there may be an error in the CP routine or CP aay be failing to get an interrupt from a hardware device. Press the SYSTEM RESTART button on the operator's console to cause an abend dump
to he taken. Use the ahend dump to determine the cause of the enabled
(and noninterrupted) wait state. After the dump is taken, IPL the
system. Using the dump, examine the VMBLOK for each user and the real device,
channel, and control unit blocks.. If each user is waiting because of a
request for storage and no more storage is available, there is an error
in CP. There may be looping in a routine that requests storage. Refer to
-Reading CP Abend Dumps" for specific information on how to analyze a CP du.p.
The VM/370 Control Program does not allow the virtual machine to enter a
disabled wait state or certain interrupt loops& Instead, CP notifies
the virtual machine operator of the condition with one of the following
aessages: DMKDSP450W CP ENTERED; DISABLED WAIT PSW DMKDSP451W CP ENTERED; INVALID PSi DMKDSP452W CP ENTERED; EXTERNAL INTERRUPT LOOP DMKPRG453W CP ENTERED; PROGRAM INTERRUPT LOOP and enters the console function .ode. Use the CP commands to display the
following information on the terminal. • PSW • CSW • General registers • Control registers
Then use the CP DUMP command to take a dump. Part 1. Debugging with V8/370 29