IST2306I
TDU DIAGNOSTIC INFORMATION FOR NODE: ID = cp_name

Explanation

VTAM® issues this message as part of a group of messages in response to a DISPLAY TOPO,LIST=TDUDIAG,ID=cp_name. A complete description of the message group follows:
 IST350I DISPLAY TYPE = TDU DIAGNOSTICS
 IST2306I TDU DIAGNOSTIC INFORMATION FOR NODE: ID = cp_name
 IST2312I CURRENT RSN = decimal_rsn - HEX RSN = hex_rsn
 IST2356I PLATFORM = platfor
[IST2355I TDUDIAG THRESHOLD REACHED ON date AT time]  
[IST2307I THIS NODE DOES NOT SUPPORT UNKNOWN TOPOLOGY VECTORS]
[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 node. 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 node 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
    • DISPLAY NET,TOPO,LIST=TDUDIAG,CLEAR=YES
    • DISPLAY NET,TOPO,LIST=TDUDIAG,ID=cpname,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 node. 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 node. See DATE and TIME formats for information about the date and time values.
IST2282I, IST2352I, IST2353I, IST2354I
  • This message subgroup displays topology database update (TDU) counts for this node. 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 node.
  • IST2352I
    • This message displays the counts of TDUs that were sent and received for this node.
    • sent is the number of TDUs about the node that were sent since the last time that the TDU counts were reset.
    • received is the number of TDUs about the node 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 node.
    • accepted is the number of TDUs about the node 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 node.
    • ignored is the number of TDUs about the node 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 node.
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 node. 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 node.
  • 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 node. 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 node 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 node.
    • time is the time when the TDUDIAG RSN update for this node 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 node before the RSN update. It is expressed in hexadecimal.
    • after_rsn is the RSN for the node after the RSN update. It is expressed in hexadecimal.
    • reason is the reason that the RSN was updated for this node. Possible values are:
      ****NA****
      RSN update reason is unknown.
      BN EXCHANGE
      The RSN was updated for a non-native border node that was sent in a topology exchange.
      BN STATUS
      The RSN was updated for the host node when an intersubnet link (ISL) was activated or deactivated, changing the border node (BN) status of the host node.
      CHANGE ROLE
      The RSN was updated for an adjacent node when the node type changed from an NN to an EN.
      COMMAND
      The RSN was updated for the node as the result of a command other than those specifically listed.
      F DELETE
      The RSN was updated when a MODIFY TOPO,FUNCTION=DELETE,SCOPE=NETWORK command was entered to delete the node.
      F NORMAL
      The RSN was updated when a MODIFY TOPO,FUNCTION=NORMAL,SCOPE=NETWORK command was entered to change the node 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 node status to quiesced.
      NODE UPDATE
      The RSN was updated when one of the following occurred:
      • A MODIFY VTAMOPTS,ROUTERES=value command was entered to change the node's route resistance.
      • A CDRM-CDRM session was activated, changing the node from a pure APPN node to an interchange node (ICN).
      GARBAGE
      The RSN was updated during topology garbage collection to inform the rest of the network of the impending node deletion.
      TDU EQUAL
      The RSN was updated when an input TDU was received for the node 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 host node with a RSN greater than the RSN in the topology database. Because the receiving host node maintains the RSN, this is inconsistent information.
      TDU VECTOR
      The RSN for the node was updated from an input TDU vector.
      WEEKLY
      The RSN for the host node was updated during the weekly broadcast of the node and all TGs owned by the node.
  • IST2300I
    • One IST2300I message is issued following each IST2297I message that describes a TDUDIAG RSN update 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.
IST2306I
  • This is a header message for the topology database update (TDU) diagnostic information for a node.
  • cp_name is the network-qualified CP name of the node.
IST2307I
  • This message indicates that the displayed node is an adjacent node that does not support the receipt of unknown topology vectors in TDUs. Network nodes adjacent to the displayed node can send only the originally architected control vectors, X'44', X'45', X'46', and X'47', in TDUs to the displayed node.
IST2312I
  • This message displays the current resource sequence number (RSN) for this node.
  • decimal_rsn is the current RSN in decimal format.
  • hex_rsn is the current RSN in hexadecimal format.
IST2313I
  • This message displays information about resource sequence number (RSN) updates made for this node.
  • rsn_count is the total number of times that the host node has updated the RSN for this node since the last time that the TDU counts were reset.
IST2315I
  • This message is issued if no TDU about this resource was sent.
IST2355I
IST2356I
  • platform is the platform identifier this node. Possible values are:
    ****NA****
    Platform identifier is unknown
    ****NA****
    Platform identifier is unknown
    CS/2
    IBM® Communications Server for OS/2
    CS/AIX
    IBM Communications Server for AIX®
    CS/LINUX Z
    IBM Communications Server for Linux on System Z
    CS/LINUX I
    IBM Communications Server for Linux on Intel
    CS/WINDOWS
    IBM Communications Server for Windows
    ISERIES
    IBM iSeries®
    SNAPLUS2
    Hewlett-Packard SNAplus2
    Z/OS VTAM
    IBM z/OS® Communications Server (VTAM)
    Z/VM VTAM
    IBM z/VM® VTAM
    Z/VSE VTAM
    IBM z/VSE® VTAM

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 node has excessive TDU activity, and TDUDIAG RSN update information is saved for the node 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,ID=SSCP1A,NUM=6 command:
IST350I DISPLAY TYPE = TDU DIAGNOSTICS
IST2306I TDU DIAGNOSTIC INFORMATION FOR NODE: ID = NETA.SSCP1A
IST2312I CURRENT RSN = 1024100 - HEX RSN = 000FA064
IST2356I PLATFORM = Z/OS VTAM
IST2355I TDUDIAG THRESHOLD REACHED ON 01/29/10 AT 15:42:08
IST924I -------------------------------------------------------------
IST2275I TDU INFORMATION SINCE LAST RESET ON 01/29/10 AT 11:43:47
IST1769I LAST TDU RECEIVED - 01/29/10 15:43:25 FROM NETA.SSCP2A
IST2281I LAST TDU SENT - 01/29/10 15:43:25
IST2282I TDU COUNTS:
IST2352I   SENT     = 496565       RECEIVED = 541498
IST2353I   ACCEPTED = 42795        REJECTED = 450422
IST2354I   IGNORED  = 48281
IST2313I TOTAL RSN UPDATES BY LOCAL HOST NODE = 502059
IST924I -------------------------------------------------------------
IST2294I TDUDIAG RSN UPDATES:
IST2295I                    TIME      HEX RSN   HEX RSN
IST2296I CP NAME            UPDATED   BEFORE    AFTER     REASON
IST2297I NETA.SSCP1A        15:43:25  000FA062  000FA064  TDU GREATER
IST2297I NETA.SSCP1A        15:43:25  000FA060  000FA062  TDU GREATER
IST2300I   RECEIVED FROM: NETA.SSCP2A
IST2297I NETA.SSCP1A        15:43:19  000FA05E  000FA060  TDU GREATER
IST2297I NETA.SSCP1A        15:43:18  000FA05C  000FA05E  TDU GREATER
IST2300I   RECEIVED FROM: NETA.SSCPAA
IST2297I NETA.SSCP1A        15:43:02  000FA05A  000FA05C  TDU GREATER
IST2297I NETA.SSCP1A        15:43:02  000FA058  000FA05A  TDU GREATER
IST2300I   RECEIVED FROM: NETA.SSCPAA
IST2314I 6 OF 50 RSN UPDATES DISPLAYED
IST314I END