Signalling attention takes the user to the virtual CP level, where he
issues a SET DUMP command. Ordinarily, when testing an unstable
system, this would have been one of the first commands entered after
issuing the IPL for the virtual CP system. The query of the dump unit
verifies that the dump is of the CP nucleus to the spooling disk at
address 330. r---------------------------------------.----------- ! ! CP system restart
RRRR •••• RING •••• GGGG 19:20:06 DMKDMP9081 SYSTEM FAILURE, CODE PSA002 RRRR •••• RING •••• GGGG
RRRR •••• RING •••• GGGG DMKCKP9601 SYSTEM WARM START DATA SAVED DMKDSP450w CP ENTERED; DISABLED WAIT PSW CP DMKCKP961W SYSTEM SHUTDOWN COMPLETE CP ••• RING •••• GGGG CP -, I I I Signalling attention takes the user to the real CP level, where he
enters the ccmmand SYSTEM RESTART. This command is the equivalent of a
system restart function on a real processor. The system restart
function for a CP system automatically dumps the system and then issues IPL again. After the system is dumped, a message appears with abnormal
termination code PSA002 (a system dump due to pressing the system
restart key).
The virtual bell rings to indicate that the system has been reloaded, and the system prints messages about: saving warm start data, CP entering a disabled wait state, and system shutdown being complete. The
message indicating that CP has entered a disabled wait is
Fremature1y issued between these two messages. It occurs because of a
synchronizaticn of the real CP system with the virtual CP system console
output.
After these messages are issued, the user is in real CP mode. He can
either log cff or obtain the system abend dump.
To obtain this dump, re-IPL 330 and repeat the test procedure up to
the Foint where the 'print profile exec' is shown in the same session.
At this peint, the user now has eMS initialized in the virtual CP system and has read/write access to his real eMS minidisk at virtual address
191. By issuing a QUERY RDR ALL command, VM/370 should reveal that a
class D dumF file is in the operator's virtual reader (because the
operator's userid is specified in the SYSDUMP operand of the SYSOPB system generation macro instruction) • Section 2. VM/370 in a Virtual Machine 67

..-- !
19:22:10
19:22:10 CMS vmfdump
R;
spool rdr cl d
b
The SPOOL RDR CL D command allows the virtual reader to access the
class D dump file. By entering the B (BEGIN) command, the virtual machine user returns to CMS. By entering the veFDUMP command (class C or E), IPCS reads the CP abend dump and creates a CMS dump file, problem report, and symptom summary entry on the 191 A-disk. (For a sample VMFDUMP session, refer to When VMFDUMP processing completes under CMS in the virtual CP system,
terminate the test system by entering real CP mode and initializing CMS. Under CMS, the user can issue the IPCS DUMPSCAN command to look at the
dump taken cf his virtual test system. This dump resides as a dump file
on the user's real 191 A-crisk. Summary
Tc update and test a VM/370 system in a virtual machine, an installation must first have a VM/370 directory entry for a VM/370 virtual machine.
This virtual directory entry need only specify the minimum number of
users sufficient to perform the test. Before initializing this system,
an installaticn should verify that the virtual machine configuration
has: the ccrrect console address, sufficient unit record devices
available a t the correct addresses, and enough disks (either linked or
attached) tc make a reasonable test. Also, the VM/370 virtual machine
can run CMS when it has access to the CMS system residence volume. With few exceFtions, IPL for a VM/370 virtual machine is similar to IPL for a real VM/370 system. Operationally, Ve/370 provides CF ccmmands to disFlay and store into real storage. The VM/370 system in a
virtual machine can also display and store into its own third level
virtual storage. If the virtual machine performs any spooling
oFerations, the virtual VM/310 system is also spooling unless it has
dedicated unit record devices. This double spooling is no problem;
hcwever, there are some special operational considerations.
68 IBM Sjstems kn a Virtual Machine