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:
The following new features were introduced in Version 4.2.0 Fix Pack 1 and Interim Features for Advanced Diagnostics:
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.
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.
The following new features 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 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 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.
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.
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.
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:
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:
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 |
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.