Can a Report Going to CA View be Forced to be Written to Tape?
Article ID: 124300
Updated On:
Products
OM Deliver
OM View
Issue/Introduction
The client sometimes collects very large sysouts to their View database, which sometimes fills their database to near capacity.
Is there a way to force large reports to go directly to tape?
How does View process a report, in collection and backup?
Environment
Release:
Component: VIEW
Component: VIEW
Resolution
View can write collected sysout directly to tape, so that the sysout (mostly due to size) will never be on the disk layer.
For example, using the following SARINIT parameters:
. CLSL=ABC
. TAPECLSL=C
. In the above, sysout of class C would get written directly to tape.
. Note: The class(es) used in TAPECLSL must also appear in CLSL.
View's mode of processing is as follows:
. A report is collected to the disk layer (unless it is collected to tape).
. In a View backup are two "phases":
. . In Phase 1, newly collected reports not yet written to tape, will get written to tape.
. . Note: At this point, the report is on both disk and tape.
. . In Phase 2, report retentions are evaluated, for how long the report is to reside on disk, and how long to reside on tape.
For example, using the following SARINIT parameters:
. CLSL=ABC
. TAPECLSL=C
. In the above, sysout of class C would get written directly to tape.
. Note: The class(es) used in TAPECLSL must also appear in CLSL.
View's mode of processing is as follows:
. A report is collected to the disk layer (unless it is collected to tape).
. In a View backup are two "phases":
. . In Phase 1, newly collected reports not yet written to tape, will get written to tape.
. . Note: At this point, the report is on both disk and tape.
. . In Phase 2, report retentions are evaluated, for how long the report is to reside on disk, and how long to reside on tape.
Feedback
Yes
No
Powered by
