Configuring a Db2 requester to use group access

You can update the CDB of a Db2 for z/OS® requester to use group access.

About this task

Recall that DVIPA network addressing uses dynamic virtual IP addresses (DVIPAs).

Procedure

To enable group access to a remote data sharing group:

  1. Identify the Db2 location name of the remote group. Insert the group's Db2 location name into the LOCATION column of the requester's SYSIBM.LOCATIONS table.
  2. Identify the DVIPA or domain name of the remote group, and specify the security definitions for conversations with group members. Insert the group's DVIPA or domain name into the IPADDR column of the requester's SYSIBM.IPNAMES table.
  3. Map the Db2 location name of the remote group to its DVIPA or domain name.

    If you use RACF® PassTickets, specify the group's generic LU name or IPNAME value as the value of the LINKNAME columns.

    Insert the same link name into the LINKNAME columns of the requester's SYSIBM.LOCATIONS and SYSIBM.IPNAMES tables. Be sure to update only those rows that are associated with the remote group.

Example

The following example provides sample SQL statements for enabling group access that uses DVIPA network addressing. It also shows the results of those statements in the form of table excerpts. This example assumes that a remote data sharing group exists with a group location name of DB2A and a group DVIPA of Vx.

The following SQL statements update the CDB of a Db2 for z/OS requester to use group access (DVIPA network addressing):
  1. This statement identifies the Db2 location name of the remote group:
    Begin general-use programming interface information.
    INSERT INTO SYSIBM.LOCATIONS (LOCATION, PORT)
      VALUES ('DB2A', '446');
    End general-use programming interface information.
  2. This statement identifies the DVIPA of the remote group and specifies security definitions for conversations with the group's members:
    Begin general-use programming interface information.
    INSERT INTO SYSIBM.IPNAMES (SECURITY_OUT, USERNAMES, IPADDR)
      VALUES ('A', ' ', 'Vx');
    End general-use programming interface information.
  3. These statements map the Db2 location name of the remote group to the DVIPA of the remote group:
    Begin general-use programming interface information.
    UPDATE SYSIBM.LOCATIONS
               SET LINKNAME='DB2ALINK'
               WHERE LOCATION='DB2A';
    UPDATE SYSIBM.IPNAMES
               SET LINKNAME='DB2ALINK'
               WHERE IPADDR='Vx';
    End general-use programming interface information.

The following table shows an example excerpt of the SYSIBM.LOCATIONS table after the update.

Table 1. Db2 location name of a remote data sharing group in a Db2 requester's SYSIBM.LOCATIONS table. Not all columns are shown.
LOCATION LINKNAME PORT
DB2A DB2ALINK 446

The following table shows an example excerpt of the SYSIBM.IPNAMES table after the update.

Table 2. DVIPA of a remote data sharing group in a Db2 requester's SYSIBM.IPNAMES table. Not all columns are shown.
LINKNAME SECURITY_OUT USERNAMES IPADDR
DB2ALINK A   Vx
The following SQL statement connects to the remote group:
CONNECT TO DB2A;