When implementing the generic resources function, the following considerations apply to the generic resources configuration:

• All generic resource members with the same generic resource name must reside within the same generic resource configuration. This means that all hosts where a generic resource member resides, and any resource selector nodes for that generic resource, must be in the same sysplex and be connected to the same coupling facility structure.
• LUs that initiate sessions using a generic resource name can be located outside the generic resource configuration that supports that generic resource name.
• Using two network node servers maintains generic resource resolution capability should one of the network nodes fail. A backup network node server outside the sysplex can be used. See the ENBCAST operand on the NETSRVR statement for the VTAMLST VBUILD TYPE=NETSRVR list in z/OS Communications Server: SNA Resource Definition Reference.
• Performance can be enhanced by placing generic resource members at end nodes in the generic resource configuration. This frees up network nodes to provide routing services.
• An application program can be known by only one generic resource name.
• Generic resource members using the same generic resource name must have the same NETID.
• Generic resource names must be unique within a single network. A generic resource name cannot be identical to:
  • A USERVAR
  • An alias name
  • A real LU name
  • An ACBNAME
• The generic resources function supports multiple copies of the same application program; however, VTAM® does not verify that each application program known by a generic resource name provides the same function.
• If your network has a security manager product installed, the security level for the generic resource name must be the same as the security level for all application programs that are using that generic resource name. The security level of the generic resource name is determined by the first generic resource member that associates itself with that generic resource name. If there is no security product, any application program residing on a VTAM that is connected to an MVS™ coupling facility can use any generic resource name.
• Using the generic resources function, VTAM distributes sessions across generic resource members rather than evenly across hosts. VTAM evaluates the current usage of each application program, regardless of the owning host. When activating generic resource members, consider the host capabilities. If VTAM A has twice the capability of VTAM B, VTAM A should support twice as many generic resource members.
• The MVS workload manager can also be used to balance allocation of sessions across hosts.