View Explanation Fields
The following fields are displayed in the
View Explanation window. Select the field
you want help on:
This is the date and time that the alert was received by Tivoli NetView for z/OS.
The date/time format can be customized on the workstation
and does not necessarily match the "Date/Time Created" format.
A major vector is one of the mechanisms used by Tivoli NetView for z/OS to receive data and issue commands. A major vector is made up of one or more
subvectors.
A major vector is in the format:
- Length (2 bytes)
- Key (2 bytes)
- One or more subvectors
Subvectors are in the format:
- Length (1 byte)
- Key (1 byte)
- Data (0-254 bytes)
A major vector can be received by Tivoli NetView for z/OS across the SSCP-PU
interface, LU 6.2 interface, or program-to-program interface.
Subvectors X'00' - X'7F' are common to all major vectors.
Subvectors X'80' - X'FE' are unique to a given major vector type.
For more information see
Systems Network Architecture Formats.
Subvectors are units of information made up of a length field, a key
field, and data. The key field is used to identify the data. The
length field is the length of the data plus two.
Subvectors are contained within a major vector. Subvectors are in the
format:
- Length (1 byte)
- Key (1 byte)
- Data (0-253 bytes)
For more information see
Systems Network Architecture Formats.
The Alert Detail section contains additional information
about basic (non-generic) alerts.
This section consists of the following data, if available:
- Product Unique Text
- Information from the product that generated the alert.
This information comes from alert subvector X'00'.
- Detail Description
- Information, predefined to Tivoli NetView for z/OS, that is unique to the associated alert. This information comes from a user-modifiable file maintained in Tivoli NetView for z/OS. The filename is BNKxxxyy where xxx is the block ID and yy is the action code derived from the associated alert. The BNKxxxyy file may contain labels for up to three qualifiers.
- Qualifiers
- Information unique to this particular occurrence of a problem.
The information
is generated by the alert sender and contains things such as address,
port ID, phone number, and so on.
- Information, as follows:
-
- GENERAL
- The hexadecimal code indicating the classification and cause of the
problem.
See the Tivoli NetView Problem Determination and Diagnosis
and Systems Network Architecture Formats for more information.
for more information.
- SPECIFIC
- The hexadecimal code for the generic type of component,
sub-component, or logical resource that can be most closely related to
the alert.
See the Tivoli NetView Problem Determination and Diagnosis
and Systems Network Architecture Formats for more information.
for more information.
- ACTION
- The code
used to select a recommended action display;
normally the alert description code from alert subvector X'91'.
- BLOCK ID
- The code used to identify the IBM hardware or software associated
with the record.
- PROD
- A product ID that is not specifically
supported by Tivoli NetView for z/OS, either a
four-character machine type or a 7- or 9-character product
number, from alert subvector X'10'.
This identifies the general classification and cause of the problem as
well as the generic type of component, sub-component, or logical
resource that can be most closely related to the alert.
The parenthesis indicates that the input record was not in a format
predefined to Tivoli NetView for z/OS. Therefore, the text is based on a general
interpretation of the record contents.
This is a brief description of why the event was generated and an
identification of the most probable failing component.
This is a variable number of detailed data fields. The fields contain
information unique to this particular occurrence of the problem. This
information is generated by the alert sender and contains things such as
address, port ID, phone number, etc.
Each qualifier may consist of the following:
- A product ID that states which hardware or software
product identification is relevant
- A data ID that indicates the type of data that is involved (for example, error
code or port number)
- Product-specific data
This is a list of probable causes for the problem. Within a
category, such as user causes or failure causes, the causes are listed
in most probable order.
Recommended actions to further isolate or correct the condition which
caused the problem are also included. The actions are listed in the
order they should be performed.
This is the date and time when the alert was generated by the sending
product. The date/time format can be customized using the SCRNFMT option of
the Tivoli NetView for z/OS DEFAULTS or OVERRIDE commands. For more information about the SCRNFMT option, see the Tivoli NetView for z/OS: Installation Configuring Additional Components book.
This is a message that was sent in the alert record.
The text was supplied by someone who, when entering the message,
is using system resources. This person plays no role in
providing system resources.
This is a message that was sent in the alert record. The text was
supplied by a person who, when entering the message, is
involved in providing or managing system resources.
This is a message that was sent in the alert record. The text is
supplied by a program that was written for or by an end user and applies
to the end user's work. This program could have been implemented in
either software or microcode.
This is a message that was sent in the alert record. The text was
supplied by a program that controls other system resources. This
program may have been implemented in either software or microcode.
Actual causes and actions are shown when a problem has been resolved.
They are a list of the actual causes of the problem and the actual actions
taken to resolve the problem.
This is a brief description of why the alert was generated.
The resolution description is shown when a problem has been resolved.
It is a brief description of why the original alert was generated.
This includes a variable number of components that may have caused the alert
condition, with the most likely component listed first.
Actual causes are shown when a problem has been resolved.
They list the components that caused the original alert condition.
This is a message that was sent in the alert record.
This is an indication of the severity of the alert condition.
Supported values are:
- AVAILABILITY
- The availability status of the reported resource
has changed.
- BYPASSED
- The loss of availability to the end user has been
avoided by allowing the resource or an alternate
resource to be used. The original problem still
exists and the recovery may or may not be noticed
by the end user. The recovery may be accomplished
by intervention, internal or external to the reporting product.
- CUSTOMER APPLICATION
- A program that does not have an IBM order
number generated the problem record.
- DELAYED RECOVERED
- The sender is reporting a previously detected
alert condition that prevented reporting when detected.
- END USER GENERATED
- The problem has been initiated by a terminal operator.
- ENVIRONMENT
- An environmental problem has occurred.
- HELD
- An error condition was detected earlier, but
the record was not sent at the time because there
was no session available to send it on.
- IMPENDING PROBLEM
- A loss of availability to the end user
is impending, but has not yet happened.
- INSTALLATION
- A system definition or incompatibility problem
between components has occurred.
- INTENSIVE MODE REC
- The record is a result of the
user invoking Intensive Mode Recording, a feature of the NCP.
When invoked, a record is generated each time the NCP goes through an
error recovery.
- INTERVENTION REQ'D
- Manual intervention is required.
- NOTIFICATION
- A loss of availability to the end user is impending,
but has not yet happened or a change to a network or system
component has occurred for which an operator notification is required.
- PERFORMANCE
- A recognized measurement of performance, such as
response time, has exceeded a preset threshold.
- PERMANENT
- A loss of availability to the end user is
reported. Intervention external to the reporting product is required
to recover.
- PERMANENT AFFECTED
- The target resource is unavailable
because of a persistent error in a resource other than the target.
- OPERATION/PROCEDURE
- The ability to perform a requested
function is not possible because of an operation or procedural error.
- REDUNDANCY LOST
- Redundant hardware, software, or both, provided to
ensure continued operation in the event of a
failure has experienced a malfunction. As a result,
failure of the remaining operational hardware
or software results in a loss of corresponding services.
- RESENT ALERT
- An alert has been resent, providing additional
information about the original problem.
- RESOLVED PROBLEM
- A previously reported problem is resolved. This
record identifies the way the problem was resolved and the failing
resource.
- SECURITY
- An incident has been detected that may indicate
security problems.
- SUMMARY
- The record contains SNA summary error counters. The
record is normally the result of a Tivoli NetView for z/OS solicitation.
- TEMPORARY
- A momentary loss of availability
is detected that may be noticed by the end user, but does not
require intervention external to the reporting product.
- UNKNOWN
- Severity of the alert condition cannot be assessed.
- UNSUPPORTED TYPE
- The alert type code is not supported by Tivoli NetView for z/OS.
This identifies the way in which the problem was resolved.
This identifies the severity of the alert condition or the way
in which the alert condition was resolved.
This is a brief description of why the alert was generated.
This lists a variable number of components that caused the alert
condition, with the most likely component listed first.
This is a list of causes for the problem. Within a category, such as
user causes or failure causes, the causes are listed in most probable
order.
This section also lists actions to further isolate or correct the
condition which caused the problem. The actions are listed in the order
they should be performed.