Bind Product Packages and Plans

The Bind Product Packages and Plans task lets you generate the following types of BIND tasks:
dm19
The Bind Product Packages and Plans task lets you generate the following types of BIND tasks:
  • Bind all product packages and plans locally and remotely
  • Bind only product packages for maintenance locally and remotely
  • Bind all product plans on a single local subsystem
  • Bind only product packages for maintenance on a single local subsystem
When binding product packages and plans, note that coexistence of mixed releases in a data sharing group can add complexity because DB2 allows only two different release levels to coexist in a data sharing group:
  • A single old-release at New Function Mode
  • The new release at an appropriate Compatibility Mode
We recommend that you execute the Bind Product Packages and Plans DB2 catalog customization task on the lowest level member. For example, on V10NFM when the logical version of a data sharing group is mixed V10NFM and V11CM. For more information about binding the product packages and plans and automatic rebinds in a coexisting data sharing group, we recommend that you review the IBM documentation about mixed releases in a data sharing group.
This task must be executed under the following circumstances:
  • Every time you install products into a DB2 subsystem.
  • When applying SMP/E maintenance and the RECEIVE Exception SYSMOD Data Report indicates that new DB2 objects are needed or existing DB2 objects have changed.
  • When migrating (upgrading) to a new DB2 version, mode, or function level. In this circumstance, you must first update the subsystem DB2 information in the SETUPxx parmlib member before you execute this task.
SMP/E PTF HOLDDATA may contain rebind IDs that are listed in the RECEIVE SUMMARY REPORT printed by SMP/E RECEIVE. However, it is not valid to select individual members from the CDBASKL1 library. All of the rebind IDs must be processed together as a set to properly update the DB2 catalog with the correct package versions. Be sure to execute this task for each PLANSxx member in parmlib that you intend to use for a given DB2 subsystem. You will have to choose unique names for the generated JCL members.
To bind product packages and plans
  1. Type
    3
    (Tasks) on the Post-Install Tailoring panel and press Enter.
    The Select DB2 Subsystems panel appears.
  2. Select a subsystem or multiple subsystems and press Enter.
    The Select DB2 Tasks panel appears.
  3. Select the
    Bind Product Packages and Plans
    task and press Enter.
    The Generate JCL for DB2 Tasks panel appears.
  4. Select an entry or multiple entries and press Enter.
    The Bind Product Packages and Plans panel appears.
  5. Specify an option (0, 1, 2, or 3):
    All options bind on the selected local subsystem. Options 0 and 1 also bind on all remote subsystems based on values.
    Press Enter.
    The BIND control cards are generated in batch when the job is run, and written to a temporary data set. You must choose unique names for the JCL members generated.
  6. Submit the generated JCL for execution.
    The scope of the generated bind job is influenced by the DRDA Remote Binds (SSREMOTE) setting you specify for the local subsystem in the SETUPxx parmlib member and by the selected option for this task.