Running HARDCOPY

In order to maintain a hard copy of ODT traffic, an installation must first ensure that HARDCOPY and PRINTCOPY are loaded on the same disk family, and then do one of the following:

  • Designate HARDCOPY as a supervisor program by entering one of the following CS (Change Supervisor) system commands. Specifying HARDCOPY as a supervisor program causes the program to be automatically initiated after a halt/load.

    CS SYSTEM/HARDCOPY
CS SYSTEM/HARDCOPY ON <family name>

  • You can also include HARDCOPY in the MCP AI (Automatic Initiate) list. This alternative also causes HARDCOPY to be automatically initiated after a halt/load. Refer to the System Commands Operations Reference Manual for more information about the AI command. 

AI + HARDCOPY = SYSTEM/HARDCOPY
AI + HARDCOPY = SYSTEM/HARDCOPY ON <family name>

Examples

The following is an example of a Work Flow Language (WFL) job that runs HARDCOPY: 

BEGIN JOB;
   RUN SYSTEM/HARDCOPY;
END JOB

The default disk family used for the file titled *HARDCOPY is DISK. If a system does not have a family named DISK, the family used by the halt/load unit becomes the default. Installations having specific requirements regarding the placement of their files can use the WFL MODIFY statement to change the default family. In the job below, MODIFY permanently changes the FAMILY attribute of *SYSTEM/HARDCOPY so that *HARDCOPY defaults to a family (DISK422) that is different from the one used by the code file. 

BEGIN JOB CHANGEFAMILY; STRING CODEFILE, DATAFILE;
   CODEFILE:="DISK00";  DATAFILE:="DISK422";
   MODIFY *SYSTEM/HARDCOPY ON #CODEFILE;
   FAMILY DISK = #DATAFILE OTHERWISE #CODEFILE;
END JOB
Prev  Up  Next
HARDCOPY  Home  Disk File Format