In most cases during virtual machine operation, a user can use the tcp
function te enter CP commands directly from the virtual machine. If the
virtual machine has issued a read to the terminal, enter a CP command
with the #CP function. For example: When no longer using virtual tape
drive 397 mapped to real tape drive 492, issue:
#cp detach 397 tcp msg cp i am done with real drive 492 VM/370 immediately processes these command lines, and the virtual
machine read remains outstanding.
Note: A user may not always be able to enter CP commands with the tcp function. The read issued by as/vs at the terminal must be for at least
as many bytes as entered in the #CP command line; any additional
informatien is truncated. If the read is for at least three bytes,
enter the iCP command. This command places the user in CP command mode
from which CP commands can be entered directly. To return to the
virtual machine environment, enter the BEGIN command.
Using OS/VS In Batch Mode Under VM/370 When many users submit jobs to a single as/vs virtual machine, someone
is generally needed to tend the machine as an operator. The virtual
machine oFerator must make those decisions required of an operator on a
real machine; that is, deciding what work is going to be done and what
is the most efficient way of doing it.
In batch mcde, one user runs as the as/vs machine (userid OSVS) and
other users (like CMSI01) may submit jobs either through the virtual
card reader, through the system card reader, or through JES remote
stations. If the card reader is not dedicated to the CS/VS virtual machine, place an 10 card at the beginning of each job stream, such as: USERID asvs A
In this card: the USERIO (or 10) indicates the valid beginning of an ID
card, asvs is the name of the VM/370 user to receive the card input in
his virtual reader, and A is the VM/370 reader class. If the VM/370 system operator has dedicated a card reader to the OS/VS virtual machine, then the 10 card must be omitted at the beginning
of the deck.
A user can send jebs to the as/vs machine from other virtual machines
by spooling his punch to the as/vs userid, such as: tcp speol punch to osvs
Entering this statement causes subsequent punched output to appear in
the virtual card reader for userid asvs.
132 IBM VM/370 operating Systems in a Virtual Machine
Alternating Between eMS and OS/VS Under VM/370 When working in a program development environment (rather than a
producticn environment) and unable to test programs directly under CMS, a user can alternate between OS/VS and CMS in a single virtual
machine. Seme advantages of this technique (described in this topic)
are: Reduced unit record output. Users can examine program output and
compiler listings online, check the results, and resubait the job
without producing any output on the system unit record devices. Faster turnaround time (generally) than in a batch environment.
Before using this technique, users should be familiar with the eMS editor and CMS file manipulation commands found in the !M/3IQ LOADING CMS INTO A VIRTUAL MACHINE To load CMS into a virtual machine, use the CP IPL command and specify either a saved system name or a device address:
ipl ells -- or --
ipl 190 When CMS responds with a message like this: CMS VERSION 3.0 Enter the CMS commands to create an OS/VS job stream. USING THE CMS EDITOR TO PREPARE JOB STREAMS The fcllowing CMS procedure creates an OS/VS job streaa that can be passed to the OS/VS virtual machine's reader. It shows how to compile a
PL/I program under OS/VS, making the PL/I source file available as a CMS file called PLI27 DECK.
edit pli127 jcl
input
//pli 127 job cps,fred,lIsglevel=1
//cat exec plifc
Iisysin dd *
(null line)
getfile pli127 deck
input
/*
//
(null line)
file
open a CMS file by name
go into input mode enter jcl entries I , return to edit .ode
copy over PL/I source file
go into input mode enter jcl entries , to edit mode write the file to disk Section 4. OS/VS in a Virtual Machine 133
Previous Page Next Page