Status History

View the status history for an SNA resource by selecting a resource and selecting Event Viewer from the NetView® management console context menu. This is a record of the most recent status changes for the resource. The first status shown is the final status from RODM.

Resources That Have Status History

If resources are deleted from the SNA topology manager internal cache but are still in RODM, the status history entries can still be displayed. When the SNA topology manager is shut down, all status history information is deleted. The SNA topology manager maintains no status history for aggregate objects (for example, subareaTransmissionGroupCircuit). Status history is available for:

• t5Nodes
• t4Nodes
• t2-1Nodes
• appnNNs
• appnENs
• lenNodes
• interchangeNodes
• migrationDataHosts
• definitionGroups (major nodes)
• virtualRoutingNodes
• crossDomainResourceManagers
• crossDomainResources
• logicalUnits
• logicalLinks
• ports
• appnTransmissionGroupCircuits
• appnTransmissionGroups

Discarding Status History

The status history entries always show the last reported status update for each agent reporting the status of a resource. In addition, five entry positions record the most recent status changes. The oldest information is discarded when the set of entries is full and a new update is received. If only one agent reports a resource, the set of entries is a simple list of the five most recent changes.

For multiply-owned objects, the entries contain two types of status updates, reported and resolved:

• The reported status is the status that is sent by the agent (adjusted by any methods you might have installed).
• The resolved status is the status calculated by using the status resolution table (FLBSRT).

If more than one agent reports status for a resource (as shown in Figure 18), new status information is added to the set of five entries when:

• Any agent sends a status update
• The status resolution table (or a method) resolves status

As shown in Figure 18, if agent A reports a status change, the agent A data becomes the newest entry. In addition a second entry, resolved status, is added to the set of entries. Resolved status is entered in the status history set of entries every time for multiply-owned objects, even if the resolved status is the same.

Figure 18. Updating the Status History Entries from Two Agents

When only one agent reports on a resource than can be multiply-owned, resolved status might be reported if it has been modified by the use of a user-written method, or if the individualStatus of the object in RODM has been changed such that the status default is no longer unknown.

Interpreting the Status History Data

The data displayed in the status history has three parts:

• The reporting agent name or static SSCP name that the resource status collector reported to the resource status focal point. This is one of the following items:
  • The network-qualified CP name
  • RESOLVED.FLBTOPO (if this is resolved status, not an agent report)
  • Network ID of contributing t4Node (if *t4NodeGateway)
• OSI states, OSI status, and native status (Refer to the description of the states field in the IBM Tivoli NetView for z/OS Data Model Reference.)
• Time stamp (The SNA topology manager records the time just after the object status in RODM has been updated.)

The nativeStatus Field

The nativeStatus field is a product-specific status supplement to OSI status. The field is a byte of the states field in the SNA topology data model and RODM. It provides a conversion of established VTAM® status representations to an OSI-like format.

The nativeStatus field is reported by VTAM topology agents for most VTAM resources, including:

• ports
• logicalLinks
• crossDomainResources
• logicalUnits
• Owned t4Nodes
• crossDomainResourceManagers

Usually, when the SNA topology manager infers status of another object, nativeStatus is not provided except for definitionGroup objects that are active. For a VTAM topology agent that contacts a t4Node but has not activated an NCP definitionGroup for this t4Node, the status of this t4Node on this VTAM console is NEVAC (never active), and this status from this VTAM topology agent is not captured in the status history.

Calculated Status for Advanced Peer-to-Peer Networking Resources

Some status updates for Advanced Peer-to-Peer Networking® resources are not sent by the agent, but are calculated by the SNA topology manager. For example in Advanced Peer-to-Peer Networking network topology, an Advanced Peer-to-Peer Networking TG status change might cause the SNA topology manager to change the status of the other nodes, based on whether at least one active path is connected to this resource. If no active path exists, the resource is marked inactive. This calculated update is displayed in the status history as if the agent that sent the update reported the status directly.

[ Top of Page | Previous Page | Next Page | Contents ]