Dynatrace supports OneAgent installation on z/OS to extend PurePath transaction-based tracing to mainframe environments. OneAgent for z/OS includes the following components: CICS code module, IMS code module, z/OS Data Collection subsystem (zDC), and zRemote.

OneAgent for z/OS architecture

OneAgent deployment scheme CICS and IMS

CICS code module

CICS code module of OneAgent traces CICS transactions initiated using WebSphere MQ (Bridge or Trigger), CICS Transaction Gateway, HTTP/S, SOAP (over HTTP/S) or 3270 terminal. The CICS code module also traces DB2, DL/I and MQ API calls as well as any programs invoked using CICS Link.

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 terminal or IMS Connect API. It supports DB2, DL/I and MQ API calls tracing.


The z/OS Data Collection subsystem (zDC) controls communication between the CICS/IMS code modules of OneAgent and the zLocal component.

The zLocal component, hosted in z/OS Unix environment, runs as part of zDC. The zLocal handles the TCP/IP connection and transfers data between the mainframe and the distributed Dynatrace component called zRemote.


The zRemote is a distributed Dynatrace component that can run in a 64 bit Windows or Linux environment. The zRemote processes the data from CICS/IMS code modules channelled by zLocal and relays the aggregated data to Dynatrace ActiveGate.

The zRemote offloads much of the OneAgent processing from the CICS/IMS code modules thereby reducing the MSU load incurred in instrumenting mainframe applications.