The IDEAL LIST statements can be your friend or enemy. Sometimes they are left in a program's routine that is rarely hit which causes no big problem. However, occasionally, an online program was promoted to production for a heavily used transaction. The LIST statement was also in one of its common routines that was referenced many times within each execution of the program. Therefore, the output grew unusually large each time a user invoked the transaction making the ADROUT fill up very quickly.
Unlike DB Log processing, PSS does not provide us with any external messages letting us know that the ADROUT spool is quickly reaching capacity.
Also, since this is an accidental situation, monitoring the ADROUT percent full on a daily or even hourly basis would not catch this situation.
And, enlarging the size of each ADROUT file in all of our 19 production CICS regions, it would only waste space and prolong the same result.
So, before we start developing our own procedures to:
a) monitor the growth of the ADROUT file per CICS on a more timely basis and trigger a ticket if the percent full is greater than 60%
b) provide a procedure that can list the directory of the ADROUT and either delete the larger files or ALL files that are on that ADROUT.
Has CA or any fellow CADRE members done anything similar to manage the ADROUT file? Any and all suggestions are welcome.