The datasets are created by a weekly job which creates a new dataset with a LLQ containing the date (e.g.: D130701. Hence, there is no change to the original dataset. This means only one backup is created. However, the backup gets deleted at the time the original dataset expires -- intermittently.
David G. Schlecht | Information Technology Professional State of Nevada | Department of Administration | Enterprise IT Services T:(775)684-4328 | F: (775) 684‐4324 | E:dschle...@admin.nv.gov -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of David G. Schlecht Sent: Wednesday, July 03, 2013 11:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Missing HSM backups Cheers Mainframe’s Finest, I’m going batty over this or perhaps already have. I have a management class that works for recent data but fails intermittently at the moment of performance. About half the datasets lose their backups around day 50. I have date-derived dataset names that get backups once created but after ~50 days the backups start to disappear. Doing a Listcat ,the problem datasets show LBAKUP of 0000.000.0000. Listcat also verifies that the datasets all have the correct classes and storage group. Since the backups disappear, HSM refuses to delete the expired datasets. There are no references to the problem datasets in the HSM job logs other than an occasional PARTREL. Anyone seen anything like this or have any suggestions on where to look next? The management class and storage group definitions follow: Expire after Days Non-usage . : 35 Expire after Date/Days . . . . : 35 Retention Limit . . . . . . . : 35 Partial Release . . . . . . : YES Migration Attributes Primary Days Non-usage . : 3 Level 1 Days Date/Days . : 5 Command or Auto Migrate . : COMMAND Backup Attributes, Backup frequency . . . . . . . . . . . : 0 Number of backup versions . . . . . . . : 3 (Data Set Exists), Number of backup versions . . . . . . . : 2 (Data Set Deleted), Retain days only backup version . . . . : 70 (Data Set Deleted), Retain days extra backup versions . . . : 35 Admin or User Command Backup . . . . . : BOTH Auto Backup . . . . . . . . . . . . . . : YES Backup copy technique . . . . . . . . . : STANDARD STORAGE GROUP Auto Migrate . . P Auto Backup . . Y Auto Dump . . . N Overflow . . . . N Guaranteed Backup Frequency . . . . . . NOLIMIT David G. Schlecht | Information Technology Professional State of Nevada | Department of Administration | Enterprise IT Services T:(775)684-4328 | F: (775) 684‐4324 | E:dschle...@admin.nv.gov ________________________________ This communication, including any attachments, may contain confidential information and is intended only for the individual or entity to which it is addressed. Any review, dissemination or copying of this communication by anyone other than the intended recipient is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and delete all copies of the original message. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
