New in this release
This overview includes the following sets of features added to
IBM(R) Tivoli(R) OMEGAMON(R) for Mainframe Networks in V4.2 and later
fix packs:
New features in Version 4.2.0 Fix Pack 3 for Enhanced Monitoring
and z/OS v1.12 Compatibility
IBM® Tivoli® OMEGAMON® XE
for Mainframe Networks Fix Pack 3 for Enhanced Monitoring and z/OS® v1.12 Compatibility is a function-rich
addition to your OMEGAMON XE
for Mainframe Networks environment that exploits the new callable
network management interfaces (NMIs) available with zOS v1.12. This
fix pack includes the following new functionality:
Support for z/OS v1.12
OMEGAMON XE for Mainframe
Networks exploits the new capabilities of z/OS v1.12, bringing the enhanced monitoring power
of the newest version of z/OS Communications
Server to Tivoli Enterprise
Portal.
The version of the z/OS Communications
Server that is part of z/OS v1.12
supports implementation of new network management interface (NMI)
calls that enable the OMEGAMON XE
for Mainframe Networks monitoring agent to greatly reduce the amount
of CPU usage related to SNMP queries. SNMP is now required only for
collecting Open System Adaptor (OSA) performance data in a z/OS v1.12 or later environment.
Because of these differences, workspaces running under different
versions of z/OS retrieve data
differently depending on z/OS level.
For these data types (TCP/IP Stack Layer, TCP/IP Address Space, Interface,
Device, and Gateways), data is no longer retrieved using SNMP but
instead uses the callable NMIs.
If the address space being monitored is running z/OS v1.11 or earlier, attribute values are retrieved
using SNMP. If the address space being monitored is running z/OS v1.12 or later, the attribute
values are retrieved using the z/OS Communications
Server callable network management interface (NMI). For more granular
understanding of data sources, see the individual attributes and workspaces,
or see the data source table in the IBM Tivoli OMEGAMON XE for Mainframe Networks: User Guide.
If you are viewing any of the new or updated workspaces discussed
in the sections that follow on z/OS v1.12,
non-strategic interfaces have status information only reported. Performance-related
attributes show a value of zero (0). The strategic interfaces have
one of the following Interface Types:
- Loopback
- OSA-Express Queued Direct I/O (QDIO) Ethernet
- HiperSockets™
- Multipath Channel Point-To-Point (MPCPTP)
- Virtual IP Address (VIPA)
Impact:
- More data, giving you better insight into the full range of interfaces
supported by z/OS v1.12
- Better data for debugging network performance issues
- A reduced SNMP footprint at a lower CPU cost for data collection
New workspaces and attributes that exploit z/OS v1.12
Exploitation of the new version of z/OS Communications
Server that is part of z/OS v1.12
makes it possible for OMEGAMON XE
for Mainframe Networks to bring you more than 300 new attributes spread
across 8 new workspaces. The new attribute groups and workspaces summarized
in Table 1 were added to take advantage of new monitoring
capabilities introduced in z/OS v1.12.
Impact:
- Improved diagnostic capabilities
- Reduced CPU costs
- Reduced configuration costs
Updated workspaces and attributes that exploit z/OS v1.12
Existing OMEGAMON XE
for Mainframe Networks workspaces and attribute groups have been enhanced
to give you fast, efficient access to the data now available through z/OS v1.12 callable NMIs. The attribute
groups and workspaces listed in Table 2 have been
enhanced.
Table 2. Existing workspaces and attribute groups updated to exploit z/OS v1.12
Attribute group |
Workspace |
Address Space Attributes (KN3TAS) |
TCPIP Address Space
If the address
space being monitored is running on z/OS v1.11
or earlier, the values for this attribute group are retrieved using
SNMP. If the address space being monitored is running on z/OS v1.12 or later, the values
for this attribute group are retrieved using the z/OS Communications Server callable network management
interface (NMI) |
TCP/IP Summary
A new Interface
Count attribute was added to the TCPIP Address Space Attributes
and is displayed in the TCPIP Summary workspace. This attribute is
defined as the number of interfaces defined for the TCP/IP stack.
If the address space being monitored is running on z/OS v1.11 or earlier, the values
for this attribute group are retrieved using SNMP. If the address
space being monitored is running on z/OS v1.12
or later, the values for this attribute group are retrieved using
the z/OS Communications Server
callable network management interface (NMI) |
TCP/IP Summary History
A new Interface
Count attribute was added to the TCPIP Address Space Attributes
and is displayed in the TCPIP Summary workspace. This attribute is
defined as the number of interfaces defined for the TCP/IP stack.
If the address space being monitored is running on z/OS v1.11 or earlier, the values
for this attribute group are retrieved using SNMP. If the address
space being monitored is running on z/OS v1.12
or later, the values for this attribute group are retrieved using
the z/OS Communications Server
callable network management interface (NMI). |
Devices Attributes (KN3TDV) |
Gateways and Devices workspace, Devices table
View
- If the address space being monitored is running on z/OS v1.11 or earlier, the values
for this attribute group are retrieved using SNMP.
- If the address space being monitored is running on z/OS v1.12 or later, the values
for this attribute group are retrieved using the z/OS Communications Server callable network management
interfaces (NMIs).
- A new attribute has been added to enable linking between this
workspace and z/OS v1.12 or
later OSA devices and interfaces. That attribute is Port
Interface Index, defined as the interface port index associated
with an OSA device or interface.
|
Gateways Attributes (KN3TGA) |
Gateways and Devices workspace, Gateways table
View
- If the address space being monitored is running on z/OS v1.9 or earlier, the values
for this attribute group are retrieved using SNMP.
- If the agent address space being monitored is running on z/OS v1.10 or v.1.11, the route
information in this workspace is retrieved using the I/O control (IOCTL).
Link or Interface attributes associated with the Gateway are retrieved
using SNMP.
- If the address space being monitored is running on z/OS v1.12 or later, the values
for this attribute group are retrieved using the I/O control (IOCTL)
interface. Link or Interface attributes associated with the Gateway
are retrieved using the z/OS Communications
Server callable network management interfaces (NMIs).
Six new attributes were added:
- Dynamic Route Indicates whether the route
used by this gateway was dynamically created (valid for IPv4 only).
If you are viewing this workspace on an LPAR running z/OS 1.9 or earlier, this attribute is unavailable
and will be blank.
- IP Version The IP version of the route
used by this gateway.
- MTU Value The maximum transmission unit
(MTU) in bytes for the route. If you are viewing this workspace on
an LPAR running z/OS 1.9 or
earlier, this attribute is unavailable and will be displayed as a
zero (0).
- Network Route Indicates whether the route
used by this gateway was defined as a network route. If you are viewing
this workspace on an LPAR running z/OS 1.9
or earlier, this attribute is unavailable and will be blank.
- Route Status The status of route used by
this gateway. If you are viewing this workspace on an LPAR running z/OS 1.9 or earlier, this attribute
is unavailable and will be blank.
- Route Type The type of route used by this
gateway. If you are viewing this workspace on an LPAR running z/OS 1.9 or earlier, this attribute
will be blank.
The existing Link Name attribute is now called Link or
Interface Name. The existing Link Status attribute is now called Link
or Interface Status. |
Interfaces (KN3TIF) |
Interfaces workspace
Two attributes in the
Interfaces Attributes have been updated to accommodate z/OS v1.12.
- Interface Capacity: An estimate, in bits
per second (z/OS v.1.11 or
earlier) or million bits per second (z/OS v.1.12
or later), of the current data rate capacity for the interface. The
format is this attribute has been updated when the workspace being
monitored is running z/OS v1.12
or later. This attribute now expresses capacity in millions of bits
per second instead of in bits per second.
- Physical Address: The address of the interface
at the protocol sublayer. The length of this attribute has been increased,
and this field now shows data for ATM, HYPERchannel, LCS Ethernet,
and MPCIPA OSA-Express QDIO interface types only. The old version
of this attribute was deprecated.
|
KN3 TCP Collector Status (KN3TCS) |
Agent Status workspace
A new attribute was
added to accommodate z/OS v.1.12:
- Data Link Control Statistics Collection:
Indicates whether Interface Data Link Control (DLC) statistics are
to be collected for this stack.
Three additional attributes were added that are z/OS release independent:
- Data Link Control Statistics Collection:
Indicates whether Interface Data Link Control (DLC) statistics are
to be collected for this stack.
- Interface Statistics Collection: Indicates
whether Interface statistics are to be collected for this stack.
- OSA Statistics Collection: Indicates whether
OSA statistics are to be collected for this stack.
- Stack Layer Statistics Collection: Indicates
whether Stack Layer statistics are to be collected for this stack.
|
TCPIP Stack Layer (KN3TSL) |
TCP/IP Stack Layers workspace
If
the address space being monitored is running on z/OS v1.11 or earlier, the values for this attribute
group are retrieved using SNMP. If the address space being monitored
is running on z/OS v1.12 or
later, the values for this attribute group are retrieved using the z/OS Communications Server callable
network management interface (NMI) |
Impact:
- Improved diagnostic capabilities
- Reduced CPU costs
- Reduced configuration costs
- Additional and improved routing information
- Self-diagnosis for new data types through the Agent Status
workspace
New product-provided situations
To take advantage of all the new and enhanced attribute groups,
nine new situations have been added:
- N3T_DLC_Accelerated_Bytes: Triggered if
QDIO Accelerator is configured in TCPIP, but the value for the Accelerated
Bytes attribute does not change over three consecutive data sampling
intervals, indicating that the QDIO Accelerator routes are not being
used.
- N3T_DLC_Max_Staging_Queue_Depth: Triggered
if the value for the Maximum Staging Queue Depth attribute is greater
than zero, indicating that the interface is not accepting outbound
data as fast as the device driver is presenting it.
- N3T_DLC_Read_Deferrals: Triggered when the
Read Processing Deferrals attributes has a value greater than zero,
indicating a critical problem that prevents the read queue from acquiring
the control blocks it needs for inbound data.
- N3T_DLC_Reads_Exhausted: Triggered if the
value for the Reads Exhausted attribute is greater than zero, indicating
that no read buffers are available to the OSA or HiperSockets device upon
entry to the queued direct I/O (QDIO) program-controlled interrupt
(PCI) Exit.
- N3T_Interface_Bandwidth_Util: Triggered
if the Bandwidth Utilization attribute, indicating that the total
percentage of capacity being used, is greater than or equal to 95%,
indicating that the interface is operating over capacity.
- N3T_Interface_Xmit_Rcv_Bytes: Triggered
if the total amount of traffic across an interface (represented by
sum of the Bytes Received and Bytes Transmitted attributes) is zero,
indicating network congestion that requires load balancing, or a configuration
error.
- N3T_IP_Input_Discard_Pct: Triggered if the
Input Discard Percentage attribute has a value of three percent or
greater, indicating that at least three of the IP segments that this
TCP/IP address space received from the network were undeliverable
and discarded due to, for example, no route found errors, unknown
or unsupported protocol errors, truncation errors, invalid address
errors, or reassembly failures.
- N3T_IP_Output_Discard_Pct: Triggered if
the value for the Output Discard Percentage attribute is three percent
or greater, indicating that a significant number of datagrams is being
discarded and pointing to the need for more buffer space and additional
diagnostic actions.
- N3T_TCP_Flow_Controls: Triggered if flow
control issues (the sum of Input and Output Window Updates and Window
Probes) are seen over three consecutive samples, indicating that the
reading application is having trouble keeping up with the sending
application.
Impact:
- New strategic, ready-to-start situations designed
by system experts
- Enhanced ready-to-use value
Support for the zEnterprise mainframe server
IBM recently announced the
zEnterprise mainframe server, a powerful, energy-efficient system
that enables POWER7® and System x® servers to share resources
and be managed as a single, virtualized system. OMEGAMON XE for Mainframe Networks added data types
to existing attributes in this fix pack to support zEnterpriseTM. For more information about zEnterpriseTM, see http://www-03.ibm.com/press/us/en/pressrelease/32166.wss.
Enhancements to Connections node workspaces
The workspaces related to the Connections node in the navigation
tree (Connections, UDP Endpoints, TCP Listeners, TCP Connections,
Application Connections, Application UDP Endpoints, Application TCP
Listeners, Application TCP Connections, and TCP Connections Link)
have been updated to implement a number of customer requirements.
The enhanced workspaces add 34 new attributes across four attribute
groups to take advantage of enhancements to the z/OS Communications Server callable network management
interfaces (NMIs). These updates include:
- Monitoring sent and received data queued for TCP connections
- Monitoring Application Transport - Transport Layer Security
(AT-TLS)
- Defining the Local Port attribute numerically
- Displaying the connection state for all connection types
Additionally, the product-specific Take Action commands
(Drop Connection, NSLookup IP Address, Ping IP Address, and Tracerte
IP Address) can now be issued from these linked-to workspaces:
Application Connections, Application UDP Endpoints, Application TCP
Listeners, Application TCP Connections, and TCP Connections Link.
Confusing gigabyte and byte representations fields have been eliminated.
These fields remain available in queries but are no longer displayed.
The attribute groups and workspaces listed in Table 3 are affected by these enhancements:
Table 3. Workspaces and attribute groups affected by Connections enhancements
Attribute group |
Workspace |
TCPIP Connections Attributes (KN3TCN) |
TCP Connections, Application TCP Connections,
and TCP Connections Link workspaces
The following new attributes
were added in this table:
- Local Port: The local port for this TCP
connection. The format of the displayed Local Port attribute is an
unsigned integer instead of a string. The existing Local Port attribute,
which was defined as a string, is no longer displayed in this workspace.
- Connection State: The state of the connection.
The list of possible states has been updated to show a state of “LISTEN"
for a TCP Listener connection and “UDP" for a UDP endpoint
connection.
- Total Bytes: The total number of bytes sent
and received since the connection started. This attribute is displayed
in place of the deprecated Total Bytes and Total Bytes (in GB) attributes.
The format of this new attribute is a long long integer.
- Total Bytes Received: The total number of
bytes received since the connection started. This attribute is displayed
in place of the deprecated Total Bytes Received and Total Bytes Received
(in GB) attributes. The format of this new attribute is a long long
integer.
- Total Bytes Sent: The total number of bytes
sent since the connection started. This attribute is displayed in
place of the deprecated Total Bytes Sent and Total Bytes Sent (in
GB) attributes. The format of this new attribute is a long long integer.
The following attributes were deprecated in this table:
- Total Bytes
- Total Bytes (in GB) (also not displayed)
- Total Bytes Received
- Total Bytes Received (in GB) (also not displayed)
- Total Bytes Sent
- Total Bytes Sent (in GB) (also not displayed)
|
TCPIP Details Attributes (KN3TCP) |
TCP Connections, Application TCP Connections,
and TCP Connections Link workspaces.
The following new attributes
were added to this table:
- APPLDATA: The result of an SIOCSAPPLDATA
ioctl query.
- AT-TLS Policy Status: The current Application
Transparent Transport Layer Security (AT-TLS) policy status for the
connection.
- AT-TLS Status: The current Application Transparent
Transport Layer Security (AT-TLS) status for the connection. This
value indicates whether the SSL handshake has completed successfully
for the connection.
- Congestion Window Size: The congestion window
size for this connection
- Duplicate ACKs: The number of duplicate
ACKs (TCP acknowledgements) received for this connection
- Inbound Bytes Buffered: The number of incoming
bytes buffered by this connection.
- Inbound Interface Name: The link name of
the receiving interface for this connection.
- Inbound Queued Data Time Stamp: The time
stamp of the oldest inbound data that was queued.
- Maximum Segment Size: The maximum segment
size the connection can send.
- Maximum Send Window Size: The maximum send
window size for the connection.
- Negotiated Cipher: The negotiated cipher
that is in use by the secure connection.
- Negotiated SSL Protocol: The negotiated
SSL protocol in use by the connection.
|
TCPIP Details Attributes (N3TCP)
(Continued) |
TCP Connections, Application TCP Connections,
and TCP Connections Link workspaces.
The following new attributes
were added to this table:
- Open Type: The type of open performed for
this connection.
- Outbound Bytes Buffered: The number of outgoing
bytes buffered by this connection.
- Outbound Queued Data Time Stamp: The time
and date of the oldest queued data waiting to be sent.
- Partner User ID: The user ID associated
with the partner's certificate.
- Receive Buffer Size: The receive buffer
size for the connection.
- Registered Ancillary Inbound Queue An indicator
of whether the TCP connection is registered with a TCP bulk data ancillary
inbound queue.
- Send Buffer Size: The send buffer size for
the connection.
- Send Window Size: The send window size for
the connection.
- Server Resource ID: The numeric identification
of the server (that is, the listener connection) associated with this
client connection.
- Slow Start Threshold: The slow-start threshold
for this connection.
- SSL Session Type: The type of System SSL
secure session defined in AT-TLS policy in use by the connection.
- Sysplex Cluster Connection Type The sysplex
cluster connection types for this connection.
- Telnet Session Type: The type of open performed
for this connection.
- TN3270 Client User ID: The client user ID
if the TCP connection is for a TN3270 or TN3270E session.
- TN3270 Logmode Name: The VTAM® Logmode if the TCP connection is for a TN3270
or TN3270E session.
- Total Bytes: The total number of bytes sent
and received since the connection started. This attribute is displayed
in place of the deprecated Total Bytes and Total Bytes (in GB) attributes.
The format of this new attribute is a long long integer.
- Total Bytes Received: The total number of
bytes received since the connection started. This attribute is displayed
in place of the deprecated Total Bytes Received and Total Bytes Received
(in GB) attributes. The format of this new attribute is a long long
integer.
- Total Bytes Sent: The total number of bytes
sent since the connection started. This attribute is displayed in
place of the deprecated Total Bytes Sent and Total Bytes Sent (in
GB) attributes. The format of this new attribute is a long long integer.
The following attributes were deprecated in this table:
- Total Bytes
- Total Bytes (in GB) (also not displayed)
- Total Bytes Received
- Total Bytes Received (in GB) (also not displayed)
- Total Bytes Sent
- Total Bytes Sent (in GB) (also not displayed)
|
TCP Listener Attributes (KN3TCL) |
TCP Listeners and Application TCP Listeners
workspaces
The following new attributes were added to this table:
- APPLDATA: The result of an SIOCSAPPLDATA
ioctl query.
- DVIPA: Whether or not the listener socket
supports Dynamic Virtual IP Addressing (DVIPA).
- DVIPA Quiesced: Whether or not Dynamic Virtual
IP Addressing (DVIPA) associated with the listener socket has quiesced.
- Established Connections in Backlog The number
of Connections in Backlog that are established.
- FRCA Connections in Backlog: The number
of Connections in Backlog that are established Fast Response Cache
Accelerator (FRCA) connections not present to be accepted by the application.
|
UDP Connections Attributes (KN3UDP) |
UDP Endpoints and Application UDP Endpoints
workspaces
The following new attributes were added to this table:
- Inbound Queued Data Time Stamp: The time
stamp of the oldest queued data that was queued.
- Last Activity Time Stamp: The last time
of connection activity.
- Total Bytes: The total number of bytes sent
and received since the connection started. This value is now calculated
differently and is expressed as a long long integer.
- Total Bytes Received: The total number of
bytes received since the connection started. This value is now calculated
differently and is expressed as a long long integer.
- Total Bytes Sent: The total number of bytes
sent since the connection started. This value is now calculated differently
and is expressed as a long long integer.
The following attributes were deprecated in this table:
- Total Bytes
- Total Bytes (in GB) (also not displayed)
- Total Bytes Received
- Total Bytes Received (in GB) (also not displayed)
- Total Bytes Sent
- Total Bytes Sent (in GB) (also not displayed)
|
Impact:
- The following customer requirements were satisfied by these updates:
- Include Receive and Send Queue metrics for Connections data.
- Modify the Local Port attribute in the Connections table to sort
numerically.
- Set a Connection State for all types of connections.
- Add AT-TLS support.
- More z/OS Communications
Server data is now available from the Tivoli Enterprise
Portal.
Retrieving route information with IOCTL
When monitoring an address space running on z/OS 1.10 or later, z/OS Communication
Server external I/O control (IOCTL) function calls are used to retrieve
route information. SNMP was used to previously obtain this data.
The change in data retrieval methods was made to reduce CPU utilization
when a large number of routes are defined. The route information
returned by the IOCTL calls is only from the main route tables (IPv4
and IPv6) for the stack. Policy-based routes are not supported by
these IOCTL calls. These IOCTL calls are supported by the z/OS UNIX Systems
Services Callable API.
Impact:
- Lower CPU utilization with large numbers of routes
- A reduced SNMP footprint for systems running z/OS v1.10 or later
DVIPA reporting differences
Differences exist in DVIPA reporting depending on the level of z/OS under which the monitoring
agent is running.
- Under z/OS V1.8 and V1.9,
all DVIPA data is reported using SNMP.
- Under z/OS V1.10 and V1.11,
DVIPA data is reported using both z/OS Communication
Server external I/O control (IOCTL) function calls and SNMP.
- Under z/OS V1.12 and later,
DVIPA data is reported using IOCTL and NMI Interface data collection.
z/OS Communications Server
does not report performance metrics for DVIPAs; therefore, these interface
performance metrics have always displayed as zero. Because of these
data collection differences noted earlier, DVIPA data is found in
different workspaces depending on the version of z/OS under which the monitoring agent is running.
- Under z/OS v1.11 and earlier,
DVIPA data is reported in the Interfaces workspace for these non-performance
related attributes only: Interface Name, Interface Type, Interface
Description, Current® State,
and MTU Size.
- In z/OS v1.12 and later,
DVIPAs are no longer reported in the Interfaces workspace. DVIPAs
are reported in the Gateways workspace. The value for the Link or
Interface Name in the Gateways table is blank for DVIPA routes If
a row in the Gateways table shows a value of blank for Link or Interface
Name attribute under z/OS v1.12
or later, then this row represents a DVIPA route.
Impact: More detailed and useful DVIPA data
can now be reported
New configuration options for more granular data collection
As part of z/OS v1.12 callable
interface support, the ability to turn data collection on and off
is now available for the following types of data:
- OSA Statistics
- Interface Statistics
- Data Link Control (DLC) Interface Read and Write Queue Statistics
- Stack Layer Statistics
Likewise, granular tracing options have been added for each of
these new data types.
These additional data types require new Configuration Tool options
and have resulted in new z/OS KN3FCCMD
MODIFY commands for stopping and starting these components when
the monitoring agent is running. Both of these updates are documented
in the IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide.
Impact:
- Configurable collection for new data types with potential CPU
savings
- Starting and stopping data collection on a per-component
basis
- Running more efficient component-level traces
Changes to OSA
In this fix pack, you will notice a number of changes to OSA data
collection and display, some of which are the result of z/OS v1.12.
Two new attributes were added to the OSA Ports, OSA-Express2 10
Gig Ports Summary, and OSA-Express3 Ports Summary workspaces that
enable linking between these workspaces and the Gateways and Devices,
Interface Status, and Interface Statistics workspaces for monitoring
agents running under z/OS v1.12
or later. For details about the new attributes, see Table 4.
Table 4. New attributes in OSA workspace
Attribute group |
Workspace |
New attribute |
OSA-Express Ports (KN3TPO) |
OSA Ports |
Two attributes in the OSA-Express
Ports attribute group have been added to accommodate z/OS v.1.12 and enable linking between the OSA Ports
workspace and the Gateways and Devices, Interface Status and Interface
Statistics workspaces. The z/OS Release attribute is defined as the version
of z/OS on which this instance
of the monitoring agent is running. The Interface
Port Index attribute is defined as the OSA-Express queued direct
I/O (QDIO) port interface index |
OSA 10 Gigabit Ports Summary (KN3TTS) |
OSA-Express2 10 Gigabit Ports Summary |
OSA-Express3 Ports Summary (KN3THS) |
OSA-Express3 Ports Summary |
It is typical for OSA adapters to be shared across multiple LPARs.
When the OSA adapters are configured across multiple LPARs, you can
collect OSA performance statistics for any LPAR that is sharing the
OSA adapter. Consequently, you do not need to turn on OSA data collection
for each instance of the OMEGAMON XE
for Mainframe Networks monitoring agent in your environment. A review
of your sharing configuration of the OSA adapters within a Central
Electronics Complex (CEC) might allow you to select only a few monitoring
agent instances that need to be configured to collect OSA data for
your environment. If all of the monitoring agents are running on z/OS v1.12 or later, then it would
be necessary to configure SNMP only on the LPARs where you elect to
collect OSA performance metrics.
Options are provided in the Configuration Tool to enable OSA data
collection globally for all TCP/IP address spaces running on the system
or for individual TCP/IP stacks and in the z/OS KN3FCCMD MODIFY commands to turn
OSA data collection on and off dynamically for a selected instance
of the monitoring agent.
Filtering provided in the OSA Port Interfaces workspaces has been
incorporated into the Interface Status and Interface Statistics workspaces.
When the monitoring agent runs in a z/OS v1.12
and later environment, the OSA Port Interfaces workspace is no longer
a target of a link, and consequently, this workspace has been deprecated.
Impact:
- You can now easily see the relationship between the OSA and interfaces
workspaces with new linking attributes.
- OSA Port (hardware) data can be associated with a TCP/IP gateway
or interface (software) data.
- You do not need to turn on OSA data collection for each instance
of the monitoring agent in your environment because you can collect
OSA performance statistics for any LPAR that is sharing the OSA adapter.
New dynamic links
Three new dynamic links to cross-product workspaces were
added:
- A link from the OMEGAMON XE
for Mainframe Networks Applications workspace to the IBM Tivoli OMEGAMON XE for DB2® Performance Monitor Thread Activity
By Plan workspace using the SMFID.
- A link from the OMEGAMON XE
for Mainframe Networks HPR Connections for EE Link workspace to the IBM Tivoli NetView® for z/OS Session Data workspace using the System ID,
filtering on Local CP Name.
- A link from the OMEGAMON XE
for Mainframe Networks HPR Connections for EE Link workspace to the IBM Tivoli NetView for z/OS Session Data workspace using the System ID,
filtering on Remote CP Name.
Impact:
- New cross-product integration
- Greater synergy with IBM Tivoli NetView for z/OS and IBM Tivoli OMEGAMON XE for DB2 Performance Monitor.
Support for the PARMLIB configuration method
The PARMLIB configuration method is a new alternative to using
the Configuration Tool (ICAT). Although the Configuration Tool is
still the primary method of configuring the Tivoli Management Services on z/OS components and the OMEGAMON XE products, the PARMLIB method might be
more suitable for new OMEGAMON XE
customers who are already accustomed to supplying parameter values
directly in the SYS1.PARMLIB data set and do not want to learn a new
tool.
With the PARMLIB configuration method, you edit a comprehensive
list of parameters for configuring all installed products and components.
You then submit a series of jobs to create a complete runtime environment
with the parameter values you specified. All products that you want
to configure must be enabled for PARMLIB. OMEGAMON XE for Mainframe Networks Fix Pack 3 is
enabled.
If you are an existing Configuration Tool user and already have
an existing RTE environment that you want to convert to using PARMLIB,
a utility is available to help you. Support for the PMAP utility
was introduced in OMEGAMON XE
for Mainframe Networks Fix Pack 2 and Interim Features for Self-Diagnosis.
The Configuration Tool was modified to enable the parameter mapping
(PMAP) report from the Runtime Environment menu.
The output of running this utility is a report that identifies
panels where configuration parameters are defined and RKAN*U members
where they are saved and can be used to configure using PARMLIB or
used to update parameters in the Configuration Tool.
The new IBM Tivoli OMEGAMON XE for Mainframe Networks: Parameter Reference introduced
in this fix pack provides complete documentation for the parameters
used by the Configuration tool, BATCH, and the PARMLIB configuration
methods.
Impact:
- Documentation for parameters used by the Configuration Tool, Batch,
and PARMLIB configuration methods
- When fully implemented, PARMLIB installation frees you from using
the Configuration Tool to configure new versions of OMEGAMON XE monitoring agents
on z/OS
New features in Version 4.2.0 Fix Pack 2 and Interim Features
for Self-Diagnosis
- The KN3 Agent Status attribute group in the Agent Status workspace
has been updated to display the following new attributes:
- IKE Daemon Started: Indicates whether the
Internet Key Exchange (IKE) daemon has been started on the monitored
system.
- PAGENT Daemon Started: Indicates whether
the Policy Agent (PAGENT) daemon is started on the monitored system.
- The KN3 TCP Collector Status attribute group in the Agent Status
workspace has been updated to display the following new attributes:
- IPv4 Security Enabled: Indicates whether
IP security is enabled for IPv4 interfaces.
- IPv6 Security Enabled Indicates whether
IP security is enabled for IPv6 interfaces.
- SMF Service Enabled: Indicates whether the
real-time SMF record information service is enabled.
- SNMP Agent Jobname: The job name for the
application that is bound to the SNMP agent port for this TCP/IP stack.
- The KN3 SNA Collector Status attribute group in the Agent Status
workspace has been updated to display the following new attribute:
- Agent VTAM Application Status: Indicates
the current status of the VTAM application used by the agent to collect
VTAM buffer pool and environment data.
- Agent VTAM Major
Node Name: The name of a dataset member that contains the definition
of a VTAM major node that defines the application used by the agent
to collect VTAM buffer pool and environment data.
- Agent VTAM Major Node Status: Indicates
the current status of the agent VTAM major node.
- PMI Exit Status: Indicates the current status
of the agent VTAM performance monitor interface (PMI) exit.
- SNA NMI Enabled: Indicates whether the SNA
network monitoring interface (NMI) is enabled.
- Support for nonstandard parameters. Under
the guidance of IBM Software Support, you can use the Configuration
Tool to specify values for configuration parameters other than those
shown in the interactive panels. This enhancement eliminates configuration
regression caused by the tool overlaying any parameters added, modified,
or deleted manually outside the control of the Configuration Tool.
For more information about nonstandard parameters and the "simulated
editor," refer to the IBM Tivoli OMEGAMON and Tivoli Management Services on z.OS: Common Planning and Configuration Guide.
- New thresholds were defined for attribute ARB Mode in the HPR
Connections and HPR Connections Link from EE workspaces so that the
cell would have a color that matches the value.
- The Configuration Tool was modified to enable the parameter mapping
(PMAP) report from the Runtime Environment menu. The report identifies
panels where configuration parameters are defined and RKAN*U members
where they are saved.
New features in Version 4.2.0 Fix Pack 1 and Interim Features
for Advanced Diagnostics
The following new features were introduced in Version 4.2.0 Fix
Pack 1 and Interim Features for Advanced Diagnostics:
- Two new product-provided Take Action commands were added:
NSLOOKUP and TRACERTE. The PING and DROP commands were introduced
in V4.2.
These new Take Action commands are executed using a product-specific
Take Action command handler that enables the product to pass IP commands
to z/OS(R) Communication Server and the
z/OS console. These product-provided Take Action commands are
available only on workspaces for which their functionality is appropriate.
These commands are issued in context by right-clicking a row in the
Summary table for the workspace or a bar graph that uses the same
query and selecting a Take Action command from the list of Take Action
commands available for that workspace and attribute. For more information
about the new Tracerte IP Address dialog, see TRACERTE command. For more information about the new
NSLookup IP Address dialog, see NSLOOKUP command.
- In this fix pack, the OMEGAMON XE for Mainframe Networks monitoring
agent introduces the capability to launch directly into the IBM(R) Tivoli(R) NetView(R) for z/OS V5.4 product from the Connections
and Application Connections workspaces and start or stop packet traces
in context for a specific connection. The monitoring agent uses the
Tivoli Enterprise Portal terminal view and the Terminal Emulator scripting
language to provide this dynamic link to the NetView product and modify
or start the packet trace function automatically.
The sample scripts
provided by the OMEGAMON(R) XE for Mainframe
Networks monitoring agent may be tailored to launch connections from
the Mainframe Networks monitoring agent or other OMEGAMON XE monitoring
agents on z/OS to other parts of the NetView product.
Two new
workspaces, the NetView for z/OS: Packet Trace – Start workspace and the NetView for z/OS: Packet Trace – Stop workspace, and the KN3 DWL Attributes were also added to support this new functionality.
The NetView for z/OS packet trace feature in the introduced
in OMEGAMON XE for Mainframe Networks Version 4.2.0 Fix Pack 1 and
Interim Features for Advanced Diagnostics has been updated. You can
run the Mainframe Networks fix pack without update if you have not
applied APAR OA31808 to NetView for z/OS. But if you have applied
this APAR to the NetView program, you must apply Interim Fix: 4.2.0.1-TIV-KN3-IF0001
to the OMEGAMON XE for Mainframe Networks monitoring agent to use
this function. Refer to the IBM Tivoli OMEGAMON
XE for Mainframe Networks: Planning and Configuration Guide for
more information about prerequisites.
- This fix pack also documents how to trigger IBM Tivoli NetView
for z/OS automation from OMEGAMON XE for Mainframe Network situations.
That information is found under the "Triggering IBM Tivoli NetView
for z/OS automation from OMEGAMON XE for Mainframe Networks situations"
topic in the IBM Tivoli OMEGAMON XE for Mainframe
Networks: User’s Guide. Two new sample situations, N3T_Sample_NetViewAuto_Cmd
and N3T_Sample_NetViewAuto_Msg, were created to demonstrate these
methods. Sample NetView automation table entries and REXX execs are
also provided in the &thilev.TKANSAM dataset
to recognize the situations and implement actions.
- A new workspace called OSA Port Interfaces is available that provides
information about selected OSA ports. A new Interface Index attribute
was added to the following workspaces:
- OSA Ports
- OSA-Express3 Ports Summary
- OSA-Express2 10 Gigabit Ports Summary
- Gateways and Devices
This attribute links the OSA workspace Summary tables to the
Device table and the Gateways table in the Gateways and Devices workspace
so that OSA adapter metrics, can be easily compared with device or
interface metrics.
Note:
This workspace is deprecated.
If the address space being monitored is running under z/OS v1.11 or
earlier, the workspace will show data. For address spaces running
under z/OS v1.12 or later, this workspace is not available.
- The CSM Buffer Pools workspace has been updated to display in-use
and allocation statistics for Communications Storage Manager (CSM)
buffers. A new view named Page Fixed Storage Allocations and the following
attributes were added:
- Current Page Fixed Storage In Use,
defined as the amount of page fixed storage currently in use, in kilobytes.
Page fixed-storage includes ECSA storage and 31-bit and 64-bit
backed data space.
- Maximum Page Fixed Storage Since IPL,
defined as the maximum page fixed storage allocated since IPL, in
kilobytes. Page fixed-storage includes ECSA storage and 31-bit
and 64-bit backed data space.
- Maximum Page Fixed Storage Allowed,
defined as the maximum page fixed storage allowed, in kilobytes.
Page fixed-storage includes ECSA storage and 31-bit and 64-bit
backed data space.
- Percent Page Fixed Storage Allocated,
defined as the percentage of page fixed storage currently allocated,
as compared to the maximum page fixed storage allowed.
- Percent Page Fixed Storage in Use,
defined as the percentage of page fixed storage currently in use,
as compared to the maximum page fixed storage allowed.
- The TCP/IP Memory Statistics workspace has been updated to display
free and in-use statistics for TCP/IP memory. The following
new attributes were added to workspaces that monitor z/OS V1.10 or
later systems:
- Authorized Private Storage Free, defined
as the current number of authorized private subpool storage bytes
free.
- Authorized Private Storage In Use, defined
as the current number of authorized private subpool storage bytes
in use.
- ECSA Storage Free, defined as the current
number of Extended Common System Area (ECSA) storage bytes free.
- ECSA Storage In Use, defined as the current
number of Extended Common System Area (ECSA) storage bytes in use.
- Percent Authorized Private Storage In Use,
defined as the percentage of authorized private storage that is currently
in use compared to the current authorized private storage that is
allocated.
- Percent ECSA Storage In Use, defined as
the percentage of Extended Common System Area (ECSA) storage currently
allocated compared to the maximum ECSA storage that is allowed.
The following new attributes were added for workspaces that monitor
z/OS V1.11 or later systems to account for 64-bit common storage:
- 64bit Common Storage Allocated, defined
as the current number of 64-bit common storage bytes allocated.
- 64bit Common Storage Free, defined as the
current number of 64-bit common storage bytes free.
- 64bit Common Storage In Use, defined as
the current number of 64-bit common storage bytes in use.
- Maximum 64bit Common Storage Allocated,
defined as the maximum number of 64-bit common storage bytes allocated.
- Percent 64bit Common Storage In Use, defined
as the percentage of 64-bit common storage that is currently in use
compared to the current 64-bit common storage that is allocated.
- This fix pack introduces fields that exploit 64-bit integers,
which can now be displayed in Tivoli Enterprise Portal. For readability
purposes, these large numbers are displayed with commas. Display of
32-bit integers remains unchanged (without commas). Commas are a display-only
convention. Automation scripts should not search on values with commas.
New features in V4.2
The following new features were introduced in V4.2:
- A new agent workspace and three new attribute groups were added
for reviewing the configuration and status information defined for
each instance of the OMEGAMON XE for Mainframe Networks monitoring
agent. For more information about this new workspace, see Agent Status workspace. To see the attributes contained
in this workspace, see KN3 Agent Status Attributes, KN3 SNA Collector Status Attributes, and KN3 TCP Collector Status Attributes.
- A new agent workspace and two new attribute groups were added
to support the OMEGAMON XE for Mainframe Networks command handler
Take Action commands. For more information about this new workspace,
see Command Log workspace. To see the attributes
contained in this workspace, see KN3 Take Action Command Attributes and KN3 Take Action Command Response Attributes.
These new Take Action commands are executed
using a product-specific Take Action command handler that enables
the product to pass IP commands to z/OS(R) Communication
Server and the z/OS console. These product-provided Take Action commands
are available only on workspaces for which their functionality is
appropriate. These commands are issued in context by right-clicking
on an attribute and selecting a Take Action command from the list
of Take Action commands available for that workspace and attribute.
For more information about the workspace and attributes supporting
these new Take Action commands, see the Take Action explanation in
the IBM Tivoli OMEGAMON XE for Mainframe Networks: User Guide.
- The Applications and TCP Listeners workspaces and attribute groups
have been updated to add the Total Backlog Connections Rejected attribute,
defined as the total number of connections rejected because the backlog
limit was exceeded before the listener was able to accept the waiting
connections.
- The HPR Connections workspace and attribute group have been updated
to add the Smoothed Round Trip Time attribute, defined as the round-trip
delay for this RTP connection, in units of 1/1000th of a second (ms).
- The TCPIP Address Space attribute group has added a z/OS Release
attribute that is not displayed by any workspace but is available
for automation.
- Configuration has been simplified and enhanced in the following
ways:
- A new "Create monitoring agent runtime members" option
has been added to the Configuration Tool SPECIFY CONFIGURATION PARAMETERS
for a specified RTE (panel KN341PPM). This new shortcut is particularly
useful when you change your configuration and need to rerun the JCL
to update the runtime environment. Previously, such a change required
cycling through a number of unnecessary panels.
- You can now use the Configuration Tool to specify which TCP/IP
stacks you want to monitor. Previously, the monitoring agent attempted
to monitor all discovered TCP/IP stacks. An option has been added
that enables you to monitor only the TCP/IP stacks you specify. The
default behavior is to collect data from all TCP/IP Address Spaces.
- You can now clone a monitored system definition from one TCP/IP
stack to another. You can copy an existing stack definition and update
all the fields rather than stepping through the sequence of Configuration
Tool panels for each TCP/IP stack.
- Support for z/OS V1.11.
The End to End Response Time Feature
product (ETE(R)) used by OMEGAMON II
for Mainframe networks requires a PTF to run under z/OS V1.11. See
APAR OA28511 for ETE V620 for more information.
- Support for reusable address spaces
z/OS V1.9 introduced the
ability to reuse address space identifiers (ASIDs). The z/OS ASID
Reuse function enables an address space to be created with a reusable
ASID. ASID reuse provides relief for z/OS users who currently have
to schedule IPLs to reclaim ASIDs that have become nonreusable by
allowing them to create reusable ASIDs. OMEGAMON XE for Mainframe
Networks V4.2.0 support for this function enables OMEGAMON XE for
Mainframe Networks started tasks to use the z/OS START command REUSASID=YES parameter.
OMEGAMON II for Mainframe Networks and ETE also
support reusable address spaces.
- All components are identified by the version number in the Managed
System Status workspace of the Tivoli Enterprise Portal. For example,
the Version column for rows in this table view might display the following
entries:
- 04.20.00 with an entry for a monitoring agent indicates that the
version of this monitoring agent is V4.2.0.
- 06.21.01 with an entry for a monitoring server indicates that
the version of this monitoring server is IBM Tivoli Monitoring V6.2.1,
with Fix Pack 1.
The new version numbering feature helps you to quickly identify
the version of each monitoring agent in an environment that comprises
multiple versions. In addition, the version number appears in the
description of queries in the Situation editor. Multiple queries with
the same name and description are required to support upgrade scenarios.
Including the version in the query descriptions enables you to more
easily identify which query is appropriate for a particular agent
at a particular version.
- The Tivoli Common Reporting reports previously available for download
from the IBM Tivoli Open Process Automation Library (OPAL) for V4.1
of OMEGAMON XE for Mainframe Networks are now available as part of
V4.2. See IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Reports of Tivoli Common Reporting book
for information about setting up Tivoli Common Reporting for the OMEGAMON
agents. See the IBM Tivoli OMEGAMON XE for Mainframe Networks: User's Guide for information about reports available
for this monitoring agent.
- Support for event forwarding:
If you are using IBM Tivoli Enterprise
Console(R) or IBM Tivoli Netcool(R) or Omnibus, in addition to IBM Tivoli
Monitoring, to manage events in your enterprise, you can now forward
events generated by Tivoli OMEGAMON XE for Mainframe Networks monitoring
agents to these event management products. See the following documents
for further information:
- See the "Event integration scenarios" section of the IBM Tivoli Monitoring: Installation and Setup Guide for
a discussion of the benefits of these products and the details of
how they can be integrated with IBM Tivoli Monitoring.
- See IBM Tivoli Monitoring: Configuring the Tivoli Enterprise Monitoring Server on z/OS to learn how to configure
and optimize event forwarding.
- In prior releases, the OMEGAMON XE for Mainframe Networks monitoring
agent included a list of product-provided situations that were distributed
and some subset were enabled to "Run at Startup."
If you are
performing a pristine installation, you will notice, when compared
to prior releases, that none of the product-provided situations have
been distributed and enabled to run at startup.
This change
in default behavior will decrease the initial processing overhead
related to the distribution of the product-provided situations and
assumes that you will determine which situations you want to distribute
and enable to run at startup. Product-provided situations continue
to be provided with each OMEGAMON agent and are intended to be used
as a template and a starting point to customize situations that enable
you to proactively monitor your environment. See the IBM Tivoli Monitoring: Administrator's Guide for instructions
on how to modify and rename situations to meet your monitoring needs.
Table 5 has been provided so you can compare the
list of product-provided situations that are distributed and enabled
to run at startup in V4.1 and V4.2:
Table 5. Situations autostarted in V4.1 that are no longer autostarted
Situation |
Autostarted in V4.1 |
Autostarted in V4.2? |
N3T_Appl_Backlog_Conns_Rejected |
Yes |
No |
N3T_Conn_Rnd_Trip_Time |
Yes |
No |
N3T_CPU_Pct_Critical |
Yes |
No |
N3T_CPU_Pct_Warning |
Yes |
No |
N3T_Device_Status_Inactive |
Yes |
No |
N3T_Input_Discard_Pct |
Yes |
No |
N3T_Fragmentation_Pct |
Yes |
No |
N3T_Output_Discard_Pct |
Yes |
No |
N3T_Pct_ECSA_Allocated_Stg |
Yes |
No |
N3T_Pct_IF_Err |
Yes |
No |
N3T_Reassembly_Pct |
Yes |
No |
N3T_Retransmission_Pct |
Yes |
No |
N3T_TCP_Conn_Drop |
Yes |
No |
N3T_Telnet_Pool_Usage_Critical |
Yes |
No |
N3T_Telnet_Pool_Usage_Warning |
Yes |
No |
N3V_BuffPool_Buf_Expan_Lim_Pct. |
Yes |
No |
N3V_CPU_Pct_Critical |
Yes |
No |
N3V_CPU_Pct_Warning |
Yes |
No |
N3V_Pct_ECSA_Allocated_Stg |
Yes |
No |
- All queries and workspaces that are new or modified for V4.2 of
this monitoring agent will include the qualifier (V420)
in the query and workspace descriptions. Queries and workspaces that
were part of the product before V4.2.0 will not include a qualifier.
The practice of identifying the version, release, and modification
level associated with queries and workspaces starts with this release,
but is not retrofitted to queries and workspaces that were new or
modified for prior releases.
- The SQL sample reports provided with V4.1 of this monitoring agent
are no longer provided in V4.2. Instead, eight reports are provided
in V4.2 of this monitoring agent that run under the Tivoli Common
Reporting tool.
To run the reports, install Tivoli Common Reporting V1.2 or later, provided
with IBM Tivoli Management Services. For more information
about Tivoli Common Reporting,
including information about installing and administering Tivoli Common Reporting and creating
reports, see the IBM Tivoli Common Reporting User's Guide. For more information about OMEGAMON XE
monitoring agents for zSeries® BIRT
reports, see IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Reports for Tivoli Common Reporting, part of the shared documents
in the IBM Tivoli Monitoring and OMEGAMON Information Center.
- Starting with V4.2.0, delivery and installation of the OMEGAMON II® for Mainframe
Networks component (sometimes called the CUA interface) for this OMEGAMON XE product has changed. The OMEGAMON II FMID has been
merged with the OMEGAMON XE
for Mainframe Networks and OMEGAMON
II for Mainframe Networks. The OMEGAMON II FMID has been eliminated. This change
should shorten the required installation time and simplify configuration.
The configuration guide for OMEGAMON
II has been merged into the planning and configuration guide
for OMEGAMON XE. The remaining OMEGAMON II manuals continue
to be provided with the current version of Tivoli OMEGAMON XE
for Mainframe Networks. No enhancements have been made to these documents
since V5.2.0 of the OMEGAMON
II interface.
- The Tivoli Enterprise Monitoring Server on z/OS and the OMEGAMON
XE for Mainframe Networks monitoring agent can now automatically reconnect
to the TCP/IP address space when TCP/IP is recycled. This capability
is enabled on the monitoring server Specify Advanced Configuration
Values panel with the Reconnect after TCP/IP recycle setting. If you
specify Y, and then the TCP/IP stack that is
used by the monitoring server is recycled, the monitoring server address
space reconnects to it without being recycled. If this parameter is
set to N (the default), and the TCP/IP stack
that is used by the monitoring server is recycled, the monitoring
server address space must also be recycled to reestablish TCP/IP connectivity.
This value must be set in two locations: at the monitoring server
and at the monitoring agent. See the IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide for information about setting this parameter for this monitoring
agent. See the online help for the Configuration Tool or the IBM Tivoli Management Services on z/OS: Configuring the Tivoli Enterprise Monitoring Server on z/OS for more information about
setting this value for the monitoring server on z/OS.
- Because the minimum supported version of z/OS in this release
is V1.8, the default set of TN3270 workspaces has been changed. The
TN3270 Server Sessions workspace with its linked-to workspaces
is now the default set of TN3270 workspaces, accessed by clicking
on the TN3270 node in the navigation tree. The TN3270 Server Session
Availability workspace and its linked-to workspaces (which
supported versions of z/OS before V1.8) remain in the product to maintain
compatibility with any user customizations that you might have made
to link to any of these workspaces. The TN3270 Server Session Availability
workspace can now be accessed as an alternate workspace by right-clicking
the TN3270 node in the navigation tree. The TN3270 Server Session
Availability workspace and its linked-to workspaces have been
deprecated and might not be available in a future release.