The spooling operator has responsibility for the following unit
record spooling operations. He must: 1. Verify that the special user identification (ID) card
precedes a user's physical deck of cards to associate the cards
with the correct user·s virtual machine (see "Spooled Card Input.")
2. sure that sufficient blank cards are available for the punch
unit, and that the paper in the printer is the proper size, width,
and number of copies, and that the proper print train is mounted and the print buffer is properly loaded.
3. Separate punched and printed output by user identification (userid)
code.
4. Start, stop, restart, or rearrange the sequence schedules of spool
files to be printed or punched.
The spooling commands are discussed (along with other operator
co •• ands) in the "Operator Commands" section.
The BOLOG Fassword is reserved for users who are not assigned any
privilege class. These users cannot log on to a virtual machine. The
user with the BOLOG password can submit jobs to the ces Batch facility
via the real card reader. The user with the BOLOG password can also be
the recipient of spool files sent by any other logged-on user only if
the other user issued a SPOOL FOR command to the userid having the BOLOG password. SPOOLED CARD IBPUT Spooled input from a real card reader requires a CP ID (identification)
card before the VM/370 system can accept it for Note: Load cards for only one user at a time. V8/370 does not look for In-cards in the middle of the card deck. The CP ID card must be inserted in front of the card deck. Then
place the deck in the empty feed hopper. Then ready the reader device
and push the EOF button. The reader immediately processes the cards (if
no errors are encountered) and place the file on a direct access device.
The file now resides in the virtual machine card reader that was
identified by the CP ID card. Note that a file is transferred fro. the
real reader to the virtual reader regardless of whether that user is
logged on or off. The user may log on at any time to read the file. Section 5. Operator Spooling Functions 215
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
Previous Page Next Page