Forgot to include this segment from the "Managing Catalogs" manual -
You can define a special management class for BCSs. This management class can be shared with other critical system data sets that have the same requirements, to ensure that recent backup copies are available in case a catalog must be recovered. In general, the management class you specify for BCSs should have the following attributes: 1. For expiration, NOLIMIT for all attributes. 2. For migration, NONE for command or auto migration. 3. For backup, a. For backup frequency, specify 0 to have DFSMShsm back up the catalog every occasion that it is changed. b. For administrator or user command backup, specify ADMIN to limit backup operations to storage administrators. c. For auto backup, specify YES. Choose appropriate values for other backup attributes, depending on the needs of your installation. It is generally prudent to keep extra backup copies of catalogs, even after the catalog has been deleted. ************************************************************************************** This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. ************************************************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
