IST2311I
TDU DIAGNOSTIC INFORMATION FOR TG: TGN = tg_number

Explanation

VTAM® issues this message as part of a group of messages in response to a DISPLAY TOPO,LIST=TDUDIAG,ORIG=origin_node,DEST=dest_node,TGN=tg_number. A complete description of the message group follows:
 IST350I DISPLAY TYPE = TDU DIAGNOSTICS
 IST2311I TDU DIAGNOSTIC INFORMATION FOR TG: TGN = tg_number
 IST2256I ORIG = origin_node - DEST = dest_node
 IST2312I CURRENT RSN = decimal_rsn - HEX RSN = hex_rsn
[IST2355I TDUDIAG THRESHOLD REACHED ON date AT time]
[IST2277I POSSIBLE CORRUPTION OF TOPOLOGY CONTROL VECTORS DETECTED]
 IST924I -------------------------------------------------------------
 IST2275I TDU INFORMATION SINCE LAST RESET ON date AT time
[IST1769I LAST TDU RECEIVED - date time FROM adjacent_cp]
[IST1784I LAST TDU RECEIVED - NONE]
[IST2281I LAST TDU SENT - date time]
[IST2315I LAST TDU SENT - NONE]
 IST2282I TDU COUNTS:
 IST2352I   SENT     = sent         RECEIVED = received
 IST2353I   ACCEPTED = accepted     REJECTED = rejected
 IST2354I   IGNORED  = ignored
 IST2313I TOTAL RSN UPDATES BY LOCAL HOST NODE = rsn_count
[IST2283I NO TDUDIAG RSN UPDATES EXIST]
[IST924I -------------------------------------------------------------]
[IST2294I TDUDIAG RSN UPDATES:]
[IST2295I                    TIME      HEX RSN   HEX RSN]
[IST2296I CP NAME            UPDATED   BEFORE    AFTER     REASON]
[IST2297I cp_name            time      befor_rsn after_rsn reason]
[IST2300I   RECEIVED FROM: adjacent_node]
⋮
[IST2314I num OF total RSN UPDATES DISPLAYED]
 IST314I END
IST350I
  • This message identifies the type of information in the display and is always TDU DIAGNOSTICS for this message group.
IST1769I
  • The date and time values specify when the last topology database update (TDU) was received for this TG. See DATE and TIME formats for information about the date and time values.
  • adjacent_cp is the network-qualified CP name of the adjacent node that sent the last TDU that was received.
IST1784I
  • This message is issued if no TDU about this resource was received.
IST2275I
  • The date and time values specify when all the TDU information and TDU counters were reset. The TDU information and TDU counters for a TG are reset every 24 hours when garbage collection runs, or when one of the following commands is entered:
    • DISPLAY NET,TOPO,LIST=TDUINFO,CLEAR=YES or a
    • DISPLAY NET,TOPO,LIST=TDUDIAG,CLEAR=YES
    • DISPLAY NET,TOPO,LIST=TDUDIAG,ORIG=cpname,DEST=destcpname,TGN=tgn,CLEAR=YES
    See DATE and TIME formats for information about the date and time values.
IST2277I
  • This message indicates that possible topology control vector corruption was detected for the TG. Because the topology control vectors contain the resource sequence number (RSN) for the node, which determines how a TDU is processed, it is possible that control vector corruption could cause a TDU war. The most probable cause of control vector corruption is a storage overlay.
IST2281I
  • The date and time values specify when the last topology database update (TDU) was sent for this TG. See DATE and TIME formats for information about the date and time values.
IST2282, IST2352I, IST2353I, IST2354I
  • This message subgroup displays topology database update (TDU) counts for this TG. A description of the message subgroup follows:
    IST2282I TDU COUNTS:
    IST2352I   SENT     = sent         RECEIVED = received
    IST2353I   ACCEPTED = accepted     REJECTED = rejected
    IST2354I   IGNORED  = ignored
  • IST2282I
    • This is a header message for topology database update (TDU) counts for this TG.
