Defining LU-to-LU Access Authority for LUs in a VTAM Generic Resource Group

If the LUs are members of a VTAM® generic resource group, you have a choice about defining APPCLU profiles for them:

You can define many APPCLU profiles, one for each LU that is a member of a VTAM generic resource group. These profiles have names that include local-lu-name, as described in Defining LU-to-LU Access Authority for a Specific LU.
You can define one APPCLU profile for each VTAM generic resource group, as described in this section. These profiles have names that include generic-resource-group-name, as shown in the examples to follow.
Migration Note: If you originally have APPCLU profiles for specific LUs (with local-lu-name in the profile names), and you later add APPCLU profiles for LUs that are in VTAM generic resource groups (with generic-resource-group-name in the profile names), you must delete the APPCLU profiles for specific LUs. If both kinds of APPCLU profiles exist, only the profiles for specific LUs are used.
To determine which specific LUs are in a VTAM generic resource group, issue the following command:
```
DISPLAY NET,ID=generic-resource-group-name                 
```
For example, if the VTAM generic resource group name is GENERNAM, issue:
```
d net,id=genernam                   
```
If the output is:
```
JOB    2  IST097I DISPLAY ACCEPTED                           
JOB    2  IST075I NAME = GENERNAM, TYPE = GENERIC RESOURCE   
 IST1359I MEMBER NAME        OWNING CP   SELECTABLE  APPC    
 IST1360I NETA.APPCAP06      SSCP2A         YES       YES    
 IST1360I NETA.APPCAP05      SSCP1A         YES       YES    
 IST1393I GENERIC RESOURCE NAME RESOLUTION EXIT IS ISTEXCGR  
 IST314I END                    
```
To cause VTAM to refresh updated RACF® profiles for generic name GENERNAM, issue MODIFY PROFILES,ID=APPCAP05 on the SSCP1A host where APPCAP05 resides, and MODIFY PROFILES,ID=APPCAP06 on the SSCP2A host where APPCAP06 resides.

A further consideration relates to network-qualified names:

If the LUs in the group are enabled to support network-qualified names (NQN is specified on each LUADD statement), the RDEFINE syntax is:
```
RDEFINE APPCLU lnetwork-id.generic-resource-group-name.pnetwork-id.partner-lu-name
        UACC(NONE)
```
If the LUs are not enabled to support network-qualified names (NONQN is specified on, or used as the default for, each LUADD statement), the RDEFINE syntax is:
```
RDEFINE APPCLU lnetwork-id.generic-resource-group-name.partner-lu-name UACC(NONE)
```

In the RDEFINE syntax, variables are defined as follows:

lnetwork-id or pnetwork-id

Is the network ID for the network on which the local LU or partner LU resides. This value is 1 through 8 characters, and matches the value coded for the VTAM start option NETID. RACF requires this value to be in discrete form (that is, the value cannot contain any wildcard characters).

generic-resource-group-name

Is the generic resource name associated with the LUs. This value is 1 through 8 characters, and matches the name coded on the GRNAME parameter of the LUADD statements for the LUs. RACF requires this value to be in discrete form (that is, the value cannot contain any wildcard characters).

partner-lu-name

Is one of the following:

The network name of the partner LU; that is, the 1- through 8-byte network-LU-name portion of their network-qualified names.
The generic resource name associated with the partner LU. This value is 1 through 8 characters.

RACF accepts this value in generic form (that is, the value can contain wildcard characters).

After creating or changing APPCLU profiles, make sure that the APPCLU class has been activated using the SETROPTS CLASSACT(APPCLU) command. To cause VTAM to refresh its in-storage copies of the updated RACF APPCLU profiles for the LUs in a generic resouce group, you must issue the MODIFY PROFILES command for each LU in the generic resource group. For example, if there are two LUs named APPCAP06 and APPCAP05 in generic resource group GENERNAM, issue MODIFY PROFILES,ID=APPCAP05 on the host where APPCAP05 resides, and MODIFY PROFILES,ID=APPCAP06 on the host where APPCAP06 resides.

If the partner LUs reside on different systems, you need a corresponding definition of the LUs on each partner's system. If RACF is installed on the partner system, define a corresponding APPCLU profile there, with the proper network ID and with the LU names in reverse order.