Installation Verification Procedure Verifying CP and CMS Using the IVP The Installation Verification Procedure (IVP) for VM/370 exercises CP and CMS to verify that they are working properly. The IVP is contained
in two files using the EXEC facility of CMS, and uses two virtual
machines in addition to the system operator's virtual machine.
The tests exercise the following areas of CP: Multiple virtual machine support I/O spooling
Transferring of spooled data to other virtual machines Offline I/O operations
Sending of messages to the system operator Paging operations
Task dispatching and scheduling
Disk I/O support
Automatic warm start following abnormal termination of VM/370 Verifying that the correct EC level is on machines with
Extended Control-program Support
The following facilities of CMS are exercised:
Normal CMS command processing
Disk formatting
Copying of files
Creation and modification of files via EDIT command
Assembly of executable programs
Execution of user programs
Creation and execution of user-written commands Printing and punching of CMS files
Issuing of commands to CP Use of multilevel nested EXEC procedures
Stacking and unstacking of command and data input from the terminal
Communication with user from EXEC procedures Several other system facilities, incidental to the primary rvp tests, are exercised. Certain system facilities such as preferred execution
options, virtual=real, as ISAM, and RSCS (Remote Spooling Communications
Subsystem) are not exercised by the IVP. The IVP requires operator
intervention only when an operational decision is to be made, or to
initiate the IVP tests themselves. All file creation, erasure,
management, and logoff of the virtual machines (with the exception of
the system operator) at test completion is performed without operator or
user action.
The IVP tests use only the system-provided facilities. All unique
test programs are created, assembled, and subsequently erased by the lVP. Facilities Required for Each IVP Virtual Machine
All VM/370 configurations are supported. The lVP executes under the
control of CMS. The other facilities required are: • The assembler • One virtual read/write disk accessed as the A-disk (usually 191) • 320K of virtual storage (16M for IVPM1) Part 3. Generating VM/370 (CP, CMS, RSCS, and lPCS) 263

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