Configuring a Db2 requester to use member-routing access

You can update the CDB of a Db2 requester to use member-routing access.

Procedure

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

Insert the group's location name into the LOCATION column of the requester's SYSIBM.LOCATIONS table.
If you use RACF® PassTickets, define only one location row.
Map the location to the security and mode requirements for conversations with each set of members.
Insert the same link name into the LINKNAME column of the requester's SYSIBM.LOCATIONS and SYSIBM.LUNAMES tables. Insert the appropriate security and mode requirements for your site.

If you use RACF PassTickets, specify the group's generic LU name as the value of the LINKNAME columns.
Map the location to the LU names of the data sharing members to be accessed.
For each member, insert the LU name of the member into the LUNAME column of the requester's SYSIBM.LULIST table.

Example

The following example provides sample SQL statements for enabling member-routing access. 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 a generic LU name of LUDB2A, and three members with names LUDB2AR, LUDB2B, and LUDB2C. Only members DB2B and DB2C with LU names LUDB2B and LUDB2C, respectively, are to be accessed.

The following SQL statements update the CDB of a Db2 for z/OS® requester to use member-routing access:

This statement defines the location and uses the group generic LU name to identify different sets of members:
```
INSERT INTO SYSIBM.LOCATIONS (LOCATION, LINKNAME)
  VALUES ('DB2A', 'LUDB2A');
```
This statement defines the location's security and mode requirements for conversations with the members:
```
INSERT INTO SYSIBM.LUNAMES (LUNAME)
   VALUES ('LUDB2A');
```

These statements map the location name to the two members of the group to be accessed:

Begin general-use programming interface information.

INSERT INTO SYSIBM.LULIST (LINKNAME, LUNAME)
   VALUES ('LUDB2A', 'LUDB2B');

INSERT INTO SYSIBM.LULIST (LINKNAME, LUNAME)
   VALUES ('LUDB2A', 'LUDB2C');

End general-use programming interface information.

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	TPN
DB2A	LUDB2A

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

Table 2. Location aliases in a Db2 requester's SYSIBM.LUNAMES table. Not all columns are shown.
LUNAME	GENERIC
LUDB2A

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

Table 3. LU names of the members that are associated with each location alias in a Db2 requester's SYSIBM.LULIST table. Not all columns are shown.
LINKNAME	LUNAME
LUDB2A	LUDB2B
LUDB2A	LUDB2C