Procedures for moving OAM to another system

This section provides information on moving OAM from one OAM system to another OAM system, neither of which is part of an OAMplex. To merge OAMs into an OAMplex, perform the procedure in Merging OAMs into an OAMplex.

The following steps are necessary when moving the entire OAM application from one single system to another single system. These steps can be followed after the installation and migration steps have been completed, should you need to move OAM from one system to another.

  1. Install OAM and DB2 on system SYS2 by following the procedures in High-level installation and migration checklists.

    _______________________________________________________

  2. Make copies of the OAM DB2 databases from system SYS1 using DB2 utilities. The OAM DB2 databases are the Object Storage Databases, Object Administration Database, and the OAM Configuration Database described in Understanding OAM databases.

    _______________________________________________________

  3. Copy the Integrated Catalog Facility (ICF) catalog where the collections reside from system SYS1 using the Export function of Access Method Services (IDCAMS). For more information on this Export function, see z/OS DFSMS Access Method Services Commands.

    _______________________________________________________

  4. Start DB2 on system SYS2.

    _______________________________________________________

  5. Move the copies of the OAM DB2 databases to system SYS2 using DB2 utilities.

    _______________________________________________________

  6. Move the copies of the collection definitions to the Integrated Catalog Facility (ICF) on system SYS2 using the Import function of Access Method Services (IDCAMS).

    _______________________________________________________

  7. Delete all of the optical library and drive definitions from system SYS1 using the ISMF Optical Library Application.

    _______________________________________________________

  8. If system SYS2 is not defined in the SCDS, then from system SYS1 add it as a valid system under the Control Data Set Definition Application of ISMF.

    _______________________________________________________

  9. Move the SCDS from system SYS1 to system SYS2 by using the copy function of DFSMSdss. This only needs to be done if system SYS2 is not part of the same complex that is sharing the SMS SCDS.

    _______________________________________________________

  10. Using the ISMF Storage Group Application on system SYS2, alter the Object and Object Backup storage group definitions to change the connectivity of SYS1 to not connected and the connectivity of system SYS2 to enabled.

    _______________________________________________________

  11. Using the ISMF Optical Library Application on system SYS2, alter the library definitions connectivity from system SYS1 to system SYS2. This is only applicable for the controlling libraries. Altering these models automatically alters any connected library expansion units associated with the controlling libraries.

    Tip: You might need to delete and redefine all the 3995 operator-accessible drives.

    _______________________________________________________

  12. Using the ISMF Optical Library Application on system SYS2, redefine all of the library definitions. Using the ISMF Optical Drive Application on system SYS2, redefine all of the drive definitions associated with the libraries. If the definitions do not exist in the DB2 OAM configuration database tables, they are added, but if they do exist, the information is updated in the DB2 tables. The information is added to the SCDS.

    _______________________________________________________

  13. Activate this SCDS from system SYS2. Activation might be done from the operator console by using the SETSMS SCDS (source control data set name) command or by using the Activate Configuration option of ISMF.

    _______________________________________________________

  14. Start OAM.