CA View - After receiving a SARBKU02 message, ALL archival stopped, not just direct to tape archival
Article ID: 145609
After receiving a SARBKU02 message, ALL archival (including archival to DISK) stopped, not just direct to tape archival. Since the View database is very large, the backup cycle runs for hours. Users are unable to see their reports in CA View until the backup cycle has completed.
CA View Exploitation of the SARINIT parameter TAPECLSL used for direct to tape archival
The product working as intended.
- SARSTC will collect sysouts from the JES spool and archive them to DISK while the backup cycle is running, as long as the sysouts are NOT direct to tape archivals. - Once a direct to tape archival sysout is encountered and the SARBKU02 is received, ALL archival is suspended until the backup cycle has complete. - Archival to DISK is suspended because the archive task is waiting for the direct to tape sysout to be archived. - Direct to tape archival is suspended because the TAPE that would be used for direct to tape archival is currently allocated to backup cycle processing, until such time as a copy of the master index is written to the TAPE. The writing of the master index occurs at the END of the backup cycle. - If a direct to tape sysout is never encountered, the archival task will continue to archive during the backup cycle.
Understanding a customers concerns for using the TAPECLSL parameter for direct to tape archive functionality, and their need to have immediate access to their report data during the time the backup cycle is running, we recommend the following.
Define 2 SARFSS collectors:
- One with a small line limit lim=0-50000, - And one with a large limit lim=0-2000000.
NOTE: WITHOUT the direct to tape archival CLASS specified in the collectors.
These FSS collectors will continue to collect sysouts from the JES spool and never encounter a direct to tape sysout because you did NOT specify the direct to tape CLASS in the FSS collectors work selection criteria.