Bind for Product Execution

The Provide Access to Optim at Remote/Local Subsystems menu lists the steps in the final bind. As with the Full Installation menu, you can press ENTER to proceed through the steps.

------------- Provide Access to Optim at Remote/Local Subsystems -------------
OPTION  ===>

     1 - Create SYNONYMs to access the DB2 Catalog & Product Directory.
     2 - Setup Plan for Product Execution at the Current Location.
     3 - Setup Plans for Product Execution at Remote Locations.

     Plan Owner          ===>
     Plan Qualifier      ===>
     Directory CreatorID    : SYSFOP
     Table Library DSN   ===> 'OPTUSR.PROD.SFOPTENU'

Optim does not explicitly reference either the Product Directory or the
DB2 Catalog.  Synonyms for the Plan Qualifier must be established to the
directory and catalog (or an alternate set of tables/views) before binding.

********************************** N O T E S *********************************
* Plan/Package owner must have SYSADM or BINDADD authority, SELECT privilege *
* on Catalog, ownership of Optim Directory Tables, and authority to change   *
* the SQLID.                                                                 *
******************************************************************************

Select the steps in the order listed:

1. Create the synonyms required to bind the plan.

   The synonyms are for the DB2^® Catalog and the Optim™ Directory tables. You will have the opportunity to specify the synonyms to be used for a shadow catalog in order to run against tables other than the DB2 Catalog tables. If you do not modify the default values specified, the synonyms for the DB2 Catalog tables are created.

2. Setup plan for product execution at the current location.

   You are prompted for the specifications to bind the packages and to grant user execute authority on the packages. Also, you are prompted for the specifications to bind the plan and then to grant user execute authority on the plan.

3. Setup plans for product execution at remote locations.

   Once the packages have been created, you can setup plans to access the remote subsystems. Remote subsystems are available to users by specifying the location name in the LOCATION prompt provided on the Optim main menu.

   This step is performed only if you intend to access remote subsystems from the current location. This step is performed at the local subsystem.

You are prompted for the plan owner and qualifier. The plan qualifier owns the synonyms created prior to binding the plan. The plan owner must have the authorization to change the SQLID to the plan qualifier.

Note that if you intend to use more than one release of Optim at your site, you should provide a unique plan qualifier. If you specify the plan qualifier used for an existing plan, any existing synonyms are dropped to create the new synonyms, and the existing plan is then invalidated. (See Run Multiple Releases for additional information.)

The Directory CreatorID is provided for your information and cannot be modified here.

You are also prompted to specify the dataset name of the table library. This table library dataset contains a table of the plans created for remote access. You can maintain this table using Option 3 on the Provide Access to Optim at Remote/Local Subsystems menu. Also, this table is used to provide the selection list of available locations if requested by a percent sign (%) in the LOCATION prompt on the main menu.