The procedures for same as thcse used in runn1ng IIcde. The prillary difference punch and printer to the other
to the user's own userid:
logon cllsid
sp pun osvs (route jobs to OSVS user)
disconn
logon osvs Icp sp prt cmsid Icp sp pun cmsid (run 0 S/VS jobs) DISCONNECTION CONSIDERATIONS with two virtual machines are lIuch the
a single virtual machine in alternating
is that a user now spools the virtual
virtual machine instead of spooling them When using lIore operating systems,
than one userid to
consider:
alternate communications between How OS/VS may read additional jobs from the card reader? What happens when a read is issued at the disconnected OS/VS virtual
console? What happens to the console output of the disconnected virtual
machine? When using CMS to route jobs to a disconnected OS/VS virtual machine, spool the OS/VS reader with the CONT operand of the CF SPOOL command: spool reader cont
This cOllmand allows the OS/VS reader to read more than a single job
at a time without opera tor intervention. When running OS/VS disconnected, a 15-minute time-out begins when a
console read occurs. If the read does not occur within the 15 minutes, VM/370 automatically logs off the virtual machine. Whenever running OS/VS disconnected, it is suggested that a console
leg be created. This log provides a user with a history of what jobs
were run. It can also indicate any unusual circumstances that occurred
during the terminal session.
136 IBM VM/370 Operating systems in a Virtual Machine
To start console spooling, issue:
spool cons start To stop console spooling and to print the log. 1ssue: spool console stop close When a virtual machine is running disconnected, all console output is
lost unless a user initiates console spooling, such as by issuing:
tcp speol console start SFooling of the console output continues until a user either logs off or
issues:
tcp spool console stop
Disconnecting the virtual machine does not stop console spooling.
Therefore, the spooled console log for a terminal session, punctuated
with several disconnects, consists of one uninterrupted printer file.
Developing and Testing Programs to Run In an OS/VS Virtual Machine
The previous discussions demonstrated how the efts editor and EXEC facility can help a user prepare jobs for execution in an as/vs virtual
.achine. In addition to these eMS functions, there are a number of
ether eMS commands for developing and testing programs.
For example: A user can use the eMS READCARD and commands
to create eMS files from source programs or existing JCL that are on
cards or magnetic tape. One advantage of storing source programs on CMS disks is that they can be maintained as backup copies of a program while a second version is being tested and debugged. By using the C!S editor or commands like COPYFILE, SORT, and RENAME, a user can modify
and copy CMS disk files.
Refer to for information on how to compile
and execute many types of OS/VS programs under CES. OS/VS2 MVS Uniprocessor Under VM/370 When operating MVS in uniprocessor mode under V!/370, VE/370 simulates tbree privileged and two nonprivileged System/37C The three Frivileged instructions are: CLRIO (clear I/O) IPK (insert PSW key) SPKA (set PSW key from address) Section 4. OS/VS in a Virtual Eachine 137
Previous Page Next Page