• Have VM/310 system operator (or any class B user) exclusively attach
the entire system residence volume to the OSVS userid by issuing this
command:
attach 152 to osvs as 250 In this command, 152 is the real device address on which the system
residence volume is mounted.
Using Virtual Devices
When using OS/VS in a virtual machine, the user is the OS/VS operator.
This user must have the following devices, which are normally defined in
the VM/370 directory entry: • A virtual card reader, from which OS/VS reads the as/vs input job
stream. • A virtual printer, which handles the printed output generated by OS/VS. • The virtual punch, which receives punched output generated during
a S/VS opera tion.
In addition tc these unit record devices, the as/vs operator can attach
virtual tape and direct access storage devices to the virtual machine
(by using either the ATTACH or DEFINE commands) • The user can also
specify these devices in the VM/310 directory entry. Depending upon hoy OS/VS Yas generated. a user May need to change a
virtual device address. For example: If OS/VS expects a 3211 printer
at device address 002 and the directory entry does not contain this
assignment, define one with the CP DEFINE command:
define 3211 002 Before using OS/vs, find out from the as/vs system programmer what
are the installation's virtual device requirements.
DEFINING THE OPERATOR'S CONSOLE The operator's console must be at the address specified during as/vs
system generation. The easiest way to ensure this is to define the
appropriate ccnsole address in the directory entry. For example: The CONSOLE directory control statement could appear as follows: CONSOLE 01F 3210 This statement defines a virtual 3210 console at virtual address 01F. Section 4. as/'s in a Virtual Machine 121

USING THE VM/370 SPOOL FILE A user should let the VM/370 spool file system handle printer or punch
output that does not have to be printed or punched. For example: When using the alternating route print output to the virtual card
reader by using this CP SPOOL command: tcp spool printer to *
After issuing this command, a user can subsequently load the systea and create a CMS file from the data in the virtual reader (by using the CMS READCARD command). Then, by using the CMS editor, the user can scan
the contents of this data at his terminal.
Preparing Jobs for an OS/VS Virtual Machine Prepare and submit a job stream to an OS/VS virtual machine in one of
two ways: • Place a deck of real punched cards that contain the appropriate job
control, Frogram and data in the real card reader. Place a CP ID
statement at the beginning of this job stream deck to indicate the OS/VS userid; for example:
ID OSVS or -- USERID OSVS Either statement is a valid ID statement for directing the input that
follows to the OSVS user's virtual reader (the reader with the
lowest virtual device address). • Use the CMS system to create a CMS file containing images of what
would normally be submitted through a card reader on a real System/310. Enter the CP SPOOL command to cause subsequent punched
output to be directed to the virtual card reader of the OS/VS machine. Enter the CMS PUNCH command to generate the virtual card
deck:
cp spool punch to osvs
punch vsjob27 jcl (noheader
The NOHEADER option of the PUNCH command suppresses punching a READ control card at the beginning of the deck.
A job stream spooled to OS/VS by either of these methods remains in the
card reader of the OS/VS virtual machine until the user starts an as/vs
reader,. When spooling jobs to a virtual machine, clear
remain in the virtual punch from previous jobs by commands: any data that may
issuing these CP cp spool punch nocont
cp close punch purge
These commands ensure that the virtual punch is purged
reader files. The first command is required if the
originally spooled with the CONT operand.
128 IBM operating Systems in a Virtual Machine
of any existing
punch had been