Renaming a member by stopping DB2

If you want to rename a member of the data sharing group, you should do so either before or while enabling DB2® data sharing. Because DB2 must be shut down during the enabling process, you can perform the tasks that are necessary to rename the member at the same time.

Before you begin

Renaming a member is an activity that you should plan for very carefully. Because every installation has a different configuration, this procedure is not guaranteed to be complete.

About this task

You can do the following tasks when you bring down the DB2 subsystem for the enabling procedure.

Procedure

To rename a member by stopping DB2:

  1. Define the correct profile names for the DSNR class.
  2. Replicate existing PERMIT commands to allow users and groups to access the new profiles.
  3. Complete the installation panels for enabling data sharing. (You cannot change the subsystem name on the installation panels.)

    On installation panel DSNTIPH, modify the archive prefix names to include the member name, like DB2PCAT.DB1A.ARCLG1. Specify the old subsystem name (for example, DB2P) as the group attachment name.

  4. Stop DB2 with MODE(QUIESCE).
  5. Run job DSNTIJUZ to assemble and link-edit the new subsystem parameter data set (DSNZPxxx) and DSNHDECP.
  6. Rename the BSDS and active log data sets with the new prefix, like DB2PCAT.DB1A.BSDS01.
  7. Update the BSDS with the renamed log data sets. Include the same RBA ranges as the original active log data sets:
    1. Run the utility print log map (DSNJU004) to obtain the start and end RBAs.
    2. Use access method services to rename the log data set.
    3. Run the utility change log inventory (DSNJU003) to delete the active logs with the old names.
    4. Run the utility change log inventory (DSNJU003) to add the renamed active logs with the correct ranges. You do not need to add the archive log data sets, because the archive log data sets that you specified on panel DSNTIPH will replace them.
  8. If necessary, increase the size of the BSDS.
  9. If necessary, increase the size of the SYSLGRNX table space.
  10. Rename the startup procedures. For example, change DB2PMSTR to DB1AMSTR. Do not forget to change the BSDS names to the new names in the ssnmMSTR startup procedure.
  11. Make sure that CICS® can connect to the new subsystem. There are several ways of doing this, depending on which level of CICS you are running. Here are a couple of techniques:
    • Change the CICS DB2CONN to use the new DB2 subsystem name, reassemble, and link-edit.
    • Modify the JCL for CICS to include the new subsystem name on the INITPARM.
  12. Make sure that IMS™ can connect to the new subsystem.
  13. Enter the command START DB2 and continue with the rest of the enabling process.