FLASH -flash count overlay use
This information is contained in theVSPIBLOK for a virtual printer. When the file is closed, the information is contained in the first DASD
buffer.
Input file processing is similar to output file processing, except for
the open and close functions, and the analysis ofCCW commands and the
direction of data movement.Many common routines are utilized to locate
and verifyCCWs, obtain buffer space, and to move the spooling data.
The difference in the open function is that instead of creating anew it is necessary to locate a reader file that already exists in the
system. To do this, -the open subroutine scans theSFBLOKs chained from the anchor, READERS, to find a file with an owner userid that matches that of the caller and is not in hold status. If a file is not found, a
unit check or intervention required condition is reflected to the
virtual machine; otherwise, itsSFBLOK is chained to the control block
for the reader and the channel program is interpreted in thesame manner
as for an output file.
After the input file is exhausted, a unit exception is reflected to
the user machine, unless the user has requested either continuous
spooling or that anEOF not be reflected. With continuous spooling, the
unit exception is not reflected until the last file for that virtual
machine is processed. IfNOEOF is specified, the simUlation terminates
with a unit check or intervention-required condition (similar to what
happens if theEOF button on a real reader is not pushed).
In
unless
saved.
either case, the input file is then deleted from thesystem, the user has specifically requested that his input files be
If the file is saved, it can be re-read any number of times.
Support of virtual consoleI/O for both the virtual
is provided as an option for theVM/370 spooling
support fulfills thefollowing requirements: machine and VM/370 capabilities. This • Provides hardcopy support for CMS Batch Facility virtual machines. • Provides hardcopy support for display devices used as system or
virtual machine consoles.• Allows disconnected virtual machines to spool virtual console output, CP commands and system resources to disk instead of losing the
output.• Improves the performance of virtual machines that currently produce a
largeamount of console output. Whenever a SIO is issued to a virtual machine console, the virtual
console manager(DMKVCN) determines if the spooling option is active.
If it is, control is passed to the virtual spooling manager atDMKVSPBP to insert the data into a spool file buffer. While console spooling
utilizes, basically, thesame code as printer spooling, the following
exceptions aremade: CP Introduction 1-141
This information is contained in the
buffer.
Input file processing is similar to output file processing, except for
the open and close functions, and the analysis of
direction of data movement.
and verify
The difference in the open function is that instead of creating a
system. To do this, -the open subroutine scans the
unit check or intervention required condition is reflected to the
virtual machine; otherwise, its
for the reader and the channel program is interpreted in the
as for an output file.
After the input file is exhausted, a unit exception is reflected to
the user machine, unless the user has requested either continuous
spooling or that an
unit exception is not reflected until the last file for that virtual
machine is processed. If
with a unit check or intervention-required condition (similar to what
happens if the
In
unless
saved.
either case, the input file is then deleted from the
If the file is saved, it can be re-read any number of times.
Support of virtual console
is provided as an option for the
support fulfills the
virtual machine consoles.
output.
large
console manager
If it is, control is passed to the virtual spooling manager at
utilizes, basically, the
exceptions are