(for running test jobs only) USER MVSID PASSWORD 3M 16M BCG ACCOUNT ACCTNO BIB8 IPL CMS OPTION REALTIMER ECMODE BM CONSOLE 01F 1052 SPOOL 01C 2540 READ A SPOOL 01D 2540 PUNC A SPOOL 007 3211 A SPOOL 008 3211 A SPOOL 017 3211 A SPOOL 018 3211 A SPOOL OlE 1403 A SPECIAL 2FF 3270 SPECIAL OFF TIMER (This entry then uses the MVS machine's PROFILE EXEC to attach
the appropriate volumes and IPL lIVS.) Accessing OS/VS This topic assumes that OS/VS for use under V8/370 has already been
generated and that the system residence volume is available on a real
disk or minidisk in read/write status.
As the OS/VS operator, the OS/VS user needs to know the location of
the system residence volume. Its location can be defined in the virtual
machine configuration in one of three ways: • Define the system residence volume as a read/write disk in the
directory entry for the OSVS userid. Such a definition may appear as
follows: MDISK 250 3330 0 403 VS2RES WR YOUR BAllE Many installations prefer this approach for maintaining a directory
definiticn of the system residence volume. • Use the CP LINK command to define the system ressidence volume after
lcgon. For example: If the SVS or MVS system programmer "owns" the
system residence volume and keeps it in his virtual machine at
virtual address 150, the OSVS user could gain access to it with this CP command:
link vs2sysp 150 250 w [name]l
In this command VS2SYSP is the programmer's userid, and NAME is the
write password. lIf an installation is using password-on-the-command-line suppression, a
user cannot specify the password on the same command line. Passwords must be entered in such a way that they are either not displayed on display terminals or typed upon a mask for typewriter terminals.
126 IBM VM/370 operating Systems in a Virtual Machine

• 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