The following new features were introduced in Version 4.2.0 Fix
Pack 1 and Interim Features for Advanced Diagnostics:
- 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 Agent Status Attributes, SNA Collector Status Attributes, and 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 Take Action Command Attributes and 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 1 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 1. 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.