Using the originating member's LU name

Using the LU name of the originating member of the group as the generic LU name, and changing the originating member's LU name can be useful. This is particularly true when the originating member is already acting as a server for applications that will migrate to the data sharing group.

By configuring the group to use the originating member's LU name, you avoid needing to make extensive changes to the CDBs of Db2 for z/OS® requesters.

To change the LU name of the originating member of the group, you must change both the LU name value in the member's VTAM® APPL statement and the LUNAME value in the member's bootstrap data set (BSDS).

For example, assume that a group is formed whose originating member is already defined to the requesters that are shown in the following figure. Until you define a generic LU name when you enable group-generic access, requesters can access DB2A's data only through the originating member (LUDB2A). If the originating member is unable to handle requests, requesters are unable to access DB2A's data.

Figure 1. Example configuration before enabling group-generic access.. Access is limited to a single member of the data sharing group.
Begin figure description. Three DB2 subsystems form a data sharing group, but requesters are still configured to use the LU name of the originating member. End figure description.

As shown in the following figure, by enabling group-generic access and by using the LU name of the originating member as the generic LU name, requesters can, with minimal change, access DB2A's data from any member of the group.

Figure 2. Example configuration after enabling group-generic access.. All members of the group can potentially handle requests.
Begin figure description. The LU name of the originating member is the generic LU name for the data sharing group, so requesters are now able to access any member of the group. End figure description.