Life cycle action delete-expired
Life cycle action delete-expired parameters
The following parameters are available:
Parameter | Format | Description | Default |
|---|---|---|---|
--simulate | yes/no | Life cycle runs in simulation mode, meaning no actual deletes occur | yes |
--target | cloud | The target storage to be scanned Only cloud is supported. | cloud |
--action | delete-expired | The life cycle action to be performed | delete-expired |
--scan-start-date | yyyy-mm-dd | The projection start date to start scanning from Accepted values are past dates only. | Previous successful run date |
Additional parameters
You can specify the following additional life cycle parameters in the agent.yml configuration file:
Parameter | Description | Default value |
|---|---|---|
lifecycle.deleteExpired.gdg.minimumDays | The minimum number of days that a data set is kept after being archived After the number of minimum days has passed, the data set is checked whether it is eligible for deletion. | 7 |
lifecycle.deleteExpired.gdg.intervalDays | After the minimum number of days has passed, the data set is checked whether it is eligible for deletion. The data set will be checked every x days. | 4 |
lifeycle.deleteExpired.cds.catalogexpiration.minimumdays | The minimum number of days that a cloud data set with catalog-controlled expiration (EXPDT=99000) is kept after being created After the number of minimum days has passed, life cycle checks if the data set is still cataloged. If it's not, the content is removed, and if it's not removed, it's postponed by the intervalDays value. | 7 |
Process output DDs
Delete-expired opens four output DD files. The following table includes details about each DD:
Output DD name | Description |
|---|---|
STDOUT | The life cycle delete-expired output |
SYSOUT | The JVM output |
SUMMARY | A list of files that were deleted, including a periodic summary that is printed every five minutes |
UTILMSGS | The IDCAMS output lock |