Operations and Commands

Describes system operations and commands.
casp14
This section describes system operators, the start command, data sets, and
Spool
commands.
2
2
System Operator
In general terms, a system operator can be:
  • The MVS console operator.
  • Any
    Spool
    user with a user ID authorization level 2 is an operator, when logged on to a display terminal.
  • Any
    Spool
    user with the appropriate authorization level when using a communication channel through an application program. This includes Menu System users, who can also issue commands to control the product.
System Start and Stop
This section provides information about the MVS start command, initialization options, and the stop command.
MVS Start Command
Enter the following MVS command to start
Spool
:
S esf
where
esf
is the name of the procedure used to start the
Spool
system. In some installation-specific cases this may not be ESF.
Initialization Options
Specify the following options in the PARM parameter of the EXEC statement in the procedure used to start
Spool
. If not specified,
Spool
prompts for options during initialization.
Use the OS Reply command to enter one or more of the following options:
  • BUILDQ -- Initiates a warm start and rebuilds the file queue.
  • COLD -- Initiates a cold start and formats the in-core file queue.
  • FORMAT -- Initiates a format cold start.
    Spool
    formats all its spool data sets, and initializes the in-core file queue.
  • LIST -- Produces a listing of the parameter data set.
  • LOG -- Initiates a
    Spool
    system log. This log records all the messages issued by
    Spool
    .
  • NOFMT -- Switches off the FORMAT option.
  • NOLIST -- Switches off the LIST option.
  • NOLOG -- Switches off the LOG option.
  • SCAN -- Initiates a syntactical check of the
    Spool
    parameter data set, after which
    Spool
    will terminate.
  • WARM -- Initiates a normal warm start.
  • U -- Initiates a normal warm start.
  • NULL -- Initiates a normal warm start. When
    Spool
    is successfully initiated, it enters into a
    waiting for work
    mode and is ready to process requests.
Stop Conditions
The following conditions must both be satisfied in order for
Spool
to stop.
  1. The network interface must be stopped using
    one
    of the following methods:
    • Issue the PNET command, which is the normal way to stop the network interface.
    • Issue the TNET command, which can be used if the interface must be stopped immediately. Be aware that all active network sessions are interrupted.
  2. All files must be closed using
    one
    of the following methods:
    • Issue the SHUTDOWN command to enable applications with open files to complete before
      Spool
      stops. No applications are allowed to open files after this.
    • Issue the SHUTDOWN,F command to stop
      Spool
      regardless of open files.
    • MVS STOP command
      P esf
      esf
      is the name of the procedure used to start the
      Spool
      system. In some installation-specific cases this may not be ESF. This is the same as entering the SHUTDOWN,F command to stop
      Spool
      regardless of open files.
Multi-Access
Spool
Multi-Access Spool (MAS) configuration enables sharing of common checkpoint and spool data sets up to 32
Spool
systems.
Cold and Warm Starts
The first system in the complex can (if desired) be cold started, and the other members of the configuration can join the complex by performing a warm start.
File Affinity
When a spool file is created, the application program may specify that the file has affinity to a single system in the MAS configuration. A spool file with affinity to a single system can only be printed on printers, or processed by application programs, on that system. However, the characteristics or status of the spool file may be altered by any system in the configuration. A file without system affinity can be processed by any system in the Multi-Access Spool (MAS) configuration. You can change the affinity of a spool file with the Reset File (TF) command.
Checkpoint and Spool Data Sets
Spool
must have one checkpoint data set and one or more spool data sets. The
Spool
checkpoint data set is allocated on a direct access volume with the default data set name CAI.ESFCHKPT. The
Spool
data sets are allocated on direct access volumes. The default spool data set name is CAI.ESFSPOOL. The structure and organization of the checkpoint and spool data sets and the data set names are specified by the
Spool
parameter data set.
A secondary checkpoint data set can be defined, which is used as a duplex copy of the primary checkpoint data set. Therefore, it can be used for manual recovery in case the primary checkpoint data set becomes unusable.
File Queue Data
This section provides file queue data including check-pointing, destination names, and whether a printed file is purged.
Checkpoint
The
Spool
system maintains an in-core file queue, which is check-pointed whenever it is changed. Each spool file in the system is identified by a unique file sequence number, an eight-character filename, an eight-character file destination name, and an eight-character user ID. The filename is not used directly by the system and can contain any alphanumeric character string. It can be used simply as a file description.
Destination Name
The destination name is used to identify the printer node on which the file is to be printed. Any printer in the network group in which the destination printer is defined may select the file for print processing, unless it operates in restricted-selection mode. If a printer operates in restricted-selection mode, it only selects files for output processing if their destination name matches the real node name or alias name of the printer.
Remember that each file has an output class definition (A-Z, 0-9), an
8-character form number, and a 4-character forms control buffer name.
Purging and Retaining Files
When a
Spool
file has been printed, it may or may not be purged automatically. This is usually specified by users, who can usually keep files as long as necessary, even after they have been printed.
You can retain any particular file after it has been printed. The file is marked as printed and retained for a specified number of hours. If you want to retain files for longer, the Re-queue File (RF) command can be used to remove the file printed indicator. Non-printed files are also eligible for automatic purging, but they are kept in the system for an installation-dependent additional time, which is added to the normal file retention time.