r ,
ID USBRID userid [CLASS n] IBA!E {filename filetype}11 I dsname L 1. Begin punching in column 1.
2. The first field must be one of the following:
ID USERID 3. Separate all fields by one or aore blanks. 4. The second field .ust be the user's identification (userid),
limited to eight characters.
5. The third field
or more spaces
designation (n).
designations.) If
to class A. If
follow userid.
(optional) is CLASS n must separate the through Z and 0 the class option is
the class option is
(if class is assigned); one
word CLASS and the class
through 9 are valid class
not coded, the file defaults
coded, it must i.mediately 6. The fourth field (optional) is the keyword BAftE, followed by filename and filetype (or dsname alone). If only a dsname is
specified, it can be 24 characters long. If both filena.e and
filetype are coded, they are each restricted to a maximum of eight
characters and must be separated by a blank.
An invalid or missing user CP ID card on the front of a card deck,
when read, causes an error message on the system console.
Printed and punched output from virtual machine users is directed to the
appropriate real unit record device. The operator (class D) can control
this spooling output by combinations of output class, hold status, and
other spool com.and operands as discussed earlier. Unless you used the NOSEP option to "START" a device, Vft/310 prints a
two-page separator between all output on printers and punches a
four-card separator between all output on punch devices.
The printer separator gives the pertinent spool file characteristics
as well as real device data. The separator prints the owner userid and distribution code in block letters on two The separator does not
print between multiple copies of the file.
The card separator gives the owner's userid and the distribution
code. The distribution code is expanded to punch each character in four
columns with tvo separating blanks so that visual interpretation of the
punched data is easier.
216 V!/310 Operator's Guide

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