Troubleshoot OneAgent installation on z/OS

This page describes various techniques for troubleshooting and for collecting the necessary data for Customer Support.

Component set up verification

The following sections describe how to identify set up issues.

zLocal could not be started

Check the job log of the zDC for any of the following error messages.


These do not appear in the zLocal log file, since the zLocal could not be started.

System under diagnosis (CICS region) could not connect to the zDC

Check the job log of the affected CICS regions for the following message, where yyyy is the subsystem ID of the zDC that the CICS region is trying to connect to. It might be blank if the CICS region is trying to connect to the default subsystem that is configured with the DEFAULT(YES) parameter. We recommend to simply search for the error message code.

ZDTP004W zDC yyyy unavailable

Verify that the zDC with that subsystem ID is started. If so, then try to issue a DTAX Enable command to re-enable the connections.

Expected queues and/or transactions (including SOAP and CTG transactions) are not being monitored

In the Dynatrace UI,

  1. Go to Settings > Server-side service monitoring > Deep monitoring > Troubleshooting.
  2. Enter "z/OS" in the "Filter for…" text box to filter the z/OS features.
  3. Expand Details to verify if the feature you want to monitor has "Capturing On".

Disabled IMS code module

If an ABEND occurs in the IMS code module, the recovery process produces ABEND diagnostics if possible, then disables the IMS code module. The IMS system continues to function. When this occurs a series of WTO messages are written to the system log for the IMS Control Region and/or IMS dependent region. A sample normal message set follows:

ZDTI032W Recovery routine entered.
ZDTI036W ZDTIII14 BDCSBK00 20170713 10.15 VER 07.02.00 ABEND at offset 001DB6.
ZDTI033W Successful ABEND recovery, agent disabled.

Different or additional messages might be issued if abnormal conditions are encountered by the recovery process, such as when dynamic storage cannot be obtained, retry is not permitted, or no SDWA was passed. All of the messages related to the ABEND recovery process are documented in the z/OS code module messages section.

A Software (SFT) Error Record further describing the ABEND is usually written to the z/OS system SYS1.LOGREC data set. You should run the z/OS EREP utility program to print the Software (SFT) Error Record associated with the ABEND.

Optionally, an SVC dump might be taken during recovery, depending on the ABEND recovery option specified or defaulted to when the IMS code module was injected. The default action is to not capture an SVC dump when ABEND recovery is driven. This option can be specified as a parameter when the IMS code module is initially injected, or specified in conjunction with the Modify or Enable function parameters to toggle dump capture during recovery on or off for a previously injected IMS code module. See Install OneAgent on IMS for more details.

When the IMS code module becomes disabled as a result of the ABEND recovery process, it remains disabled until explicitly re-enabled using the IMS code module injection program contact support for a resolution.

Migration troubleshooting

Ensure CICS and IMS code module version is less than or equal to zRemote version. Do not connect newer CICS and IMS code modules of OneAgent to older zRemote. Following is a sample message in the zRemote log when a IMS code module version is incompatible with the zRemote version.

severe  [native] IMS14CR1[asid = 108] is trying to initialize with an invalid protocol version number :