IST2313I
  • This message displays information about resource sequence number (RSN) updates made for this TG.
  • rsn_count is the total number of times that the host node has updated the RSN for this TG since the last time that the TDU counts were reset.
IST2315I
  • This message is issued if no TDU about this resource was sent.
  • IST2352I
    • This message displays the counts of TDUs that were sent and received for this TG
    • sent is the number of TDUs about the TG that were sent since the last time that the TDU counts were reset.
    • received is the number of TDUs about the TG that were received since the last time that the TDU counts were reset.
  • IST2353I
    • This message displays counts of TDUs that were accepted and rejected for this TG.
    • accepted is the number of TDUs about the TG that were accepted since the last time that the TDU counts were reset. The TDUs contain new information about the node and the topology database was updated.
    • rejected is the number of TDUs about the node that were rejected since the last time that the TDU counts were reset. The TDUs were rejected because the TDUs contain outdated information about the node. TDUs that are built from the local topology database information for the node were sent as corrections.
  • IST2354I
    • This message displays counts of TDUs ignored for this TG.
    • ignored is the number of TDUs about the TG that were ignored since the last time that TDU counts were reset. The TDUs were discarded because the TDUs contained no new information.
IST2283I
  • This message indicates that no resource sequence number (RSN) updates exist for this TG.
