z/OS MVS Planning: APPC/MVS Management
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Defining LUs to a Generic Resource Group

z/OS MVS Planning: APPC/MVS Management
SA23-1388-00

To register APPC/MVS LUs as members of a generic resource group, your installation must:

  1. Install VTAM® Version 4 Release 4 or later, and meet the requirements documented for generic resources in z/OS Communications Server: SNA Network Implementation Guide.

    If an earlier level of VTAM is installed, and a generic resource name is specified on the LUADD statement for an LU, APPC/MVS activates the LU, but without using the generic resource name. In this case, Allocate requests specifying the generic resource name will fail.

  2. Select an appropriate generic resource name. Refer to The Simplest Approach for guidelines for selecting names.
  3. Through the appropriate commands for the installation's security product, protect LUs in a generic resource group by:
    • Defining LU-to-LU access authority (APPCLU profiles)
    • Defining which user IDs are authorized to allocate conversations with those LUs (APPL profiles)
    • Prohibiting non-APF-authorized programs from registering with a generic resource name (VTAMAPPL profiles).

    If the LUs in the same generic resource group reside on different MVS systems, some of these commands must be entered on each system on which the LU members reside. You cannot specify generic resource names on any other security profiles. Refer to the appropriate sections of Setting up Network Security for details about using RACF® commands to protect LUs in a generic resource group.

  4. Through an APPCPMxx parmlib member, use an LUDEL statement to delete each existing, active LU that is to register with a generic resource name.
  5. Also through an APPCPMxx member, use an LUADD statement with the GRNAME parameter to define each LU and associate it with a generic resource name.
After these requirements are met, the installation must complete the following steps, if the generic resource name chosen was not the specific name of an existing LU. Until these steps are completed, the installation cannot benefit from using generic resource names for APPC/MVS LUs.
  • Replace specific partner LU names with a generic resource name in side information. Do not use a generic resource name in side information entries that APPC/MVS servers use, or an error results.
  • Modify existing, or coding new, TPs to specify the generic resource name for the partner LU on calls to the CPI-C CMSPLN verb, or any version of the APPC/MVS Allocate callable service.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014