Defining LUs to Support Network-Qualified Names

When you decide to allow APPC/MVS LUs to support network-qualified names, make sure you have VTAM® V4R4 installed, and do the following:

1. If your installation uses a security product to define LU-to-LU access authority, changes are required for those security profiles. For example, if a RACF® APPCLU class defines LU-to-LU access authority, make sure existing or new APPCLU profiles use the network-qualified name for both the local LU and partner LU names. In other words, for each LU to be enabled to use network-qualified names, all APPCLU profiles currently defined for that LU in the form "local-LU-network-id.local-LU-name.partner-LU-name" must have a corresponding profile in the form "local-LU-network-id.local-LU-name.partner-LU-network-id.partner-LU-name").

   You cannot specify network-qualified LU names on any other type of RACF profiles. For more information about APPCLU changes, see Defining LU-to-LU Access Authority with RACF APPCLU Profiles.

2. Through an APPCPMxx parmlib member, use an LUDEL statement to delete each existing, active LU that is to support network-qualified names.
3. Also through an APPCPMxx member, use an LUADD statement with the NQN parameter for each LU that is to be enabled to support network-qualified LU names for its partner LUs.

Changes to existing TPs are not necessary; however, consider notifying your installation's application programmers of the change in APPC/MVS processing of network-qualified partner LU names, so they can determine what changes, if any, might be necessary for the TPs they design and maintain.