Dynatrace OneAgent for z/OS is a subset of our full OneAgent. It extends PurePath transaction-based tracing to a mainframe environment.
OneAgent for z/OS includes the following individual components:
CICS code module
The CICS code module of OneAgent can either start new PurePaths for specific transaction codes or link CICS transaction PurePaths to distributed PurePaths for transactions initiated using WebSphere MQ(Bridge or Trigger), CICS Transaction Gateway, HTTP(S) SOAP (over HTTP) or 3270 TX Transactions. It supports DB2, DL/I and MQ API calls tracing, as well as any programs invoked using CICS LINK or LE dynamic call. Linked PurePaths are also provided with child transaction details started for DPL LINK or START TRANSACTION requests within a PurePath.
You need to install OneAgent into every CICS region that you want to monitor. It includes a PLT program that initiates at CICS startup, and the code module program that captures various events and forwards them to the z/OS Data Collection subsystem.
IMS code module
The IMS code module of OneAgent traces IMS transactions submitted from IMS MQ Bridge or MQ Trigger Monitor, IMS TM Resource Adapter, IMS SOAP Gateway, 3270 TX Transactions or IMS Connect API. It supports DB2, DL/I and MQ API calls tracing, as well as any programs invoked using LE dynamic call. You may also need to modify your IMS Connect Job JCL to allow IMS Connect to load the Dynatrace exit HWSTECL0.
You need to inject OneAgent into the Control Region of each IMS system where you want to capture PurePaths. OneAgent captures data on various IMS transaction processing events and forwards that information to the zDC.
See Deploy OneAgent on IMS for details.
z/OS data collection subsystem (zDC)
The z/OS Data Collection subsystem (zDC) controls communication between the zLocal and CICS and IMS code modules of OneAgent. You can enter Operator start, stop, and modify commands from a system console to control the zDC and the lifecycle of the zLocal.
The zLocal and zRemote handle the TCP/IP connection between the mainframe and the Dynatrace ActiveGate. The zLocal installs on the mainframe and passes data to the zRemote, reducing CPU consumption on z/OS.
The zLocal can't directly connect to an Dynatrace ActiveGate without first going through a zRemote. Using the zRemote reduces CPU consumption on z/OS by offloading most of the OneAgent processing.
The zLocal only transfers data to the zRemote, which can run on Windows or Linux (64-bit OS only).
The zRemote is an aggregation and data processing component that installs in the distributed environment and extends the zLocal. The zRemote offloads much of the Oneagent processing from the "Code Modules", reducing the MIPS load incurred in instrumenting mainframe applications.
The zRemote should only service one zDC and its zLocal (zDC). It is possible to run more than one zDC zLocal pair per LPAR.
See Deploy OneAgent on zDC for details.
SMP/E install of the OneAgent for z/OS
Deploy OneAgent on IMS
Deploy OneAgent on z/OS CTG and IMS SOAP gateway
Deploy OneAgent on CICS
Deploy OneAgent on zDC
Deploy OneAgent on zRemote
Deploy OneAgent on multiple instances of zDC/zRemote
Verify the installation
Troubleshoot OneAgent installation on z/OS