the reader, the file is closed by writing the final buffer to disk and
co.pleting and queuing the SFBLOK to the reader's file chain. If the
owner of the file is currently logged on, he is given a message indicating that a file has been read and if he has an available card
reader, it is posted with a device end interruption. In available
reader is one of the correct class which is ready, is not busy, has no
active file, and has no pending interruptions. Various routines in CP accumulate, for.at, and punch account cards that
contain system usage information for certain users. These routines
format the information into an SO-column card image preceded by a punch CCW and call DMKACOAQ to queue the card for real output. DMK1COAQ calls DMKACOPU to punch the card on a real punch, if one is available;
otherwise, the card is queued in main storage until a punch is free. When a punch finishes processing its last file, a test is made to see if any accounting cards have been queued. If they have, DMK1COPU is called
to process thea. In addition to the cards generated by CP to account for a virtual machine's use of syste. resources, the user may request cards to be
punched in order to account for the use of virtual machine resources by jobs running under his userid. In order to do so, the user must have
the account option (ACCT) entered into the directory.
To punch an accounting card, the user must issue a code X'004C' DIAGNOSE instruction with a pointer to either a parameter list
containing user-specified "charge to" information, or a data area
containing up to 10 bytes of user-specified information to be punched
into the accounting card. DMKHVC validates the instruction operands,
builds an account buffer (ACNTBLOK), and DMKACOQO is called to queue the
card for real output. For additional information about this user
option, see "DIAGNOSE Interface (DMKHVC)" under "privileged
Instructions." When the user accounting option is being utilized, the user .ust keep
in mind that each additional accounting record requested is occupying
real storage space. Degradation of system performance occurs if
available storage becomes filled with accounting data. SPOOLING COMMANDS The spooling co.mands provide an interface
operator, and the spooling syste.. There
commands: Those that affect virtual devices Those that affect real devices
between the user, the system are three types of spooling Those that affect spool files that are queued within the system The commands that affect virtual devices are generally available to
all system users, and a user can only affect the status of devices that
are attached to his own virtual machine. Com.ands that affect the
status of the real system's spooling devices can be used by the system operator only. Commands that affect closed spool files that are
awaiting processing are generally available to all users, with some additional capabilities assigned to the system operator. For example, a 1-144 IBM VK/370 System Logic and Problem Deteraination--Volume 1
user may alter the characteristics only of those files that have an
owner's userid that matches his own, whereas the system operator may change any spool file in the system.
Each spool file in the system has a number of attributes that are
assigned to it, either explicitly or by default, at the time that it is
created. These attributes and their values are as follows: Filename and filetype can be 24-character fields. Either or both
can be replaced by a user-supplied val ue. Spoolid number is a system-assigned number between 1 and 9900. It
is automatically assigned when the file is created (input) or closed
(output), and is unique within the system. The file;s owner, the device type, and the id number are specified. Usually, the userid
defaults to the identification of the user issuing the given
command. Because the identification number rather than the filename and filetype is an identifier, duplicate user-assigned names do not
present an identification problem. The number of logical records (cards or print lines) in the file is
an integer between 1 and 16 million5 For printer files, the record
count also includes any immediate operation code space or skip CCWs. The originating user is the identification of the file's creator, if
the file has been internally transferred from the originator's
printer or punch to the new owner's card reader. The number of copies requested for an output file is between 1 and
99. Unless altered by the user or operator, it defaults to 1. The device type is used by DIAGNOSE for a file transferred to a
reader to determine the virtual type of output device. I. CHARS for 3800 printer I. FCB for 3800 printer I. MODIFY for 3800 printer I. FLASH for 3800 printer
In addition to those attributes, a file that is queued for real
output or virtual input always has a class associated with it. 1 class
is a single alphameric character from 1 through z or from 0 to 9. It
controls both the real or virtual device on which the file will be
printed, punched, or read, and the relative priority and sequence of
output on the device. While each file is assigned a single class, each
real spooling output device can be assigned from one to four classes.
The device then processes only files that have a class attribute that
corresponds to one of its own, and processes these files in the order
that its own classes are specified.
For example, if a printer is assigned the classes A, D, 2, it
processes any printer file with a class of A before it searches the
printer output queue for a file with class D. All class D files are
printed before class 2 files.
The output class for a file is assigned at the time the file is
created and is the class that is associated with the virtual device that
created it. While each real spooling device can have up to four
CP Introduction 1-145
Previous Page Next Page