Avoiding ZDBCssid

If necessary, you could avoid needing the ZDBC ssid designation by using a different configuration. Sample scenarios are as follows:

  • Multiple DBC subsystems are running in the same sysplex, they are in different DBC groups, and the RTCS system registry is shared. (For more information, see Multiple DBC groups sharing one RTCS system registry.)

    To avoid the use of ZDBCssid in this situation, you could set up the RTCS system registry to be shared per DBC group. (For more information, see Controlling-sharing-of-the-RTCS-system-registry.)

  • Multiple DBC subsystems are running on the same LPAR but are in different DBC groups. See Different DBC groups on one LPAR.

    To avoid the use of ZDBCssid in this situation, use either of the following options:

    • Require the DBC subsystem registered as defaultdbc to always start first.
    • Set up a dedicated DBC group to be registered with the defaultdbc parameter, include only the LGC agent in it, and always require this DBC group to start before the other DBC subsystems. This configuration uses an LGC options server. The following procedure describes how to set up an LGC options server.

To set up an LGC options server

  1. Customize the sample job LGC$REGD in the hlq.llq.SAMP data set and use this as the input:

    <list>
      <dbc/>
    </list>

    Review the output and verify that the defaultdbc is the DBC that you plan to bring up first and be the host for LGC services. If it is not, use the following input to the job to replace the defaultdbc with the desired one. For example, this input defines the DBC Group PRODPLEX as the defaultdbc:

    <register>
      <defaultdbc replace="yes">PRODPLEX</defaultdbc>
    </register>

  2. Upgrade the DBC registered as the defaultdbc.

    Note

    You apply infrastructure upgrades to the DBC registered as the defaultdbc first to ensure downward compatibility with other DBCs. After upgrading the default DBC you will upgrade any other DBCs you have.

    1. Run the $420INF job.
      1. Review the variables in the $$INCINF member to ensure that the DBC SSID, GROUP, and DBCENV data sets are correct for this DBC.
      2. After the job runs, edit the DBCPRODS member in the runtime BMCENV data set. Place an asterisk in column 1 on PROD lines for any products that you do not want to start in this DBC.
      3. Make sure that PROD=LGCvvrm does not have an asterisk in column 1 so that it will start in this DBC.
    2. Start the DBC for this new environment if it is not already started in version 11.1.00 or later of DBC.
    3. Run the $490TRIG job. 
      This job copies the members from the runtime BMCENV data set to the DBCENV data set referenced in the DBC PROC and starts DBC agents.
      1. Make sure that the LGC agent defined to the task is active.
      2. Review the data sets in the LGCvvrm and LGCOPTS members in the DBC DBCENV data set referenced in the DBC PROC.
        Overrides for data sets can be placed in the LGCOPTS member after it is created by the DBC. Changes in the LGCOPTS member persist from release to release; however, the LGCvvrm member will be replaced with each installation of LGC in order to have values from the installation (such as LOADLIB data set names). For more information on how to override the LOADLIB data sets, see comments in the LGCOPTS member.
        To implement changes to the LGCOPTS member, issue the command  /ssid DBC,EXEC,LGC (where ssid is the DBC ssid). 

    Tip

    After initially running the $4nnxxxx jobs, the LGCvvrm and LGCOPTS members are created for the first time. 

    Once they exist in the DBCENV data set, the next time you want to upgrade LGC:

    1. Update the data sets referenced in the members to the new code base instead of performing this step
    2. Issue the following command on the DBC hosting the LGC Options Server:
      /ssid DBC,EXEC,LGC
      Where ssid is the DBC ssid.

  3. Upgrade all other DBCs (those not registered as defaultdbc).

    Note

    This step may be delayed until a later deployment date if necessary.  Infrastructure earlier than version 11.1.00 in the client can interact with the server at version 11.1.00 or later.

    1. Run the $420INF job.
      Review the variables in the $$INCINF member to ensure that the DBC SSID, GROUP, and DBCENV data sets are correct for this DBC.
    2. Start the DBC for this new environment if it is not already started in version 11.1.00 or later of DBC. 
    3. Edit the $490TRIG job so that all steps except ENVEXEC step are executed (the ENVEXEC is run later in this procedure).
      As generated during the installation, the $490TRIG job contains a // null card to prevent the DBC from enacting changes before you are ready.
      Remove the // null card and add one before the ENVEXEC step.

    4. To prevent LGC from starting in the second DBC Group, edit the DBCPRODS member in the DBCENV data set referenced by this DBC and place an asterisk in column 1 on the PROD=LGCvvrm line.

      Note

      It is important to comment the line by placing an asterisk in column 1 on the PROD=LGCvvrm line so that the change persists from release to release. Otherwise, if the line is deleted, LGC will be added as a new PROD line with each install.

    5. Customize and run the following sample jobs for the type of installation being performed on the products that use LGC. 

      Note

      Run the jobs only once for each subsequent DBC Group, not per DBC. 

      Run the jobs on the DBC registered as the defaultdbc, but reference the DBCENV data set of the second DBC Group.

      For each job:

      • Change the STEPLIB to reference the LOADLIBs for DBC, NGI, LGC, USC, and SCC infrastructure code.  
      • Change the DBCENV DD to point to the correct data set for this subsequent DBC Group.

      The sample jobs are in the  HLQ.llq SAMP data set. The Jobs to run based on type of installation table below indicates the jobs to run based on the type of installation you are performing. The "How to customize the jobs" table below explains each job and how to customize it.

      Type of installation

      Description

      Jobs to run

      New

      The product has never been installed. Default options will be used and a default optionset will be created using the name of the DBC Group.

      LGC$1REG

      LGC$2IMP

      Upgrade

      The product is executing at a previous release level. The optionsets will be migrated forward to the new release and updated with new values from the pppvvrm member in the DBCENV data set (where ppp is the 3-character product code and vvrm is the version, release, and maintenance level).

      LGC$1REG

      LGC$2IMP (Only run this job for product IOD.)

      LGC$3MIG

      LGC$4UPD

      Maintenance

      The product was reinstalled at the GA level which was already executing. The optionsets will be updated with new values from the pppvvrm member in the DBCENV data set (where ppp is the 3-character product code and vvrm is the version, release, and maintenance level ).

      LGC$1REG

      LGC$2IMP (Only run this job for product IOD.)

      LGC$4UPD.


       How to customize the jobs

      Jobname

      Purpose

      How to customize

      LGC$1REG

      Register the product templates to LGC.

      This job is applicable to the following products:

      DOM = SQL Performance for DB2 and BMC System Performance for DB2
      IOD = APPTUNE for DB2
      GUD = BMC Workbench for DB2
      BRD = BMC Subsystem Optimizer for zEnterprise (Subzero)

      Perform the following task:

        1. Change the first three characters of the member name specified by <envmember>.

      Example: <envmember>GUDL001</envmember>

      This will register the product templates for BMC Workbench for DB2 (GUD).

      LGC$2IMP

      Import a default optionset for a new installation.

      For APPTUNE for DB2, imports the canned Filter Optionsets.

      This job is applicable to the following products:

      DOM = SQL Performance for DB2 and BMC System Performance for DB2
      IOD = APPTUNE for DB2
      GUD = BMC Workbench for DB2
      BRD = BMC Subsystem Optimizer for zEnterprise (Subzero)

      Perform the following tasks:

        1. Change the first three characters of the member specified by <envmember>.
        2. Change the value specified by <envdbcssid> to the DBC subsystem ID of the client DBC subsystem.
        3. Change the value specified by <envdbcgroup> to the DBC Group Name of the client DBC subsystem.

      Example:

      <envmember>GUDL002</envmember>
      <envdbcssid>DCSA</envdbcssid>
      <envdbcgroup>DBCPLEX1</envdbcgroup>

      This will import a default optionset for BMC Workbench for DB2 (GUD) and resolve values to DCSA and DBCPLEX1 for any symbolic variables referencing the client DBC subsystem ID or group name in member GUDL002.

      LGC$3MIG

      Migrate all optionsets from the previous release to the new release.

      This job is applicable to the following products:

      DOM = SQL Performance for DB2 and BMC System Performance for DB2
      IOD = APPTUNE for DB2
      GUD = BMC Workbench for DB2
      BRD = BMC Subsystem Optimizer for zEnterprise (Subzero)


      Perform the following tasks:

        1. Change the value for <prodcode> to the three-character product code.
        2. Change the value for <prodvrsn> to the current version being installed for this product.
        3. Change the value for <fromvrsn> to the previous version that had optionsets.

      Example:

      <product>
            <prodcode>DOM</prodcode>
           <prodvrsn>1210</prodvrsn>
      </product>
      <fromvrsn>1120</fromvrsn>

      This will migrate all optionsets from version 11.2.00 of SQL Performance for DB2 and BMC System Performance for DB2 to version 12.1.00.

      LGC$4UPD

      Apply updates from the pppL003 member to the product optionset specified in the pppOPTS member in the client DBC DBCENV data set.

      This job is applicable to the following products:

      DOM = SQL Performance for DB2 and BMC System Performance for DB2
      GUD = BMC Workbench for DB2


      Perform the following tasks:

        1. Change the LGCUPD DD data set to reference the XML data set for this product containing the pppL003 member.
        2. Change the value for <prodcode> to be the three-character product code.
        3. Change the value for <prodvrsn> to be the current version being installed for this product.
        4. Leave the value for the <name> element as &OPTSET. This will be resolved to be the name that is currently in use by the product specified in the ppp OPTS member in the client DBC DBCENV data set.

      Example:

      <product>
           <prodcode>GUD</prodcode>
           <prodvrsn>1210</prodvrsn>
      </product>
      <name>&OPSET.</name>

      This will update the optionset specified in the GUDOPTS member using values from GUDL003.

    6. Run the ENVEXEC step in the $490TRIG job.
      The LGC agent will not start in this DBC. Products will retrieve their optionsets from the LGC agent in the defaultdbc .
    7. Run the $500 series of jobs (if generated).
    8. Replicate the installation to other DB2 subsystems using the $700 series of jobs.
      For more information, see Replicating-the-installation-to-other-DB2-subsystems.
    9. After completing all the jobs to deploy the products, verify that the products are working correctly:
      1. Check the DBC log and DBCPRINT for messages to ensure that the product agents are running successfully.
      2. Invoke the product CLIST (if applicable) or run a batch job to verify that the products are working correctly.

If you need help with a specific situation or you need more information, contact BMC Customer Support.

Related topic

Replicating-the-DBC-by-using-a-different-DBC-group



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*