We want to clean-up automatically old GDG versions.
We want to use TMSEXPDT with the use of RDS.
But when we want to expire a GDG version nothing happens
--> RETENTION INPUT RECORDS READ 1
--> RETENTION DEFINITIONS 1
--> RETENTION ERRORS FOUND 0
--> RETENTION DEFINITIONS IN ERROR 0
OPTIONS IN EFFECT TMCDSN TMC.FILE
0000000 TMC RECORDS UPDATED.
0000528 DSNS ELIGIBLE, NO RDS ENTRY
0000000 RECORDS MODIFIED BY USER EXIT
0000000 RECORDS BYPASSED BY USER EXIT
This works fine when we put a gdgbase or a non-gdg as input.
When we adapt in ISPF-CA1, online the EXPDT from CATALOG to CURRENT date for a GDG version it works fine.
In the design of CA 1, we did not allow for the specification of the GDG number as part of the RDS rule. If you are specifying the entire data set name for a GDG do not put a "-" at the end to mask the "GnnnnVnnn" portion on the name.
We will need to use TMSUPDTE or TMSUDSNB or the ISPF panels to extend or change the retention for these specific volumes or gdg files.