Page of GC20-1806-9 As Updated April 1, 1981 by TNL GN25-0834 SPECIAL CONSIDERATIONS FOR THE EP 370X CONTROL PROGRAM If a 370x Emulation Program (EP) is automatically reloaded after a 310x failure, the system may loop after the restart. The message
DMKRNH4631 CTLR xxx UNIT CHECK; RESTART IN PROGRESS and two responses
CTLR xxx DUMP COMPLETE CTLR xxx ncpname LOAD COMPLETE indicate that the 370x has been reloaded. If the system loops after the
second response, must reset all emulator lines from the 310x control
panel.
If the automatic dump feature is not enabled, one of the messages
DMKRNH462I CTLR UNIT OHECK; IPL REQUIRED DMKRNH464I CTLR 'raddr' CC=3; DEPRESS 310X "LOAD" BUTTON indicates a 310x abnormal termination. You must reload the 310x Emulation Program with the NETWORK LOAD command. If the system loops
when an attempt is made to enable the lines, you must reset all emulator
lines from the 370x control panel.
The IBM 37Q4 Control Panel Guide and the IBM 3705 Contral Panel Guide resetting 370x control panel in its "Generating Channel End/Device End with Emulator
program" section.
A 370x communications centroller cannot be used by VM/370, as a 370x, unless it has been loaded by VM/370. Use of the ATTACH and DETACH
commands reset the "loaded" status and, therefore, the 370x will need to
be reloaded.
section 2. Initiating VM/370 operation 23

April 1, 1981
Messages on Startup and Initialization In the course of VM/370 initialization or startup, in addition to the
normal expected messages that are a part of loading the system, you may
see other messages to which you must respond. These messages relate to
functions of initializat-lon: checkpoint .• warm start, and automatic
checkpoint requirements. These messages and the recommended course of
action are described in the VM/370 System Messages. Console Messages After Startup System console messages are in three categories: • System operation status messages • Virtual machine user messages • Hardware and program status messages
The operator action required depends on the type and content of the
message. SYSTEM OPERATION STATUS MESSAGES These messages inform the system operator of the logging on and logging
off of users, number of spooled files, output printer or punch
accounting data, device attention conditions, and command completion
indications. Some of these messages require operator action, while
others do not. MESSAGES FROM VIRTUAL MACHINE USERS These messages include requests and inquiries from virtual machine users
on the system; a sampling of these user messages follows: MSG FROM JONES: CAN YOU GIVE ME A TAPE MSG FROM SMITH: CAN YOU PUT UP A SCRATCH 181 MSG FROM SMITH: PLEASE TAKE RING OUT OF 181 NOW MSG FROM BROWN: PLS ATTACH 382 HARDWARE AND PROGRAM STATUS MESSAGES These messages include VM/370 error recording messages, VM/370 system
error information, and I/O error messages related to users of virtual
machines who have invoked SVC 76. SVC 76 causes VK/370 to send a
message to the system operator (for I/O error records only) and to
record the error data in VK/370 "s error recording area. The V!/310 manual describes these messages.
For more information about error detection and the recording and
editing of errors, refer to the !M/370 OL!SEP and Error The following the action that the operator must take in
response to an error message:
1. Determine the severity of the error.
24 VM/370 Operator's Guide