1 user can start or stop virtual console spooling any ti.e during a
ter.inal session with the SPOOL CORSOLE com.and. For a description of
the CP SPOOL and CLOSE co •• ands, see the £R !B! Use£!. Rote: The user cannot use console spooling to stack co •• ands for subsequent execution. The console spool file is for historical purposes
only.
If a permanent I/O error occurs during a real I/C operation, you restart
the spooled files as follows: • Printer files--from the beginning of the current page (the last skip
to channel 1). • Punch files--from the beginning of the spool file. • Beader files--fro. the beginning of the real deck (the operator .ust normally place the card deck back in the reader). • Console files--do not restart.
the console file. The virtual
console spooling. CP ends console spooling and purges
.achine continues without further
Bote: If an I/O error repunches only the error
nor.al punch spool files.
occurs while punching accounting cards, CP card and not the whole file as in the case of SPOOL BUFFERS The buffers used in virtual .achines while collecting and writing spool
data are each olie page ('1096 bytes) long, and contain both the data to be transcribed and all CCls necessary for operating the unit record
devices that perfor. the transcription. Syste. failures that end syste.
operation can cause virtual .achine operators to lose up to one page of
spooling data.
Buffers used for the te.porary storage of spool data on its way between auxiliary storage and the user's virtual .achine are allocated
fro. a pool of virtual pages that belong to CP. Direct access devices
provide the auxiliary storage necessary for CP spool buffering. CP uses unit record devices to spool input and output operations. However, certain features or functions that pertain to this group of
.achines are not supported. Consult the V8/370 restrictions listed in
the Y!L370 ana the list of devices suitable for spooling devices (both unit record and direct access) listed in "Appendix B: System Require.ents." llso see the !!L370 PlgBniBg gnd §y!g!. 212 '8/370 Operator's Guide

SPOOL FILES Each spool file in the system has a number of attributes that are
assigned to it, either explicitly by default, at the tiae that it is
created. These attributes and their values are as follows: Each of these consist of alphaaeric fields of up
to eight characters. The CHINGE or CLOSE command can change these
fields. This is a system-assigned number between 1 and 9,900. It is
automatically assigned when the file is closed, and is unique to that
spooled file. To identify a given file, it is necessary to specify the
userid of the file's owner, the device type, and the spoolid nuaber. In most instances, the userid defaults to the ID of the user issuing the
given command. Since the ID nu.ber, rather than the filenaae and
filetype, is used as an identifier, duplicate user-assigned names do not
present an identification problem. Q§!! ID: This is the ID of the file's creator, if the file
has been internally transferred froa the originator's virtual printer or
punch to a new owner's virtual card reader. !yaber of This is the number requested for an output spool file;
it This is a nuaber between 1 and 99. Unless specified by the user or operator, it defaults to 1. Time: This is the date and tiae that the file was created. Users create-most files from virtual spool devices and the date and tiae
indicate when the originator of the file closed the device. !yaber Q! This is a six-digit number indicating the number of
logical record (printer or card iaages) in the file and is an indication
of the size of the file. OUTPUT CLASSES In addition to the attributes described above, a file queued for output
on a real unit record device always has an output class associated with
it. A single alphameric character (A through Z, 0 through 9, and the
special character *) controls what real device the file is to be printed
or punched on, and the relative priority and sequence of output on the
device. Although each file is assigned a single class, you can
designate each real spooling output device to handle froa one to four
classes. The device processes only files that have a class code that
corresponds to one of its own, and processes these files in the order
you specify. For example, if you assign a printer the classes I, D. and
2, it always processes any printer file with class I before it searches
the printer output queue for a file with class t, and all class D files
are printed before any file with class 2. You can assign a class of *
to a real output unit record device to allow that device to process any class spool file. Section 5. Operator Spooling Functions 213