If a CA View SARSTC task experiences a hang condition (generating a SARSTC24 message) during the collection of a large report to the database disk layer, this article outlines the steps regarding how to address the condition.
This procedure should be used only to address a large report that has started being collected to the disk layer of a View database via SARSTC, but is not to be collected due to its size:
. Put the problem sysout on hold in the JES spool.
. To message "SARSTC24 No more space in database xxxxxxxxxxxxxxxxx - Reply R (retry), B (backup), N (new), C (clean), OR T (terminate)", choose one of the following recovery options:
. . Run the SARDBASE program to add more space to the database, or manually delete SYSOUT groups to free up space while the archival task waits. After you allot more space, reply R to have the archival task retry its archival with the additional space.
. . Reply B to force the archival task to execute its backup cycle. As part of its backup cycle, the archival task deletes the generation of SYSOUT on disk that is in excess of the NGEND= initialization parameter, freeing some space.
. . Replying N has the same effect as B, except that a new tape is used for the backup cycle.
. . Reply C to force the archival task to scan its database for SYSOUT groups left in an OPEN state due to a system crash and recover the space used by them.
. . Reply T to terminate the archival task.
. Determine what is to be done with the original problem sysout on the JES spool, but do NOT release it for View to collect again.