H06.27 Software Installation and Upgrade Guide

Drain the Spooler (Optional)
Use the SPOOLCOM;SPOOLER,DRAIN command to perform an orderly shutdown of the Spooler.
Failure to do so can cause problems during a warm start of the Spooler.
Before executing the SPOOLCOM;SPOOLER,DRAIN command:
1. Use the SPOOLCOM;COLLECT $collector-process, LISTOPENS command to identify
processes that currently have jobs open.
2. Use the SPOOLCOM;JOB (STATE PRINT) command to determine which jobs are currently
printing.
Take the appropriate action to ensure that these jobs either terminate when finished or are stopped.
After receiving the SPOOLER DRAIN command, the supervisor stops accepting jobs for collection
or printing (new opens are rejected with a file-system error 66—device downed). Each collector
stops when it has no more open jobs. Each print process finishes printing active jobs and then
stops.
After all collectors and print processes have stopped, the supervisor process stops itself. The Spooler
enters the dormant state, ready to be warm started.
CAUTION: Never use the TACL STOP command to halt the Spooler. The control file can be
corrupted during the next warm start or rebuild.
For more information on draining the Spooler, see Support Note S99086, NSK Spooler—Migration
and Draining Instructions and Chapter 1 and Appendix H in the Spooler Utilities Reference Manual.
Back Up the Spooler Control Files
While the spooler environment is closed, back up the spooler control files to render a known
database from which you recover in case of a catastrophic spooler failure. Make sure that you
drain the Spooler:
BACKUP/OUT SPLBKUP/$TAPE,($SYSTEM.SPOOLER.*,$DATA01.SPOOLER.DATA),LISTALL
ZPHIRNM
During the Build/Apply phase, DSM/SCM places product files in their subvolumes with temporary
(fabricated) file names so that the new file names do not conflict with the file names of currently
running programs. The ZPHIRNM program renames files that currently have actual file names with
fabricated names and renames new files, which have fabricated names, with their actual names.
ZPHIRNM is run from the DSM/SCM subvolume.
Using ZPHIRNM PREVIEW Mode
You can do a preview run of ZPHIRNM to check that the target subvolumes (TSVs) and associated
map files are consistent. Running ZPHIRNM in PREVIEW mode simulates the ZPHIRNM process
without actually updating files or activating the configuration. In PREVIEW mode, ZPHIRNM indicates
whether TMF needs to be up when running ZPHIRNM. For example, if no SQL program files need
running, TMF is not required to be running along with the ZPHIRNM program.
If ZPHIRNM is run in PREVIEW mode, ZMODGP will be run in TRIAL mode. The new ZcccGP files
will be named ZFBccncc, but cannot be easily distinguished from non-ZcccGP files also named
ZFBccncc.
Example of ZPHIRNM for H06.03:
Statistics:
TSVs:
TSVs in new configuration .................. 129
112 Running ZPHIRNM