WRONG EXPDT WHILE RETPD=9999

Products

• Disk Backup and Restore - MVS
• DISK BACKUP AND RESTORE- ADD-ON OPTIO
• DISK BACKUP AND RESTORE

Issue/Introduction

Some DSNINDEX records created with RETPD=9999 have RETPD 9998 only. Why is the RETPD in some cases 1 day too short?

 

Environment

Release : Disk Backup and Restore 12.5

Resolution

This occurs only for jobs running over midnight. We need to assign the dsnexpdt (expiration date of the DSNINDEX record) as if the processing all takes place on the 1st day. Changing the value during the life of the job could mean creating a DSNINDEX record that expires later than the ARCHVOL record. This is working as designed.