z/OS Agent troubleshooting

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.

z/OS zLocal Agent could not be started

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


These do not appear in the z/OS zLocal Agent log file, since the Agent could not be started.

Correct the DTAGTCMD parameter in the SYSIN DD of the zDC to point to the correct z/OS zLocal Agent binary location.

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

Check the job log of the affected CICS region(s) for the following message, where xxxx = the subsystem ID of the zDC that the CICS region is trying to connect to, or blank if it is trying to connect to the default subsystem that is configured with the DEFAULT(YES) parameter. It is advisable to simply search for the error message code.

ZDTP002W zDC xxxx unavailable or CICS exits disabled

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

Verify that the CICS Sensor is configured correctly, and that the monitored CICS region's configuration matches that of the CICS Sensor in the system profile.

Edit the CICS Sensor Properties for the System Profile under diagnosis.

Issue a DTAX CONF command to display the following output:

Disabled IMS Agent

If an ABEND occurs in the IMS Agent code, the recovery process produces ABEND diagnostics if possible, then disables the IMS Agent. The IMS system continue 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 20160713 10.15 VER 06.05.00 ABEND at offset 001DB6.
ZDTI033W Successful ABEND recovery, agent disabled.

Different or additional messages may 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 Agent 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 may be taken during recovery, depending on the ABEND recovery option specified or defaulted to when the IMS Agent 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 Agent 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 Agent. See IMS Agent Injection and Configuration.

When the IMS Agent becomes disabled as a result of the ABEND recovery process, it remains disabled until explcity re-enabled using the IMS Agent injection program. See IMS Agent Injection and Configuration.

When the IMS Agent becomes disabled as a result of the ABEND recovery process, you should contact support for a resolution.

Migration troubleshooting

In general, do not connect newer z/DCs to an older AppMon Server or newer Agents to older z/DCs. Newer AppMon Servers with older other components should normally be fine no matter if Agents are bootstrapped or not.

Agents started by the bootstrap part update on application restart.