Installation Verification Procedure
Starting the IVP The IVP must be executed to formally complete the initial installation.
(See "Variations of the IVP" for post installa tion testing.) It
requires two virtual machines (IVPM1, IVPM2) which must be described in
the VM/370 directory.
The directory entries for the IVP virtual machines, IVP1 and IVP2, are included in the VM/370 directory supplied with the starter system;
these entries should be included in your own directory. The spooling
classes for the reader and the punch must be the same.
You, as the system operator, execute the IVP. To initiate the IVP tests, enter the command:
ivp
and then answer "yes" or "no" to the following question:
ARE YOU THE SYSTEM OPERATOR? ENTER "YES" OR "NO": If you enter the IVP command with no parameters specified and then
reply that you are not the system operator, the IVP tests default to the
single virtual machine verification procedure. (See "Variations of the IVP. ") Prompting instructions are displayed whenever you must perform an
operation or issue a command.
Log on the virtual machine (IVPM1), using the password IVPASS, and IPL eMS to continue the testing procedure:
logon ivpml
ENTER PASSWORD: ivpass LOGON AT 09:55:00 EST FRIDAY mm/dd/yy
define storage 16384k STORAGE= 16384K
If you created a eMSSEG discontiguous saved segment in step 24 of the
system generation procedure, IPL eMS by issuing:
ipl 190 If you did not create a eMSSEG segment in step 24, IPL eMS by issuing:
ipl 190 parm seg=null
In either case, the system will respond: eMS VERSION n.n mm/dd/yy hh.mm
Then you begin the IVP procedure by issuing:
ivp
264 IBM VM/370 Planning and System Generation Guide

Installation Verification Procedure
At this point, the tests begin on virtual machine 1. After the
disconnect message is displayed, follow the prompting messages that are
displayed. These messages tell you to log on the IVPM2 virtual machine
(this may be done on the same terminal), as shown:
logon ivpm2
ENTER PASSWORD: ivpass LOGON AT 09:58:30 EST FRIDAY mm/dd/yy
If you created a CMSSEGdiscontiguous saved segment in Step 24 of the
system generation procedure, IPL CMS by issuing:
ipl 190 If you did not create a CMSSEG segment in Step 24, IPL CMS by issuing:
ipl 190 parm seg=null
In either case the system will respond: CMS VERSION n.n mm/dd/yy hh.mm
Then you begin the IVP procedure by issuing: ivp 2
At this point, the remainder of the tests begin on virtual machine 2.
The final phase of the IVP tests consists of displaying, printing, and
punching a file which contains the messages generated by IVPK1 after it
is disconnected. Upon completion of the tests, the IVP EXEC procedure logs off. The
system abnormal termination test, which consists of forcing an ABEND
dump of VK/370 and the subsequent warm start, is an option that you must
specify in response to messages that are displayed. For the purpose of
installation verification, you should select this option. You are
instructed to delay starting the spooling devices (reader, printer, and
punch) until after the warm start procedure.
Variations of the IVP If you wish, you may run the IVP procedure after initial installation,
using anyone of the following methods: • Executing the IVP without testing the system abnormal termination • Executing the IVP using virtual machines other than IVPK1 and IVPK2 • Executing the IVP in a single virtual machine When you execute the IVP in a single virtual machine, intermachine
functions, such as transferring data between virtual machines, are not
exercised.
To execute the IVP without testing system abnormal termination: • Retain the created virtual machines in your VM/370 directory. • Execute the IVP as described previously under "Starting the IVP," but
do not select the "system abnormal termination" option. Part 3. Generating VM/370 (CP, CMS, RSCS, and IPCS) 265