z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Adding OAM systems to an existing OAMplex

z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support
SC23-6866-00

This section provides information on adding OAM systems to an existing OAMplex. When you initialize OAM, it looks for the OAMXCF statement in the CBROAMxx PARMLIB member. If the OAMXCF statement exists, this OAM system joins the XCF group, which means that it joins the OAMplex. Each OAM system in the OAMplex share the DB2 databases (object storage and OAM configuration databases).

  1. Update the IGDSMSxx PARMLIB member for each OAM system that you are adding to the OAMplex. For more information, see 5 Changing system libraries.
    1. Add the DB2SSID parameter to the IGDSMSxx PARMLIB member. The DB2SSID parameter specifies the name of the DB2 system.
    2. Add the OAMPROC and OAMTASK parameters to IGDSMSxx only if you need to start the OAM address space to initialize SMS on the new system.
    3. Issue the SET=SMSxx command to update the SMS information.

    _______________________________________________________

  2. Update the CBROAMxx PARMLIB member to include the ONLYIF statement to specify whether or not specific statements, within the CBROAMxx, are to be processed on a given system.
    Figure 1. CBROAMxx PARMLIB Member Samples Using the ONLYIF Statement and Optional Parameters
    ONLYIF SYSNAME(system_name|*ALL*)
                      OAMXCF statements
                      SETDISK statements
                      SETOAM statements
                      SETOPT statements
                      SETOSMC statements

    _______________________________________________________

  3. Update the OAMXCF statement in the CBROAMxx PARMLIB member to include the XCF group name and OAM member name for each OAM system that you are adding to the OAMplex. Each OAM system has a unique OAMMEMBERNAME and belongs to the same OAMGROUPNAME. For more information, see OAMXCF statements in an OAMplex.
    Figure 2. CBROAMxx PARMLIB Member Samples Using the OAMXCF Statement and Optional Parameters
    OAMXCF OAMGROUPNAME(OAMGRP1)
           OAMMEMBERNAME(OAMSYS1)
           XCFTIMEOUT(XCFOPTREADA(20) XCFOPTREADM(50)
                      XCFOPTWRITEA(150) XCFOPTWRITEM(150) 
                      XCFTAPEREADA(40) XCFTAPEREADM(50))

    _______________________________________________________

  4. Set up an OAM PROC with the OAM=xx parameter for the new system, where xx is the low-order suffix of your CBROAMxx PARMLIB member. For more information, see step 5h2 in 5h Updating the PROCLIB.

    _______________________________________________________

  5. Set the OSMC processing system to the desired system for each Object and Object Backup storage group.

    _______________________________________________________

  6. Update all the Object and Object Backup storage groups so that they are enabled to each system where OAM is running. For more information, see Defining storage groups and relating the libraries to the storage groups.

    _______________________________________________________

  7. Ensure that the DB2 tables are in a data sharing group. Contact your DB2 administrator to set up the data sharing group.

    _______________________________________________________

  8. If applications connect to DB2 and call OAM, the DB2SSID and the data sharing group that they connect to must be the same, or else the "Connects to two DB2s from one TCB" error displays. Contact your DB2 administrator for assistance with this step.

    _______________________________________________________

  9. Run the CBRSMERG and CBRS100 jobs to merge the OAMs into the OAMplex at this point. For more information, see Merging OAMs into an OAMplex.

    _______________________________________________________

  10. Start OAM on each system in the OAMplex. Display the DISPLAY SMS,OAMXCF command on each system to verify that they joined the OAMplex successfully.

    _______________________________________________________

Result: Now all of the OAM systems belong to the OAMplex.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014