IST1706I
PARTNER NAME GENERIC RESOURCE MEMBER ATTRIBUTES

Explanation

This message is the first in a group of messages that VTAM® issues in response to DISPLAY GRAFFIN command. A complete description of the message group follows.
IST350I DISPLAY TYPE = GENERIC AFFINITY
IST1706I PARTNER NAME       GENERIC RESOURCE    MEMBER     ATTRIBUTES
IST1707I partner_name       generic_name        appl_name  attributes
 .
IST314I END
IST1706I
  • This message is a header message for information displayed in message IST1707I.
IST1707I
  • partner_name is the network qualified partner LU name.
  • generic_name is the generic resource name of appl_name.
  • appl_name is the application to which the partner LU has an affinity.
  • attributes describes the attributes of the session the affinity represents. attributes is an eight-byte character string that has the following meaning:
    1. The first character is either P to indicate that the generic name has been resolved but the session is pending activation, or a hyphen (-) otherwise.
    2. The second character is either V to indicate that the affinity will be cleaned up by VTAM when the session is terminated, or A to indicate that the application is responsible for deleting the affinity. Application owned affinities might not be deleted when the session is terminated. An application owned affinity will also be deleted when the application is terminated, if the affinity is not persistent (see the fourth aattribute character)
    3. The third character is either G to indicate that the session was started using the generic name, or A to indicate that the session was started using the application name.
    4. The fourth character is either 6 to indicate the affinity will persist after application termination, or a hyphen (-) otherwise. If the affinity will persist it is the responsibility of the application to delete the affinity. An affinity can persist for one of the following reasons:
      • This is an LU6.1 session.
      • This is an LU6.2 SYNCPT session.
      • The application used the SETLOGON GNAMEADD AFFIN=APPL API command to request ownership of all affinities.
      • The application used the LUAFFIN=APPL parameter on the appropriate RAPI or APPCCMD API command to request ownership of this affinity. LUAFFIN=NOTAPPL will override the other three reasons.
    5. The fifth character is either M to indicate that the generic resource application also supports MNPS, or a hyphen (-) otherwise. This affinity will not be deleted in a MNPS recovery scenario unless the recovery does not occur before the PSTIMER expires. See the z/OS Communications Server: SNA Network Implementation Guide for more information about MNPS.
    6. The sixth character indicates who created the affinity. The value will be one of the following:
      V
      to indicate that VTAM resolved the generic name to an application name based on session count or by setting up a session directly to a member of a generic resource group.
      W
      to indicate that the WorkLoad Manager resolved the generic name to an application name based on system workload.
      X
      to indicate that the Generic Resource Resolution Exit resolved the generic name to an application name.
      S
      to indicate that the original resolver of the name is not known. This is most probably caused by a previous search request that did not cause an affinity to be created at the time of resolution. This may also occur due to such things as VTAM losing connectivity to the coupling facility, VTAM being re-IPL'ed, a structure failure of the generic resource coupling facility structure, or following an MNPS recovery.
    7. The seventh character is either L to indicate that this affinity will be used for up to 10 minutes after the last session between the session partners ended, or a hyphen (-) otherwise. An affinity might used for this extended time if either of the following is true:
      • An LU6.2session is established without SYNCPT or Limited Resource.
      • An LU6.2 session is established, but the application specified LUAFFIN=NOTAPPL on the NIB for the OPNDST or OPNSEC.
    8. The eight character is not used and is always a hyphen (-).

System action

Processing continues.

Operator response

None.

System programmer response

None.

Routing code

2

Descriptor code

5