ISSUING SPOOL COMMANDS TO CONTROL UNIT RECORD DEVICES Spool the virtual punch to the virtual .achine:
cp spool punch to *
This command causes subsequent punched output to appear in the user's
own virtual card reader. To submit a job to the OS/VS .achine, punch
the JCL and associated card data. Spool the virtual printer to the virtual card reader:
cp spool printer to *
Instead of routing printed output to the real printer, this co •• and
causes it to appear in the virtual card reader. By using the CBS machine, each print file can then be read, eXamined, and either purged
or printed at the real printer. !Qte: Since a user may find both punch and printer files in the virtual
reader, ccnsider using the spool file class attribute to control which
files are to be processed at anyone time. PUNCHING CMS FILES Use the CMS PUNCH command to transfer the job stream to the virtual card
reader of the OS/VS virtual machine:
punch pli21 job (noheader
By specifying NOHEADER option of the PUNCH command, V8/370 does not punch a CMS READ control card at the beginning of the output deck.
INIZIALIZING OS/VS Lead OS/VS into the virtual machine by issuing this command: cp ipl 250 When an OS/VS reader is started, it reads the job stream that had been previously punched with the punch spooled to the user's own userid.
For example, the OS/VS command: s rdr,OOc starts a reader on virtual device OOC and reads those cards that appear
in the OS/VS reader queue. RELOADING CMS INTO A VIRTUAL MACHINE When the job stream has been processed, reload CftS and use the BE1DC1BD com.and to create a CMS file from the printed output and put it onto a CMS disk. The output can now be examined with the CMS editor or TYPE command. When hardcopy output is needed, the file can be printed via
the CMS PRINT command. When using the REIDCARD co.mand to create a CBS file, do not use a filetype of LISTING. Otherwise, VB/370 assumes the
first character of each line to be a control character, which is not
printed.
134 IBM VM/370 operating Systems in a Virtual Machine

EXAMINING OS/iS VIRTUAL MACHINE OUTPUT To examine a job's output executed under the OS/VS virtual machine, sFeol the unit record output to the user's own Now read the
file in the virtual card reader onto a eMS disk by using eMS BEADCABt command:
readcard pli27 job
The CMS TYPE command or editor can then be used to scan such a file.
If programming errors occurred during the execution of the job
stream, the eMS editor can be used to make corrections to the source
program, ccrrect job control statements, or resolve any other executicn
problems. After aaking these corrections, resubmit the job stream.
Using More than One Virtual Machine A user can run multiple systems, each in its own virtual machine and
each contrclled from its own terminal. However, if multiple terminals
are not available, a user can use one terminal to control all systems
but only one at anyone time.
This aFFroach combines the alternating system and batch techniques. Separate userids are used to run OS/VS in one virtual machine and to
prepare jobs and examine OS/VS output in a CMS virtual machine.
After submitting a job stream under the eMS userid: issue the DISCCNN or LOGOFF command (depending upon how soon the user intends to log onto
the CMS ID again). The terminal is now free to be used for running the OS/VS job stream under the OSVS userid:
logon cmsid
(route jobs to OSVS user)
disconn
logon osvs
(run jobs) Section 4. OS/VS in a Virtual Machine 135