START FLUSH REPEAT LOADBUF SPACE Restart a device after it has been drained. Options allow the
operator to specify the spooling output class for the output
device and output separator records. For a 3800 printer, the IMAGE CHAR, FCB and PURGE options may also be specified.
Immediately halts the output on the specified device and
either flushes that copy of the file from the system, or puts
it into the system hold status for future processing. Supplements the number of copies requested by the user for the
file when it was created. The operator can specify a number from 1 to 99 that is added to the number specified by the
user.
Loads the universal character set buffer of the FCB of the
specified printer with the specified image. If requested, the system verifies the loading by printing its contents on the
affected printer.
Forces the output on the spaced, regardless of the skipping
specified by the file's creator.
printer to be single
or spacing commands The spooling commands alter the
attributes and status of closed spool files that are queued and awaiting
processing. When a co.mand applies to an individual file, the device
type (RDR, PUN, PRT) and the spoolid number must be provided to identify
the file. In most commands requiring a spoolid, the keyword CLASS followed by a valid spool class or the keyword ALL are acceptable
substitutes for the spoolid number. This causes the command to be
executed for all files of the given class or device type. The userid is
the identification of the user issuing the command, except that the system operator must explicitly supply the identification of the user
whose files he wishes to affect or he must specify the keyword which gives access to all files (valid for CHANGE, PURGE, ORDER, and
TRANSFER commands also). CHANGE HOLD FREE PURGE ORDER Changes the filename and filetype, the number of copies, and
the class of the specified file. The CHANGE com.and also
specifies 3800 attributes. Any of the above attributes of a
file can be determined via the QUERY command. Places, via the system operator, the specified file in a hold
status. The file is not printed or punched is released by the
system operator. The operator can hold any user files by
device type.
opposite of the HOLD command. Allows a file or group of files
that were previously held to become available for processing.
However, the user cannot reset a hold that was set by the
operator with the HOLD command.
Removes unwanted spool files from the system before they printed or punched.
Reorders the input files in a virtual
order files by identification number,
combination of the two.
card reader. It can
by class, or by any TRANSFER Transfers a virtual reader to another user's virtual reader
without any processing. The TRANSFER co.mand causes a
changing in the owning userid field in the file's SFBLOK. CP Introduction 1-141

SPOOL FILE ERROR RECOVERY I/O errors on real spooling unit record devices are handled by a
transient routine that is called by D"KIOS after it has sensed the unit
check associated with the error on a spooling device. If appropriate, a
restart CAW is calculated and D"KIOS is requested to retry the
operation, in some cases waiting for a device end that signals that the
failing device has been made ready after manual corrective measures have
been taken. If, after retrying the operation, the error is
unrecoverable, DKKIOS is informed that a fatal error has occurred. D"KIOS then unstacks the interruption, flagged as a fatal error, and
passes control to real spooling executive. The routines that handle
unstacked interruptions in real spooling execute only module operations
that have been completed correctly or those that are fatal errors. If a
fatal error is unstacked, the recovery mechanism depends on the
operation in progress.
For fatal reader errors, processing of the current file is terllinated and any portion of the file that has been read and stored on disk is
purged. The owner of the file is not informed of the presence of a
fractional part of the file in the system.
For fatal printer or punch errors, the SFBLOK for the partially completed file is re-queued to the appropriate output list and
processing can be resumed by another available printer or punch, or can
be deferred until the failing device is repaired.
In any case, the failing device is marked logically offline, and no attempt is made by the system to use it until the operator varies it
back online via the VARY command. If an invalid load module is specified for a 3800 DIAGNOSE code 1'14'), the file involved is held or
printer queue is searched for the next file to print.
user and operator are sent a message (DftKRSE241E), action.
printer (refer to
purged, and the
In addition, the
describing the DASD I/O errors for page writes are transparent to the user. A new page
for the buffer is assigned, the file linkage pointers are adjusted, and
the buffer is rewritten. The failing page is not de-allocated and no
subsequent request for page space is granted access to the failing page.
If an unrecoverable error is encountered while reading a page,
processing depends on the routine that is reading the file. If the
processing is being done for a virtual reader, the. user is informed of
the error and a unit check/intervention required condition is reflected
to the reader. If the processing is being done for a real printer or
punch, the failing buffer is put into the system hold status, and
processing continues with the next file. In either case, the DASD page
is not de-allocated and it is not available for the use of other tasks.
1-148 IBK V"/310 System Logic and Problem Deteraination--Voluae 1