Install the CICS code module
With the CICS code module, you can get observability for your CICS transactions and programs including IBM MQ and database calls.
| Observability for | Including |
|---|---|
CICS transactions | Transactions initiated using
|
CICS programs |
|
Database calls | Database calls with their SQL statements from CICS to DB2 and IMS DB via the DL/I access method |
File access | File access from CICS via the VSAM and BDAM access methods. |
Analyze the performance of your transactions end-to-end using the Service flow.
Use the PurePath distributed traces to drill down to the code level and to optimize your programs.
Understand exceptions in the context of your transactions down to the DB2 database layer.
Davis® AI automatically pinpoints the root cause of problems and assesses their user impact so that you can prioritize mitigation strategies and reduce the mean time to repair.
Analyze failures with exception details in the context of transactions.
Installation
The CICS code module includes a PLT program that initiates at CICS startup. This program uses hooks to instrument CICS terminal and application owning regions, creating events of interest. It forwards monitoring data to the zDC subsystem via shared buffers.
You need to install the CICS code module in every CICS region you want to monitor. To update your CICS code module without restarting the CICS region, see Update the CICS code module without region restart.
You need to add the z/OS Java code module to each CICS Transaction Gateway you want to monitor.
CICS library definition
You can dynamically add the load library as a CICS library definition in the CSD. The CEDA definition is in SZDTSAMP member CICRDO. You can find it in the example in the next section.
If you don't want to use the CICS Library definition, you need to add the following PDS (or its contents) to the DFHRPL concatenation:
// DD DISP=SHR,DSN=<hlq>.SZDTLOADWhere <hlq> is the high-level qualifier you set during Download z/OS product datasets.
Dynatrace CICS programs and transaction
The sample CICS definitions below install programs and a transaction that are required by the CICS code module. A copy of these definitions can be found in SZDTSAMP member CICRDO, which is provided for use with the batch RDO utility DFHCSDUP.
We recommend to use these transaction and group names, but you can change them in accordance with your installation policies. Coordinate the group name and group list name with your CICS administrator. Replace XYZLIST with the name of your group list (GRPLIST).
CICS startup program list table
Add the CICS startup program (ZDTPLT) after the DFHDELIM entry in your PLTPI source code and assemble the table.
This step is optional for test installations because the DTAX transaction can be used instead to enable the code module after CICS initialization. We recommend that you place the ZDTPLT entry immediately before the TYPE=FINAL specification.
The JCL procedure DFHAUPLE in CICSHLQ.SDFHINST(DFHAUPLE) can be used to build the PLTPI table.
The PLT startup program (ZDTPLT) initializes the CICS code module's exit work area, which CICS obtains on its behalf. Products such as Compuware Xpediter/CICS may be configured to enforce strict storage access controls and may abend ZDTPLT and prevent the CICS code module from starting unless it is excluded from these controls. If you use the Xpediter/CICS global storage protection feature, add a monitor exceptions entry to the XDDBPINP DD in the CICS region JCL to exclude ZDTPLT*. For example:
DBPA 17.02 TRAN=*,PROGRAM=ZDTPLT*,CSECT=*CICS shutdown program list table
Add the CICS shutdown program (ZDTPLTSD) before the DFHDELIM entry in your PLTSD source code and assemble the table.
We recommend to place the ZDTPLTSD entry immediately after the TYPE=INITIAL specification.
The JCL procedure DFHAUPLE in CICSHLQ.SDFHINST(DFHAUPLE) can be used to build the PLTSD table.
Connect CICS code module to a zDC subsystem
The PLT startup program (ZDTPLT) automatically connects to the default zDC subsystem at CICS region initialization.
If multiple zDCs subsystems are running, it connects to the zDC that specifies DEFAULT(YES), unless an INITPARM override parameter in the CICS SYSIN parameters specifies that it must connect to a zDC with a particular name:
INITPARM=(ZDTPLT='MEPC,<option>'),<option> sets the log level for the CICS code module; see Logging.
To verify the connectivity between the CICS code module and the zDC subsystem, send a ping message.
Customization
CICSPlex name grouping
You can group CICS regions belonging to the same CICSPlex into a single process group. To do so
- In the Dynatrace menu, go to Settings > Mainframe > Transaction monitoring.
- Turn on Group CICS regions that belong to the same CICSPlex.
- Add
MASPLTWAIT(YES)to your LMAS parameter. It instructs the CICS region to wait for the CICSPlex to become available before proceeding. If the CICSPlex isn't available, the code module can't consider it. - optional The
MASINITTIME(10)timeout interal defaults to 10 minutes. You can customize it in the range of 5 minutes to 59 minutes.
If you enabled CICSPlex name grouping after the CICS region is up, you need to run the DTAX transaction DTAX DISABLE and DTAX ENABLE.
CICS web services support
The CICS code module can trace the CICS web services invoked through a SOAP request or a JSON request (non-Java JSON pipeline).
To trace the CICS web service provider programs that are invoked by DFHPITP from CICS SOAP pipelines or invoked by DFHPIJT from non-Java JSON pipelines, update the service provider pipeline definitions for the services that should be traced.
Add a <handler> stanza that invokes the supplied ZDTSOAPH header program.
<?xml version="1.0" encoding="EBCDIC-CP-US"?>
<provider_pipeline xmlns="http://www.ibm.com/software/htp/cics/pipeline">
<transport>
<default_http_transport_handler_list>
<handler>
<program>ZDTSOAPH</program><handler_parameter_list/>
</handler>
</default_http_transport_handler_list>
</transport>
<service>
<terminal_handler>
<handler>
<program>DFHPIJT</program><handler_parameter_list/>
</handler>
</terminal_handler>
</service>
</provider_pipeline>You need to add a <headerprogram> stanza that invokes the supplied ZDTSOAPH header program.
For example, add the sample stanza below to the cics_soap_1.1_handler section after any existing header program sections.
<headerprogram>
<program_name>ZDTSOAPH</program_name>
<namespace>*</namespace>
<localname>*</localname>
<mandatory>true</mandatory>
</headerprogram>To trace outbound SOAP requests that originate within CICS transactions that are traced by a CICS code module, add the previous <headerprogram> stanza to the service requester pipeline definitions of those SOAP services that should be traced. Outbound SOAP requests that occur within CICS transactions that aren't traced are ignored. However, tracing isn't limited to requests from SOAP programs that act as CICS SOAP service providers.
Route DTAX messages using TDQueue
To optionally route DTAX messages to Dynatrace TDQueue (Transient Data Queue), use the ZDTQ resource definition provided above in your CICRDO member.
By default, the queue remains closed through the OPENTIME(DEFERRED) attribute. You must manually open it by using the CEMT INQUIRE|SET TDQUEUE command. To default the queue to open at install time, use the OPENTIME(INITIAL) attribute.
Logging
You can control the CICS code module log level either by using the DTAX transaction or by specifying an optional INITPARM at CICS region startup.
INITPARM=(ZDTPLT='MEPC,<Option>'),<Option> sets the logging level for CICS code module. Accepted values are:
FINE|Ffor fine logging. We recommend to enable it only when the CICS code module has difficulties during startup.INFO|Ifor info logging. This is the default.WARNING|Wfor warning messages logging.SEVERE|Sfor severe messages logging.
Example:
INITPARM=(ZDTPLT='MEPC,SEVERE'),There are two different sets of CICS logs:
- One set of messages occurs when the DTAX transaction issues the
DISABLEandENABLEcommands. These messages are written to the CICS CSMT Transient Data Queue(usually written to MSGUSR). View these messages in the CICS job spool. DTAX also writes a set of messages to the CEEOUT SYSOUT statement when errors occur in the connection between the zDC and the DTAX transaction. View these messages in the CICS Job spool. As long as the DTAX transaction can connect to the zDC, it logs its messages to the zRemote. - The CICS code module monitoring transaction activity routes its log messages to the zDC, and subsequently to the zRemote. The log shows if any corrupted distributed traces, timeouts, or other errors occurred. You may also see some statistical information in these logs.
You can access the CICS logs via the zRemote logs.
Update without region restart
To update your CICS code module to a newer version without restarting the region
- Download z/OS product datasets and follow the instructions to get the newest version.
- Disable the DTAX transaction in the CICS region with the
DISABLEcommand. - Copy the CICS code modules in the
SZDTLOADdataset into the DynatraceDFHRPLdataset defined to your CICS region. - Use the CICS command
CEMT I PROG(ZDT*)to display the CICS code modules. Use theSET PROG(ZDT*) NEWCOPYcommand to tell CICS a new version of each program will be used. - Enter CICS command
CEDA INSTALL GROUP(DTA1)to install the new code module to the CICS region. - Enable the DTAX transaction with the
ENABLEcommand. Verify that the new CICS code module version is displayed on the DTAX panel.