Updating IMSRSC repository specifications in the RS catalog repository

You can update the name, auto-open option, security class, and data sets of an IMSRSC repository.

You can change the name of a repository using the RENAME FRPBATCH command. You can change any other repository details using the UPDATE FRPBATCH command.

Here are some implications for performing the various update operations:

• Renaming a repository:
  If you change the name of a repository, the Resource Manager (RM) must be modified to refer to the repository by the new name. To modify the RM to refer to the repository by the new name:

  1. Disable RM from using the repository by issuing the UPDATE RM TYPE(REPO) REPOTYPE(IMSRSC) SET(REPO(N)) command.
  2. Ensure that all RMs are disabled from using the repository by issuing the QUERY RM TYPE(REPO) SHOW(ALL) command.
  3. Modify the CSLRIxxx member of the IMS PROCLIB data set at all RMs to have the new repository name.
  4. Enable RM to use the repository by issuing the UPDATE RM TYPE(REPO) REPO(TYPE(IMSRSC)) SET(REPO(Y)) command.
• Toggling the AUTOOPEN option for the UPDATE FRPBATCH command:

  Changing the AUTOOPEN option takes effect the next time the repository is started.

• Changing the security class:

  Specifying SECURITYCLASS(NULL) for the UPDATE FRPBATCH command results in any existing value being reset in the repository definition. You can use the SECURITY Repository Server (RS) command to refresh the in-storage security settings immediately. Otherwise, the new value takes effect the next time the repository is started.

• Changing the data sets a repository uses:

  You can use the REPDSnRID and REPDSnRMD parameters for the UPDATE FRPBATCH command to change the names of the data sets corresponding to each IMSRSC repository data set pair. This action does not change the status of that repository data set pair in the repository definition. For example, if repository data set pair 3 has a status of COPY1 and you use the UPDATE FRPBATCH command to change the repository index data set (RID) and repository member data set (RMD) names, the new data sets are still treated as COPY1 the next time the repository is opened. Therefore, if you decide to use the UPDATE FRPBATCH command to manipulate the repository data sets while the repository is offline, you must ensure that the actual state of the data sets is compatible with their state as stored in the RS catalog repository before the next time the repository is started.

  Attention: Updating repository data sets incorrectly can result in loss of data. Retain a backup of any data set you intend to change until you confirm that data recovery is successful.