Configuring a Db2 requester to use member-specific access

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

Before you begin

You should disable sysplex support when configuring a Db2 requester for member-specific access. If you do not disable sysplex support, Db2 Connect uses DRDA workload balancing by default to allocate requests among the members of the group. The database directory should use the member IP address.

Procedure

To enable member-specific access to a remote data sharing group:

Define one or more location aliases that identify different sets of members. Insert each location alias into the LOCATION column of the requester's SYSIBM.LOCATIONS table.
Map each location alias to the security definitions for conversations with each set of members.
If you use RACF® PassTickets, then all LOCATION aliases must eventually refer to a single common IPNAMES row whose LINKNAME value must match the remote group's generic LU name or IPNAME value. The IPADDR value in the IPNAMES row must eventually refer to the group distributing DVIPA of the data sharing group.

Insert the same link names into the LINKNAME columns of the requester's SYSIBM.LOCATIONS and SYSIBM.IPNAMES tables. In the SYSIBM.IPNAMES table, insert the appropriate security definitions for your site, and leave the IPADDR column blank.
Map each location alias to the domain names or DVIPAs of the data sharing members in that set.
For each member of a set, insert the domain name or DVIPA of the member into the IPADDR column of the requester's SYSIBM.IPLIST table.
Define location aliases on the server (remote data sharing group).
For each location alias on the requester's side, you must define a location alias at the server by using the DSNJU003 (change log inventory) utility.

Example

The following example provides sample SQL statements for enabling member-specific 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 Db2 location name of DB2A and three members with DVIPAs V1, V2, and V3. Location aliases that are to be defined are DB2B (with members V1 and V2), DB2C (with members V2 and V3), and DB2D (with member V1).

The following SQL statements update the CDB of a Db2 for z/OS requester to use member-specific access (DVIPA network addressing):

These statements define location aliases that identify different sets of members:

Begin general-use programming interface information.

INSERT INTO SYSIBM.LOCATIONS (LOCATION, PORT)
  VALUES ('DB2B', '446');

INSERT INTO SYSIBM.LOCATIONS (LOCATION, PORT)
  VALUES ('DB2C', '446');

INSERT INTO SYSIBM.LOCATIONS (LOCATION, PORT)
  VALUES ('DB2D', '446');

End general-use programming interface information.

These statements map each location alias to the security definitions for conversations with each set of members:

UPDATE SYSIBM.LOCATIONS
           SET LINKNAME='ALIASB'
           WHERE LOCATION='DB2B';

INSERT INTO SYSIBM.IPNAMES (LINKNAME)
           VALUES ('ALIASB')

UPDATE SYSIBM.LOCATIONS
           SET LINKNAME='ALIASC'
           WHERE LOCATION='DB2C';

INSERT INTO SYSIBM.IPNAMES (LINKNAME)
           VALUES ('ALIASC')

UPDATE SYSIBM.LOCATIONS
           SET LINKNAME='ALIASD'
           WHERE LOCATION='DB2D';

INSERT INTO SYSIBM.IPNAMES (LINKNAME)
           VALUES ('ALIASD')

These statements map each location alias to the DVIPAs of the data sharing members in that set:

INSERT INTO SYSIBM.IPLIST (LINKNAME, IPADDR)
           VALUES ('ALIASB', 'V1')

INSERT INTO SYSIBM.IPLIST (LINKNAME, IPADDR)
           VALUES ('ALIASB', 'V2')

INSERT INTO SYSIBM.IPLIST (LINKNAME, IPADDR)
           VALUES ('ALIASC', 'V2')

INSERT INTO SYSIBM.IPLIST (LINKNAME, IPADDR)
           VALUES ('ALIASC', 'V3')

INSERT INTO SYSIBM.IPLIST (LINKNAME, IPADDR)
           VALUES ('ALIASD', 'V1')

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

Table 1. Location aliases for a remote data sharing group in a Db2 requester's SYSIBM.LOCATIONS table. Not all columns are shown.
LOCATION	LINKNAME	PORT
DB2B	ALIASB	446
DB2C	ALIASC	446
DB2D	ALIASD	446

Location aliases are not associated with the DVIPA of a remote data sharing group in a Db2 requester's SYSIBM.IPNAMES table. The following table shows an example excerpt of the SYSIBM.IPNAMES table after the update.

Table 2. Excerpt of the SYSIBM.IPNAMES table. Not all columns are shown.
LINKNAME	IPADDR
ALIASB
ALIASC
ALIASD

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

Table 3. DVIPAs of the members that are associated with each location alias in a Db2 requester's SYSIBM.IPLIST table. Not all columns are shown.
LINKNAME	IPADDR
ALIASB	V1
ALIASB	V2
ALIASC	V2
ALIASC	V3
ALIASD	V1

The following SQL statement connects to the remote group using a location alias:

CONNECT TO DB2C;