How to re-archive an SMS-managed data set that was recalled the same day?
search cancel

How to re-archive an SMS-managed data set that was recalled the same day?

book

Article ID: 190178

calendar_today

Updated On:

Products

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

Issue/Introduction

Trying to re-archive an SMS-managed data set that was recalled the same day is usually prevented by MC attributes.
With SMSMCBYP set to Y, CA Disk processes a data set without regard of the SMS Management Class attributes associated with the data set.
The related Dsnindex record is flagged as non-SMS, gets an expiration date and IXMAINT will not consider any SMS attributes for its expiration.
Is there any option to bypass the SMS MC attributes and force the backup or archive of data sets, but keep the corresponding Dsnindex records under SMS control?                                

Environment

Release : 12.5

Component : CA Disk Backup and Restore

Resolution

Set sysparm SMSMCBYP to B.  
With SMSMCBYP set to B, CA Disk bypasses the BACKUP and/or ARCHIVE attributes of the MC, but the Dsnindex record for these datasets will remain SMS managed.
That means these entries will remain under SMS control, they will show EXPDT=99365 (non-expire) and IXMAINT will honor the SMS MC attributes. 

Double-check the entries with a LISTS:
//STEP01  EXEC LISTD 
//SYSIN     DD *
  LISTS DUP,DSN=dsname
/*

Additional Information

See description of sysparm SMSMCBYP at link - 
http://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/performance-and-storage/ca-disk-backup-and-restore/12-5/systems/sysparms/system-parameter-definitions/s.html#concept.dita_519b76aed1c239bcc9b2ed137c07da169588f7af_SMSMCBYPn