IST2294I, IST2295I, IST2296I, IST2297I, IST2300I, IST2314I
  • This message subgroup displays information about the TDUDIAG resource sequence number (RSN) update information that was saved in the topology database for this TG. A description of the message subgroup follows:
    IST2294I TDUDIAG RSN UPDATES:
    IST2295I                    TIME      HEX RSN   HEX RSN
    IST2296I CP NAME            UPDATED   BEFORE    AFTER     REASON
    IST2297I cp_name            time      befor_rsn after_rsn reason
    IST2300I   RECEIVED FROM: adjacent_node
    IST2314I num OF total RSN UPDATES DISPLAYED
  • IST2294I
    • This is a header message for information about the TDUDIAG resource sequence number (RSN) update information that was saved in the topology database for this TG.
  • IST2295I, IST2296I
    • These are header messages for the information that is displayed in the IST2297I and IST2300I subgroup messages that follow.
  • IST2297I
    • One IST2297I message is issued for each TDUDIAG RSN update that was saved in the topology database for this TG. The first IST2297I in this message subgroup describes the most recent TDUDIAG RSN update.
    • The NUM keyword can be specified on the DISPLAY command to limit the number of topology resources that are displayed. The default value is 10 and the maximum value is 50. If the number of TDUDIAG RSN updates that are saved for this TG is smaller than the number of RSN updates that were requested on the display command, the number of IST2297I messages that are displayed in this subgroup can be smaller than the value that was specified in the NUM keyword.
    • cp_name is the network-qualified CP name of the network node that updated the RSN for this TG.
    • time is the time when the TDUDIAG RSN update for this TG was saved in the topology database. See DATE and TIME formats for information about the date and time values.
    • before_rsn is the RSN for the TG before the RSN update. It is expressed in hexadecimal.
    • after_rsn is the RSN for the TG after the RSN update. It is expressed in hexadecimal.
    • reason is the reason that the RSN was updated for this TG. Possible values are:
      ****NA****
      RSN update reason is unknown.
      COMMAND
      The RSN was updated for the TG as the result of a command other than those specifically listed.
      CW ACTIVE
      The RSN was updated when the contention winner CP-CP session was activated over the TG.
      CW INACTIVE
      The RSN was updated when the contention winner CP-CP session over the TG was deactivated.
      F CLRUNRCH
      The RSN was updated when a MODIFY TOPO,FUNCTION=CLRUNRCH,SCOPE=NETWORK command was entered to clear unreachable partner records.
      F DELETE
      The RSN was updated when a MODIFY TOPO,FUNCTION=DELETE,SCOPE=NETWORK command was entered to delete the TG.
      F NORMAL
      The RSN was updated when a MODIFY TOPO,FUNCTION=NORMAL,SCOPE=NETWORK command was entered to change the TG status from quiesced to normal.
      F QUIESCE
      The RSN was updated when a MODIFY TOPO,FUNCTION=QUIESCE,SCOPE=NETWORK command was entered to change the TG status to quiesced.
      GARBAGE
      The RSN was updated during topology garbage collection to inform the rest of the network of the impending TG deletion.
      TDU EN TG
      The RSN was updated when an input TDU was received for a TG owned by the receiving host node because the partner node changed from an NN to an EN. The host node sets the TG to an INOP status and broadcasts it to all adjacent nodes to prevent the use of the endpoint TG for intermediate routing.
      TDU EQUAL
      The RSN was updated when an input TDU was received for the TG with a RSN equal to the RSN in the topology database, but with inconsistent information included.
      TDU GREATER
      The RSN was updated when an input TDU was received for the TG owned by the receiving host node with a RSN greater than the RSN in the topology database. Because the TG's owning node maintains the RSN, this is inconsistent information.
      TDU ISL/BEX
      The RSN was updated when an input TDU was received for an intersubnet link (ISL) or branch extender (BEX) TG that is owned by the receiving host node and the input status of the TG was rejected for one of the following reasons:
      • The input TDU has the garbage collection indicator (GCI) on, but the TG in the local database is operational and its RSN has an even value.
      • The input status of the TG is not quiesced; an ISL or BEX TG is always broadcast to non-owning nodes as quiesced.

      The host node broadcasts the correct status of the TG to all adjacent nodes.

      TDU NEW TG
      The RSN was updated when an input TDU was received for a TG that is owned by the receiving host node, but that TG does not exist. The host node broadcasts the TG with an INOP status to all adjacent nodes to prevent the use of the non-existent TG.
      TDU VECTOR
      The RSN for the TG was updated from an input TDU vector.
      TG ACTIVE
      The RSN was updated when the TG was activated.
      TG CREATE
      The RSN was set to the start RSN when the TG record was created at TG activation.
      TG INACTIVE
      The RSN was updated when the TG was deactivated.
      TG LOCAL
      The RSN was updated for a TG that originates in the host node, with a destination partner node that changed its node type from NN to EN.
      TG REVERSE
      The RSN was updated for a TG that originates in a partner node that changed its node type from NN to EN. This is the reverse TG of a TG that originates in the host node.
      WEEKLY
      The RSN for the TG was updated during the weekly broadcast of the host node and all TGs owned by the host node.
  • IST2300I
    • One IST2300I message is issued following each IST2297I message that describes a TDUDIAG RSN update for the TG that was made by a node other than the host node.
    • adjacent_node is the network-qualified CP name of the adjacent node that sent the input TDU that contains the TDUDIAG RSN update information. This might not be the same node that updated the RSN.

    Result: Only the first copy of a TDUDIAG RSN update that was made by a node other than the host node is displayed. Duplicate RSN updates received from other adjacent nodes are not saved unless the host node must update the RSN in response to the input TDU information.

  • IST2314I
    • This message displays the number of TDUDIAG RSN updates that are displayed in this message subgroup.
    • num is the total number of IST2297I messages that are displayed in the message subgroup.
    • total is the total number of TDUDIAG RSN updates that currently exist for this node.
IST2311I, IST2256I
  • This is a header message subgroup for the topology database update (TDU) diagnostic information for the TG. A description of the message subgroup follows:
    IST2311I TDU DIAGNOSTIC INFORMATION FOR TG: TGN = tg_number
    IST2256I ORIG = origin_node - DEST = dest_node
  • IST2311I
    • This header message displays the TG number for the TG.
    • tg_number is the TG number of the TG.
  • IST2256I
    • This header message displays the origin and destination of the TG.
    • origin_node is the network-qualified CP name of the origin node of the TG.
    • dest_node is the network-qualified CP name of the destination node of the TG.
