Space announcement

   

The Using section of the MainView for DB2 documentation is now available in Japanese. The displayed language is dependent on your browser language. You can switch languages from the Language menu.

Db2 target system considerations

Consider the following points when customizing the Db2 target system and the BBI-SS PAS.
  • MainView for DB2 libraries are not required in your Db2 system.

  • One BBI-SS PAS can monitor multiple Db2 systems (see BBPARM member BBIJNT00).

Note

Version 12.1 of MainView for DB2 supports Db2 Versions 10 and later. A MainView for DB2 PAS can monitor Db2 subsystems at two different Db2 releases if the Db2 load library used in the PAS contains the appropriate call attachment facility (CAF) compatibility level. Contact IBM for information about upward-compatibility PTFs for the lower release load library.

  • The BBI-SS PAS establishes a CAF connection to Db2 that detects Db2 startups and shutdowns, and establishes a Db2 thread to use the Db2 Instrumentation Facility Interface (IFI) for workload requests.

    Note

    If the MainView for DB2 CAF connection to Db2 is lost for any reason, you can use following BBI control commands:

    • To RESET a Db2 that is started, specify:

      .E BM <db2Ssid>
    • To START a Db2 that is not connected, specify:

      .S BM <db2Ssid>
  • The BBI-SS PAS loads Db2 CAF related modules. These modules must be present in the BBI-SS PAS STEPLIB or available via the LNKLST. If these modules are not present, MainView for DB2 is unable to connect to and monitor Db2 targets.

To bind and authorize the Db2 Plan name for Db2 targets

The BBI-SS PAS uses a Db2 Plan to connect to Db2 by using the CAF function. The Db2 Plan default name is BMCMVDB2. You can modify the default name for each Db2 by specifying the PLAN= parameter in the DMRBEXxx member in hlq..UBBPARM. You can find sample jobs in the BBSAMP dataset.

For each target Db2, the Db2 plan name must be bound and authorized. This process is done automatically during MainView configuration, or you can complete the process manually. Depending on your maintenance level, choose one of the following options:

  • PTF BPD4932 applied 

    1. Edit sample job DZALIAS to create aliases for two common repository objects.

      Example

      Sample ALIAS statement:

      CREATE ALIAS BDS1210D.BMC_BMCUTIL FOR BMCUTIL.BMC_BMCUTIL ;             
      CREATE ALIAS BDS1210D.BMC_BMCSYNC FOR BMCUTIL.BMC_BMCSYNC ;                                                                                   
    2. Edit sample job DZBIND for a Db2 target. The QUALIFIER value must match the DZALIAS job.

      Example

      Sample BIND statement:

      BIND PLAN(BMCMVDB2) QUALIFIER(BDS1210D) +                  
           PKLIST(BMCCOLLID.*,BMCSCC.*)      +                     
           DYNAMICRULES(BIND) ISO(CS) ACT(REP) 
    3. Repeat steps 1 and 2 for each Db2 target.
  • PTF BPD4932 not applied

    1. Edit sample job DZBIND for a Db2 target.

      Example

      Sample BIND statement:

      BIND PLAN(BMCMVDB2) PKLIST(BMCCOLLID.*,BMCSCC.*) +                     
           DYNAMICRULES(BIND) ISO(CS) ACT(REP) 
    2. Repeat step 1 for each Db2 target.

To authorize the Db2 Plan for each target Db2

For each target Db2, the Db2 Plan name must be authorized.

Execute the following SQL Statement for the Db2 Plan name:
GRANT EXECUTE ON PLAN planName TO PUBLIC;

Example

Sample GRANT statement:

GRANT EXECUTE ON PLAN BMCMVDB2 TO PUBLIC;


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments