Defining connections

When you define a connection to a generic resource, you have two possibilities for the NETNAME attribute of the CONNECTION resource.

About this task

  1. Use the name (applid) of the generic resource member. This type of connection is known as a member name connection.
  2. Use the name of the generic resource. This type of connection is known as a generic resource name connection.
It is important that you make the correct choice when you define connections to a generic resource:
  • When CICS® initiates a connection using a member name definition, z/OS® Communications Server establishes a session with the named member.
  • When CICS initiates a connection using a generic resource name connection, z/OS Communications Server establishes a connection to one of the members of the generic resource. Which member it chooses depends upon whether any affinities exist, and upon z/OS Communications Server's session-balancing algorithms.

When a CICS Transaction Server for z/OS generic resource member sends a BIND request on a connection, the request contains the generic resource name and the member name of the sender. If the partner is also a CICS TS for z/OS generic resource, it can distinguish both names. Other CICS systems take the generic resource name from the bind, and attempt to match it with a connection definition.

It follows that the only time an LUtype 6 which is not itself a member of a CICS TS for z/OS generic resource can successfully use a member name to connect to a generic resource is when the generic resource member will never initiate any sessions. This is an unusual situation, and therefore a connection from a system that is not a CICS TS for z/OS generic resource member to a generic resource should use the generic resource name.



dfht1c0099.html | Timestamp icon Last updated: Sunday, 4 June 2017