IST2312I
  • This message displays the current resource sequence number (RSN) for this TG.
  • decimal_rsn is the current RSN in decimal format.
  • hex_rsn is the current RSN in hexadecimal format.
IST2355I

System action

Processing continues.

Operator response

If you are displaying TDU diagnostic information because of performance degradation of the APPN network, use the information about display TDU information in z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures , and do the following:

  1. If the DISPLAY TOPO,LIST=TDUINFO commands indicate that this TG has excessive TDU activity, and TDUDIAG RSN update information is saved for the TG in the topology database, this display might provide information about the network nodes that are causing the performance degradation (TDU war).
  2. If you can identify the network nodes that are involved in the TDU war, bring down the CP-CP sessions from one of the network nodes involved to all other network nodes in the network or subnetwork.
  3. If you cannot stop the TDU war, save the system log and request a dump for problem determination. Contact the system programmer.

System programmer response

Take the following actions:
  • If the operator provides output from the DISPLAY TOPO,LIST=TDUINFO or DISPLAY TOPO,LIST=TDUDIAG, use the display TDU information in z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures to learn how to diagnose a TDU war. If possible, identify the topology resource that is in contention and the network nodes that are involved in the TDU war.
  • If you have access to IBMLink, search for known problems in this area. If no applicable matches are found, report the problem to IBM® by using the Electronic Technical Report (ETR) option on IBMLink.
  • If you do not have access to IBMLink, report the problem to the IBM software support center.

User response

Not applicable.

Problem determination

See the system programmer response.

Source

z/OS® Communications Server SNA

Module

You can display the module that issues a SNA message in the message by setting the MSGMOD start option to YES. See Adding the originating module to the message text for more information about the MSGMOD start option.

Routing code

2

Descriptor code

5

Automation

Not recommended.

Example

The following is an example of the display output from a DISPLAY TOPO,LIST=TDUDIAG,ORIG=SSCP1A,DEST=SSCPBA,TGN=2,NUM=3 command:
IST350I DISPLAY TYPE = TDU DIAGNOSTICS                               
IST2311I TDU DIAGNOSTIC INFORMATION FOR TG: TGN = 21                 
IST2256I ORIG = NETA.SSCP1A - DEST = NETA.SSPCBA                     
IST2312I CURRENT RSN = 3128 - HEX RSN = 00000C38                     
IST2355I TDUDIAG THRESHOLD REACHED ON 02/11/10 AT 13:37:08           
IST924I -------------------------------------------------------------
IST2275I TDU INFORMATION SINCE LAST RESET ON 02/11/10 AT 10:48:52    
IST1769I LAST TDU RECEIVED - 02/11/10 13:40:14 FROM NETA.SSCP1A      
IST2281I LAST TDU SENT - 02/11/10 13:40:20                           
IST2282I TDU COUNTS:                                                 
IST2352I   SENT     = 3890         RECEIVED = 5101                   
IST2353I   ACCEPTED = 793          REJECTED = 4260                   
IST2354I   IGNORED  = 48                                             
IST2313I TOTAL RSN UPDATES BY LOCAL HOST NODE = 4260                                     
IST924I -------------------------------------------------------------
IST2294I TDUDIAG RSN UPDATES:                                        
IST2295I                    TIME      HEX RSN   HEX RSN              
IST2296I CP NAME            UPDATED   BEFORE    AFTER     REASON     
IST2297I NETA.SSCP1A        13:40:20  00000C36  00000C38  TDU GREATER
IST2300I   RECEIVED FROM: NETA.SSCP1A                                
IST2297I NETA.SSCP1A        13:40:20  00000C34  00000C36  TDU GREATER
IST2300I   RECEIVED FROM: NETA.SSCP2A                                
IST2297I NETA.SSCP1A        13:40:19  00000C32  00000C34  TDU GREATER
IST2300I   RECEIVED FROM: NETA.SSCP1A                                
IST2314I 3 OF 50 RSN UPDATES DISPLAYED                               
IST314I END