April 1, 1981
Because output for a user file starts on a real device, the following
message occurs: {
-PRT}- raddr {OUTPUT OF}- userid FILE PUN REPEATED = file RECDS = norecs COpy = nn a typ
raddr userid file
norecs
nn
a
typ
The OUTPUT the REPEATED
they start.
is the real device address.
is the identification of the owner of the spool file.
is the spool file spoolid number.
is the logical record count (lines or cards) for the
file.
is the current copy number being produced where 01 is the
last copy.
is the spool file class.
is the originating device typ (PRT, PUN or CON). OF message occurs yhen the file output first starts and
message occurs for subsequent copies of the same file as
As the card deck starts reading through the real device, the operator
receives the following message:
RDR raddr INPUT FOR userid FILE = file
raddr
userid
file
is the real address of the card reader.
is the user identification of the owner of the file from
the ID card at the front of the deck.
is the spool file spoolid number assigned.
An invalid or missing user identification card on the front of a card
deck, when read, causes an error message on the system console. SPOOL FILES FOR VIRTUAL MACHINES RUNNING BATCH JOBS Usually, when an installation has only one real reader, printer, or
punch, the unit record devices must be shared by all virtual machines.
Before VM/370 can process any virtual machine CP spool files and direct
them to a real device, those files must be closed. For virtual machines
executing batch jobs and using operating systems other than CMS, usually
the operator who initially program loaded the virtual machine operating
system must intervene to issue the CP CLOSE command.
section 5. Operator Spooling Functions 217

Page of GC20-1806-9 As Updated April 1, 1981 by TNL GN25-0834 A feature that closes CP spool files is available for OS/VS1. When the VM/VS Handshaking feature is active, VS1 closes the CP spool files
by issuing the CP CLOSE command when the VS1 Job output from its DSD, terminator, and output writer is completed. Once output files are
closed, they can be processed by V!/370 without operator intervention.
without the VM/VS Handshaking feature, CP spool files are not sent to
the real printer or punch until the virtual machine operator intervenes.
Using the eMS Batch Facility The Batch Facility is a V8/370 programming facility that runs under CMS. It allows a VM/370 user to run jobs in batch mode by sending jobs from
either his own virtual machine or the real card reader to a virtual
machine dedicated to running batch jobs under the Batch Facility. This
dedicated machine is aenerallv set uo at a terminal in the
installation's computer room and is controlied by the system operator.
The Batch Facility virtual machine runs continuously, executing all
jobs spooled to its virtual card reader from other virtual machines or
from the real card reader. The batch operator need pay no attention to
the batch machine once he has started, and disconnected it. I STARTING THE BATCH VIRTUAL MACHINE The system operator starts the batch virtual machine by logging on with
a batch userid and loading CMS using the CP IPL command.
Every installation in which the CMS batch facility is available should
establish one or more common user ids for the Batch Monitor virtual
machine. Users can then spool their files for execution to the card
reader for that batch userid.
It is the operator's responsibility to log on the V"/370 system using
the batch userid that has been established for his installation.
The userid established for the batch facility virtual machine must
have a read/write work disk in its directory at virtual address 195.
The 195 disk is erased when it is accessed as the A-disk at the
beginning of each job.
218 VM/370 Operator's Guide