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

Installation Verification Procedure
To execute the IVP with virtual machines other than IVP1 and IVP2: • Enter, in place of the command IVP 1: IVP 1 userid1 • Enter, in place of the command IVP 2: IVP 2 userid2
where useridl and userid2 identify the two virtual machines in which the
EXEC procedures IVP 1 and IVP 2 (respectively) are to be executed.
To execute the IVP in a single virtual machine, enter the command
(from any logged-on virtual machine): IVP *
This causes the IVP tests to be run in that single virtual machine.
Intermachine transfer of data is simulated by transferring virtual
punched output to the same virtual machine's virtual card reader.
Interpreting the Test Results Messages at the end of the IVP test indicate successful completion. If
any errors are detected by the IVP, call IBM for software support,
because an error usually indicates a serious malfunction of the
generated system. The IVP procedure identifies each command being tested
just before the command is executed.
Error messages are displayed in a four-line format, for example:
*** IVP FAILURE HAS OCCURRED ***
*** COMMAND: STATE IVPTST *
*** EXPECTED RETURN CODE 28
*** RECEIVED RETURN CODE 0 These messages indicate that the CMS STATE command had a return code of 0, instead of the expected 28.
All information messages that originate within the IVP are preceded
by three asterisks (***).
If any command fails, the IVP procedure terminates. Follow the
instructions (if any are given) to log off the virtual machine. Once the IVP procedure has executed successfully, continue the system
generation process by loading and saving discontiguous saved segments,
as described in the section that follows.
266 IBM VM/370 Planning and System Generation Guide