Default language.

Applying changes to the $729DOP1 and $730DOP2 jobs


If you modify any of the values in the $729DOP1 or $730DOP2 job after configuration, use the following procedure to apply the changes.


  1. After making the changes, rerun the $729DOP1 and $730DOP2 jobs.
  2. For products listed in the following table, if you changed the plan name, edit the bind job and bind the plan:

    1. In the bind job listed for your product in the following table, change the plan name to the plan name in $729DOP1 and $730DOP2.You must perform this action for each product for which you changed the plan name.
    2. If needed, change the product collection ID in the PKLIST statement (the first parameter of this statement) to match the plan name.
    3. (ALTER, 

      Catalog Manager

      Change Manager

      , and DASD MANAGER only) Edit the control table in the BMCDB2 CLIST by changing the name of the plan to match the plan name that you changed in $729DOP1 and $730DOP2.

    4. Rerun the bind job.

      Important

      If you are using data sharing and plan to use mixed versions of Db2 in the same data sharing group, complete the following steps:

      • Ensure that the DSNZPARM ABIND is set to COEXIST.
      • Use the earliest version of Db2 in the data sharing group to perform the bind.

    Bind jobs

    Product

    Bind job 1

    ALTER

    ACMssidB

    Catalog Manager

    ACTssidB

    Change Manager

    ACMssidB

    CHECK PLUS

    ACKssidB

    DASD MANAGER PLUS

    ASUssidB

    LOADPLUS

    AMUssidB

    REORG PLUS

    ARUssidB

    UNLOAD PLUS

    ADUssidB

    Any NGT utility

    NGTssidB

    1 The ssid variable represents the ID of the Db2 subsystem where you will run the job. If one is available, run the IVP job to verify that the changes took effect. For more information, see the IVP information in Customizing BMC products and solutions for Db2.

 

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