Maintain Discard and Report Files
By default, discard files and report files are aged the same way. A new discard or report file is created at the start of a new process run. Old files are aged by appending a sequence number from 0 (the most recent) to 9 (the oldest) to their names.
If the active report or discard file reaches its maximum file size before the end of a run (or over a continuous run), the process abends unless there is an aging schedule in effect. Use the DISCARDROLLOVER and REPORTROLLOVER parameters to set aging schedules for the discard and report files respectively. These parameters set instructions for rolling over the files at regular intervals, in addition to when the process starts. Not only does this control the size of the files and prevent process outages, but it also provides a predictable set of archives that can be included in your archiving routine. For more information, see the following documentation:
No process ever has more than ten aged reports or discard files and one active report or discard file. After the tenth aged file, the oldest is deleted when a new report is created. It is recommended that you establish an archiving schedule for aged reports and discard files in case they are needed to resolve a service request.
Table 12-1 Current Extract and Aged Reports
| Permissions | X | Date | Report |
|---|---|---|---|
-rw-rw-rw- |
1 ggs ggs |
4384 Oct 5 14:02 |
TCUST.rpt |
-rw-rw-rw- |
1 ggs ggs |
1011 Sep 27 14:10 |
TCUST0.rpt |
-rw-rw-rw- |
1 ggs ggs |
3184 Sep 27 14:10 |
TCUST1.rpt |
-rw-rw-rw- |
1 ggs ggs |
2655 Sep 27 14:06 |
TCUST2.rpt |
-rw-rw-rw- |
1 ggs ggs |
2655 Sep 27 14:04 |
TCUST3.rpt |
-rw-rw-rw- |
1 ggs ggs |
2744 Sep 27 13:56 |
TCUST4.rpt |
-rw-rw-rw- |
1 ggs ggs |
3571 Aug 29 14:27 |
TCUST5.rpt |