Rules checklist

Here is a checklist of the rules that govern CICS® use of the z/OS® Communications Server generic resources function.

  • Generic resource names must be unique in the network.
  • A CICS region that is a member of a generic resource can have only one generic resource name and only one applid.
  • A generic resource name cannot be the same as a z/OS Communications Server applid in the network.
  • Within a generic resource, member names only must be used. There must be no definitions in any of the members of the generic resource for the generic resource name.
  • Non-LU6 devices that require sequence number resynchronization cannot log on using the generic resource name. They must use the applid and therefore cannot take advantage of session balancing.
  • APPC connections to a generic resource that are initiated by the partner (that is, on which the non-generic resource sends the first bind) can log on using a member name.
  • For LU6.1 connections initiated by a generic resource member, the partner must know the member by its generic resource name.

    Therefore, you are strongly recommended not to try to access the same LU6.1 partner from more than one member of a generic resource.

  • For APPC connections initiated by a generic resource member, where the partner is not itself a member of a CICS Transaction Server for z/OS generic resource, the partner must know the member TOR by its generic resource name.

    Therefore, you are strongly recommended not to try to access such partners from more than one member of a generic resource.

  • A system cannot statically define both an APPC generic resource name connection and an APPC member name connection to the same generic resource. (Generic resource name connections and member name connections are described in Establishing connections between CICS TS for z/OS generic resources.)

    Furthermore, all members of a generic resource must choose the same method. That is (for statically-defined APPC connections to a partner generic resource), they must all use member name connections or all use generic resource name connections.