Typical Bind Scenarios

We recommend that you bind the product packages and plans using DRDA protocol. With DRDA, packages and plans are bound on the local subsystem, but the packages are also bound and executed on the remote subsystem. DRDA remote binds can be accomplished while connected to the local or remote subsystem.
dm19
We recommend that you bind the product packages and plans using DRDA protocol. With DRDA, packages and plans are bound on the local subsystem, but the packages are also bound and executed on the remote subsystem. DRDA remote binds can be accomplished while connected to the local or remote subsystem.
Following are examples of typical bind scenarios that can occur during the post-installation and customization processing:
Example: Performing a New Install with Remote Data Access
When you are performing a new base install with DRDA protocol and remote data access, use the following process to bind packages locally and remotely and all plans locally.
  1. Prepare the SETUPxx parmlib member for each local subsystem as follows:
    • Specify YES for DRDA Remote Binds (SSREMOTE) on the local subsystem.
    • Add the local subsystem and each remote subsystem to the location list for the local subsystem.
    The same SETUPxx parmlib member should include a subsystem section for each remote location, with each subsystem section also specifying YES for DRDA for Remote Binds.
  2. Generate and execute the Bind Product Packages and Plans DB2 customization task with bind task 0.
    You
    must
    execute the Bind Product Packages and Plans task with option 0 every time you perform a base install of all products into a DB2 subsystem.
    The generated job creates and executes a temporary file of commands that will bind all packages locally and remotely and all plans locally. You can now run the product on the local subsystem and access data on all remote subsystems using the DRDA protocol.
    If you have several remote subsystems assigned to a given local subsystem, you may find that this job becomes too large, or one or more of the subsystems may not be active. If this occurs, change the SETUPxx member DRDA Remote Binds option (SSREMOTE) to NO for each subsystem and use bind task 0 to generate and execute the bind job separately on each local and remote subsystem.
Example: Accessing Remote Data from a Local Subsystem
In this example, we assume you have bound packages and plans only locally on a subsystem with DRDA. To access remote data from that local subsystem, do the following:
  • Make sure that the remote subsystems are included in the SETUPxx parmlib member location list for the local subsystem.
  • Make sure that each remote subsystem has its own subsystem section in the same SETUPxx member.
  • Specify DRDA Remote Binds (SSREMOTE) YES for the local subsystem and generate and run the Bind Product Packages and Plans task using option 0 (Bind all product packages and plans) locally and remotely. Alternatively, you can specify DRDA Remote Binds (SSREMOTE) NO for the local subsystem and then generate and run a bind job separately for each subsystem.
Example: Using a Remote Subsystem with DRDA as a Local Subsystem
If you have already bound packages with DRDA on a remote subsystem and now want to use that subsystem as a local subsystem, bind the product plans on that subsystem using Bind Packages and Plans task option 2 (Bind all product plans only).
Example: Using a Remote Subsystem with Newer Versions of DB2
When the remote subsystem has a newer version of DB2 than the local subsystem, some of the product packages cannot be bound remotely while connected to the local subsystem. If you specified YES for DRDA Remote Binds (SSREMOTE) in your SETUPxx parmlib member and option 0 for the bind packages and plans task, when the job is generated, it omits the remote subsystems with newer versions of DB2.
To bind packages on a remote subsystem with a newer version of DB2 than the local subsystem, select the newer versioned subsystem as the local subsystem in the SETUPxx parmlib member and generate and execute bind task option 0 or 2.
Example: Binding Changed Packages for Maintenance for a Service Pack or PTF
To bind changed packages for maintenance from a Service Pack or PTF, generate and execute Bind Product Packages and Plans option 1 (bind only product packages for maintenance). Make sure that the SETUPxx member has DRDA Remote Binds (SSREMOTE) YES specified for the local subsystem.