Data Sharing Requirements

Use this procedure to set up a data sharing environment for the
Database Management Solutions for Db2
.
dm20
To set up a data sharing environment for the
Database Management Solutions for Db2
, address the data sharing requirements in the following procedure. With Db2 data sharing, applications that run on more than one Db2 subsystem can read and write to the same set of data concurrently. Db2 subsystems that share data must belong to a Db2 data sharing group that you identify in the SETUP global parmlib member. The SETUP global parmlib member defines global and remote z/OS and Db2 subsystem options for the
Database Management Solutions for Db2
.
Follow these steps:
  1. Specify the following values in the SETUP member for each Db2 subsystem that is a part of a data sharing group:
    For more information about editing the SETUP global parmlib member, see Create a SETUP Global Parmlib Member. We recommend that you create one SETUP member for
    each
    LPAR.
    • Db2 Subsystem (SSID)
    • Db2 Version (SSIDVERF/SSIDVERC or SSIDVER/SSIDMODE)
    • VSAM Catalog Alias (CATALIAS)
      Use the same value for the VSAM Catalog Alias (CATALIAS) parameter for each member in the data sharing group. This value identifies the VCAT high-level qualifier for the Db2 subsystem and corresponds to the group CATALIAS value.
    • Db2 Load Libraries (LOADLIBS)
      These libraries must be APF-authorized. READ access is required for product users.
    • BSDS01 Dataset and BSDS02 Dataset (BSDS)
      Use unique names for the bootstrap data sets (BSDS01 Dataset and BSDS02 Dataset--BSDS) for each member subsystem.
    • Data Sharing Group Name (DSGROUP)
    For these values, note the following considerations:
    • When using separate SETUP members for each LPAR, define
      all
      Db2 subsystem member names (SSID) and data sharing group names (DSGROUP) in
      each
      SETUP member so that the
      Database Management Solutions for Db2
      can access information about all the subsystems within the group from each LPAR.
    • In coexistence mode (Db2 11 NFM with V12R1M100), the group attach name or subgroup attachment name definition must point to the highest Db2 version. It must also include a concatenation of load libraries from all releases in the data sharing group in the Db2 load libraries (LOADLIBS) parameter. Define
      all
      the Db2 subsystem member names, group attach names, and subgroup attachment names with the data sharing group name in
      each
      SETUPxx parmlib member to ensure that the products are able to access information from all the Db2 subsystems within the data sharing group.
      For example, you have a data sharing group that is named DSNDR0G with a group attach name of DR0G and three Db2 subsystems (DR1G, DR2G, and DR3G). DR1G is a Db2 12 subsystem. DR2G and DR3G are Db2 11 NFM subsystems. Use the post-install tailoring panels to complete the following tasks:
      • Define DR0G as a Db2 subsystem (SSID) with function level V12R1M100 (SSIDVERF), catalog level V12R1M500 (SSIDVERC), Db2 12 and 11 load libraries (LOADLIBS), and data sharing group DSNDR0G (DSGROUP).
      • Define the DR1G subsystem (SSID) with function level V12R1M100 (SSIDVERF), catalog level V12R1M500 (SSIDVERC), Db2 12 load library (LOADLIBS), and data sharing group DSNDR0G (DSGROUP).
      • Define the DR2G subsystem (SSID) with Db2 version 11 (SSIDVER), Db2 11 NFM (SSIDMODE), Db2 11 load library (LOADLIBS), and data sharing group DSNDR0G (DSGROUP).
      • Define the DR3G subsystem (SSID) with Db2 version 11 (SSIDVER), Db2 11 NFM (SSIDMODE), Db2 11 load library (LOADLIBS), and data sharing group DSNDR0G (DSGROUP).
      As a result, the following entries are defined in the SETUPxx member:
      SSID (DR0G) SSIDVERF (V12R1M100) SSIDVERC (V12R1M500) ... LOADLIBS (DB2.DB212.SDSNLOAD ==> Db2 12 load library DB2.DB211.SDSNLOAD ==> Db2 11 load library) DSGROUP (DSNDR0G) ... SSID (DR1G) SSIDVERF (V12R1M100) SSIDVERC (V12R1M500) ... LOADLIBS (DB2.DB212.SDSNLOAD ==> Db2 12 load library) DSGROUP (DSNDR0G) ... SSID (DR2G) SSIDVER (11) SSIDMODE (NFM) ... LOADLIBS (DB2.DB211.SDSNLOAD ==> Db2 11 load library) DSGROUP (DSNDR0G) ... SSID (DR3G) SSIDVER (11) SSIDMODE (NFM) ... LOADLIBS (DB2.DB211.SDSNLOAD ==> Db2 11 load library) DSGROUP (DSNDR0G)
    • As a member of the data sharing group, the following group-wide options can be edited simultaneously in SETUP instead of editing each member individually:
      • Db2 12 function level and catalog level or Db2 11 version and mode
      • VSAM catalog alias
      • STOGROUP name and volume
      • Database name
      • BIND owner
      • Tablespace BUFFERPOOL 4 KB, 8 KB, 16 KB, and 32 KB
      • Index BUFFERPOOL
      • Define (TS and IX)
      • CLOSE (TS and IX)
      • COMPRESS TABLESPACE
  2. If the data sharing members are on different LPARs, set the XSYS parameter to Y in the Xmanager started task JCL on the affected LPARs.
    When XSYS=Y, we recommend that the involved Xmanagers use the same load library so that they are at the same maintenance level. If the Xmanagers are at different maintenance levels, you must access data from the local Xmanager. The maintenance mismatch can potentially result in the display of user values that are inaccurate, an unexpected user ABEND, or both.
    For more information about setting this parameter, see Customize Xmanager.
  3. If
    MIM
    is used to ensure cross-system integrity of objects across all members of the sysplex, enable the QNAME CADB2 to propagate cross-system enqueues. If IBM Global Resource Serialization (GRS) is used instead, no further action is required. For more information, see Global Resource Sharing.
  4. Execute the Bind Product Packages and Plans task on the group member that has the lowest Db2 version. A package that is bound on a higher version can result in SQL errors when executing that same package on the lower versions.
    For more information about binding the product packages and plans, and automatic rebinds in a coexisting data sharing group, review the IBM documentation about mixed releases in a data sharing group.
  5. Review your product-specific documentation for data sharing implementation requirements. For example,
    SYSVIEW for Db2
    requires each member of the Db2 data sharing group to be monitored by its own data collector. In
    Subsystem Analyzer
    , you must create a subsystem-specific datastore using the same high-level and datastore name as the other datastore for this group, and then start data collection for the new member. For more information, see your Product Documentation.