This document covers the following topics:
An upgrade installation from Version 8.2 to Version 9.0 of the Application Monitoring Data Collector (in the same directory) is not supported. If you want to install Version 9.0, you must first uninstall Version 8.2 in the current directory, or you have to install Version 9.0 into a different directory. See also Installation for Application Monitoring.
It is now possible to monitor distributed application scenarios that make use of the following components:
EntireX Adapter on UNIX and Windows
Natural RPC Client on z/OS, UNIX and Windows
Cobol RPC Client on z/OS
Natural RPC Server on UNIX and Windows
See Components Which Support Application Monitoring.
Application monitoring is now possible in scenarios where the EntireX Adapter is used instead of the EntireX Broker. See Setting Up the EntireX Adapter.
The following connection types of the EntireX Adapter support application monitoring:
EntireX RPC Connection
EntireX Direct RPC Connection
EntireX RPC Listener Connection
EntireX Direct RPC Listener Connection
IMS Connect Connection
CICS ECI Connection
See Setting Up the EntireX Adapter and KPI Definitions for Application Monitoring.
Three different types of application monitoring scenarios are now supported:
CICS ECI Application
IMS Connect Application
RPC Application
Each scenario has its own event map with a specific set of KPIs. See KPI Definitions for Application Monitoring.
The RPC application scenario contains the previous KPI definitions for application monitoring that have been revised and renamed.
It is now possible to monitor failed requests. For each application monitoring scenario as defined above, an event map exists with new KPIs:
CICS ECI Error
IMS Connect Error
RPC Error
Three performance-optimized versions of the application monitoring MashApp are now available for the following scenarios: RPC, CICS ECI and IMS Connect. The MashApps now support error monitoring. MashZone 9.0 is required for these MashApps. See Application Monitoring MashApps.
Separate KPIs are now available for monitoring the length of the RPC request and the length of the RPC reply.
A Natural RPC server on a mainframe now delivers for database calls against an Adabas server the KPIs Time - DB Transport and Time - DB Calls.
The following products are supported as of this version:
Natural Connection
Natural for DB2
Natural for VSAM
Natural SQL Gateway
zIIP Enabler for Natural
The following features of already supported products are supported as of this version:
Natural
Natural for Adabas
Natural Nucleus
Natural Optimize
Natural RPC
A new chapter Defining a Common Action for All
Rules is available. It describes how you can add an action
to your Optimize rules which triggers a web service action in case of a rule
violation. Sample Natural subprograms are provided in the SYSEDM
library which process the information from the web service and perform an
appropriate action.
Sample MashZone MashApps for infrastructure monitoring are provided in Empower, as a download component for Optimize for Infrastructure. MashApps for the following product components are available:
Adabas Server
EntireX Broker
Natural Security
Natural zIIP (zIIP Enabler for Natural)
The MashApp "Monitor Overview v1.1" provides links to the infrastructure monitoring MashApps and can be used as a starting point. For further information, see Infrastructure Monitoring MashApps.
PROFILES Text
MemberYou can now add inline comments to the PROFILES text
member. When the profile settings are read, any entries after the inline
comment indicator (/*) are ignored. See
Editing the
Profile in Adabas/Natural Data Collector
Profile.
SYSPLEX ParameterThe default for the sysplex environment is now defined in Optimize.
However, when the SYSPLEX parameter is set in the
PROFILES text member, it overwrites the Optimize settings. See
Sysplex
Environment in Adabas/Natural Data Collector
Profile.
With Natural 8.2.1 on z/OS and Natural 8.2.3 on z/VSE, the Natural Optimize Monitor Buffer Pool has been introduced, which collects statistical data of Natural components. The Natural Optimize Monitor Buffer Pool is able to monitor all component instances running in one LPAR. Therefore, only one batch RPC server per LPAR is required for all of these components.
The following table lists the products and components which use the Natural Optimize Monitor Buffer Pool. Some of these products have been monitored in previous versions through a proprietary interface. These products must now use the Natural Optimize Monitor Buffer Pool if the Natural version supports the Natural Optimize Monitor Buffer Pool in general. For more information, see Natural in Product-Specific Environment Configuration.
| Product Component | Proprietary Interface |
|---|---|
| Natural Buffer Pool (Mainframe) | Yes |
| Natural CICS | Yes |
| Natural CICS - Thread Group | Yes |
| Natural Connection | No |
| Natural Development Server | Yes |
| Natural Editor (Software AG Editor) | Yes |
| Natural for Adabas | No |
| Natural for DB2 | No |
| Natural for VSAM | No |
| Natural Nucleus | No |
| Natural Optimize | No |
| Natural RPC | No |
| Natural Security | Yes |
| Natural SQL Gateway | No |
| Natural Swap Pool | Yes |
| Natural Web I/O Interface - Server | Yes |
| Natural zIIP (zIIP Enabler for Natural) | No |
A batch RPC server can now monitor all Natural Roll Servers running in the same LPAR.
The aggregation type for the KPI "NOPVersion" has been corrected to "last value". Previously, it was "sum".
The new version will load the new definitions which will result in a loss of historical readings of monitoring data for the Entire Operations component.
This version of Optimize for Infrastructure already supports the product component Natural for VSAM. Natural for Mainframes Version 8.2.3 Fix 2, however, does not yet support monitoring of Natural for VSAM. This will be provided with a later Natural fix.