Automatic Archival

The automatic report archival extension allows a site to create a copy of its reports for archival purposes. The original reports continue to print as usual. With this feature, a site can backup all reports or a specified subset of reports. If a report is lost, it can be easily reprinted from CA View.
view
The automatic report archival extension allows a site to create a copy of its reports for archival purposes. The original reports continue to print as usual. With this feature, a site can backup all reports or a specified subset of reports. If a report is lost, it can be easily reprinted from CA View.
The word
report
in the previous paragraph applies to any SYSOUT data set for which normal open and close processing is performed.
Note:
For more information about automatic report archival, see the topic System Extensions .
Contents
Non-Eligible Output
JES does not perform the normal open and close processing for the job log, JCL listing, and job message data sets. Therefore, the job log, the JCL listing, and the job message data sets are not eligible for automatic archival.
Examples
The following examples illustrate archiving.
Example 1
This example assumes that CA View is set to archive all SYSOUT with a destination of R99 (the master index file is initialized with the parameter DEST=R99). You want to produce and archive to tape a copy of all production reports and those test reports written to SYSOUT classes J and K. Production jobs are defined as those jobs with classes P, Q, R, and S. Test jobs are defined as all jobs with classes T, U, V, and W.
The following parameter field starts the CA View system extensions:
PARM=',PQRS/*//R99//T,TUVW/JK//R99//T'
Example 2
This example assumes that CA View is set to archive all SYSOUT for class S (the master index file is initialized with the parameter CLSL=S). You want to produce and archive to disk a copy of all reports written to SYSOUT classes A and B, and to produce and archive directly to tape all other reports.
The following parameter field starts the CA View system extensions:
PARM=',*/AB/S///D,*/*/S///T'
Running in Batch
The archival task can run as a started task or as a batch job. Previous releases required that a user modification, HA17SE01 or HA20SE01, be applied to the SARSTC module to enable the task to run as a batch job. Beginning with r11, this user modification is no longer required.
Note:
If you run the archival task as a started task, you can ensure the integrity of the archived data, because, only an operator executes the programs. However, after modification to run as a batch job, the integrity of the archived data is no longer being assured, because any user can execute the program. If batch execution is essential to your operation, you must provide for data integrity in other ways, such as placing the load modules in a passwordprotected library.