When running disconnected, a user must reconnect to the DOS/VS virtual machine to enter the interruption that causes DeS/VS to continue
reading jobs.
To use CMS to spool jobs to a disconnected DOS/VS virtual machine,
sFool the reader of the DOS/VS machine with the CONT operand:
spool reader cont
Then, if another job is received in the card reader of the DOS/VS machine befcre the currently executing job stream has completed, the job
just received is also read and executed. Thus, when running a series of
jcbs in a single job stream and the reader is spooled with the ceNT
oFerand, a user can continue to send (from the virtual machine)
additional jobs to the DOS/VS virtual machine for execution. Under these circumstances, a user does not have to reconnect to
the DOS/VS virtual machine to signal an interruption, unless the
currently executing job stream finishes before the next job is received
in the card reader.
If DOS/VS is running disconnected and is processing many jobs, a user may want to obtain printed output for completed jobs without waiting for
all the jobs to finish. When running DOS/VSE with the VSE/Advanced Functions program Product (5746-XE8), iM/370 automatically releases spooled printer output to iSE/POWER. However, for DOS/iS Release 34 (or earlier), release spooled
Frinter outFut (either accumulated directly or through the FOWER/VS program) by reconnecting to DOS/VS and issuing the command: close printer
This command releases the SYSLST output accumulated thus far. However,
when using the POWER/VS program and a dedicated printer, all spooled
output files are under the control of POWER/VS spooling, and not VM/370 spooling.
When running DOS/VS disconnected, a 15-minute time-out begins
ccnsole read occurs. If the virtual machine does not respond
read before the 15 minutes elapse, VM/370 automatically logs
virtual machine.
when a
to the
off the
For examFle: DOS/iS is running disconnected, and a program running
in the machine comFletes execution or issues a PAUSE request. The
virtual machine is logged off after 15 minutes unless the user
reconnects the virtual machine and issues the BEGIN command. Section 3. DOS/VS in a Virtual Machine 103

When running DOS/VS disconnected, VM/370 ignores all output or "writes" tc the virtual console unless the console is spooled. To spool virtual
ccnsole a virtual machine user can issue the following CP command befcre disconnecting the virtual machine: #cp sFcol console start
This command starts recording all console output on a spool file. When the user logs on again, he can issue:
spool console stop close
This command stoFs console spooling and releases the spool file to the
real printer. If this command is not entered, VM/370 saves all spooled
ccnsole outFut except the last 4K page of output. Developing and Testing Programs to Run In a DOS/VS Virtual Machine
The foregoing discussions noted how to use the eMS editor and the EXEC facility tc help Frepare jobs for execution in a DOS/VS virtual
machine. In addition tc these CMS features, there are a number of other CMS commands for developing and testing programs on CMS disks. One advantage of storing source programs on CMS disks is that they can be
maintained as backup cOFies of a program while a second version is being
tested and debugged. CMS has a specia I e nvironmen t, called CMS/DOS, which provides many
commands that simulate the functions of DOS/VS or DeS/VSE if VM/370 Basic Systea Extensions Program Product (5748-118) is installed. An installation needs this program product for VM/370 to support FE-512
devices in its configuration. (For DOS/VSE to access FE-512 devices, an
installation also needs to install the VSE/VSAM program Product, Program NO. 5746- A M 2 • ) Some of the things that can bs done in CMSjDOS are: • Creating eMS macro libraries from DOS/VS assembling programs directly in CMS. (Assembler
are disFlayed on the terminal.) macro libraries and
diagnostic messages • Compiling Frograms written in DOS/VS COBOL or DOS/VS PL/I programming
languages, using DOS/VS macro libraries. • Displaying or printing the directories of DOS/VS private or system
core image, relocatable, source statement, or procedure libraries. • Displaying or Frinting the procedure library. • Link-editing TEXT decks from eMS disks, or relocatable modules from DOS/VS or Frivate relocatable libraries. These simulated core image
libraries called DOSLIBs are on a CMS disk. Users can also copy
relocatable modules from DOS/VS libraries. • Loading core image phases from CMS DOSLIBs or from DOS/VS core image
libraries into virtual storage and executing them. • Identifying system and programmer logical units for programs being
used and listing current assignments. 104 IBt'5 VM/370 operating Systems in a Virtual Machine