Configuring a Db2 requester to use group-generic access
You can update the CDB of a Db2 requester to use group-generic access.
Procedure
To enable group-generic access to a remote data sharing group:
- Identify the generic LU name of the remote group. Insert the group's generic LU name into the LUNAME column of the requester's SYSIBM.LUNAMES table. Do not include in this table the real LU names of the members of the group.
- Map the generic LU name to the group's Db2 location name. Insert the generic LU name and the Db2 location name of the group into the LINKNAME and LOCATION columns of the requester's SYSIBM.LOCATIONS table.
Example
The following example provides sample SQL statements for enabling group-generic 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 DB2R and a generic LU name of LUDSGA.
The following SQL statements update the CDB of a Db2 for z/OS® requester
to use group-generic access:
- This statement identifies the group's generic LU name:
INSERT INTO SYSIBM.LUNAMES (LUNAME, GENERIC) VALUES ('LUDSGA', 'Y'); - This statement maps the group's generic LU name to the group's Db2 location name.
INSERT INTO SYSIBM.LOCATIONS (LOCATION, LINKNAME) VALUES ('DB2R', 'LUDSGA');
The following table shows an example excerpt of the SYSIBM.LUNAMES table after the update.
| LUNAME | GENERIC |
|---|---|
| LUDSGA | Y |
The following table shows an example excerpt of the SYSIBM.LOCATIONS table after the update.
| LOCATION | LINKNAME | TPN |
|---|---|---|
| DB2R | LUDSGA |