Free trial

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.

Note

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 may 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.

ZDTP002W zDC yyyy 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 code module is configured correctly, and that the monitored CICS region's configuration matches that of the CICS Sensor in the system profile.

In the DESK UI select Settings then select Server-side service monitoring. Now under Server-side service monitoring select Deep monitoring. Under Deep Monitoring select New OneAgent features. Hit the right tab arrow (>) until you see the feature(s) you want.

Disabled IMS code module

If an ABEND occurs in the IMS code module code, the recovery process produces ABEND diagnostics if possible, then disables the IMS code module. 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 20170713 10.15 VER 07.02.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 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 may 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 Deploy 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

To ensure proper migration:

  • Do not connect newer CICS and IMS code modules of OneAgent to older z/DCs.

DESK ActiveGate always supports OneAgents of earlier versions. with older other components should normally be fine no matter if code modules are bootstrapped or not.

Agents started by the bootstrap part update on application restart.