|
|
|
|
|
Maximum number of generations of the job to keep in the History Jobs file. For z/OS jobs, only.
Additional information |
Description |
|---|---|
Usage |
Optional. |
Format |
00 - 99 generations. NOTE: When the Retention Generations field is left blank, History Jobs file information is kept as specified by the Retention Days parameter. For more information, see Retention Days. |
Variable Support |
None |
Alternate names |
|
Jobs in the History Jobs file are easier to restore to the Active Jobs database (for example, for restart) than jobs archived to CDAM. Therefore, it may be desirable to retain several of the most current generations of the job in the History Jobs file.
Retention Generations enables specification of the number of generations of the job to keep in the History Jobs file. Once the specified number of generations has been reached, as a new generation is added to the History Jobs file, the earliest remaining generation is deleted.
Retention Days and Retention Generations are mutually exclusive. A value can be specified for either, but not both.
When changing job criteria from Retention Days to Retention Generations (or the reverse), previous job criteria are lost and are not acted upon.
For retention criteria to hold across job executions, the jobs must be identical in all respects. (For example, if a job is transferred to a different folder it is treated as a different job for purposes of retention. In this case, retention values are reset, and retention is calculated from the moment of transfer.)
At sites that do not use the History Jobs file, this parameter is not relevant and is not displayed.
Parent Topic |