Why do you think that additional backup copies will alleviate an underallocation condition in the primary MCDS?
If you want to keep 6 copies of MCDS backups, you also need to keep 6 copies of the BCDS, JRNL, and OCDS. But keep in mind that their only purpose is historical. To inform HSM of the change you need to issue the SETSYS command with CDSVERSIONBACKUP parameter with at least the BACKUPCOPIES subparameter. And then it would probably be a good idea to incorporate the change in the ARCCMDxx member or PARMLIB. I thought VSAM datasets could have more than 16 extents. :>: -----Original Message----- :>: From: IBM Mainframe Discussion List [mailto:[email protected]] On :>: Behalf Of George Rodriguez :>: Sent: Thursday, August 23, 2012 4:30 AM :>: To: [email protected] :>: Subject: Changing Size of DFSMShsm Auto Backups of the Control Datasets :>: :>: I found in the z/OS DFSMShsm Implementation and Customization Guide, :>: member ALLOCBK1, which provides a sample job that defines four backup :>: versions of each control dataset and allocates those backup versions on :>: DASD volumes. I modified the JCL to allocate six backup versions that :>: mirrors what's out there now, but I don't know how to get DFSMShsm to :>: use :>: the new allocations. :>: :>: My original problem is that the MCDS is under allocated cylinders (20,5) :>: and I've reached the 16 extent limit. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
