Created:  | Updated: 


z/IRIS enables the JDBC observability for JDBC calls processed by IBM Db2 for z/OS systems Instana APM. Refer to Distributed Db2 for z/OS observability for more information about how z/IRIS traces JDBC requests.

Instana APM traces, created by z/IRIS, are enriched with custom tags that make searching and filtering traces easy for DevOps and analysis teams.


Requirement

z/IRIS instrumentation should be activated with Instana Java agents to enable Distributed Db2 for z/OS tracing. Refer to How to Enable system-wide Instana instrumentation for more information about activating z/IRIS instrumentation.

Db2 Accounting calls (IFCID 3)

Db2 Accounting call tags provide information about resource consumption and performance for JDBC transactions (commits/rollbacks). CPU and zIIP processor time, elapsed time (duration), service units and more are extracted and presented within the context of the JDBC application creating the mainframe workload.

Click on the image to enlarge

Instana Db2 Accounting screenshot

Metadata

duration 

IFCID 3 In-Db2 elapsed time.

endpoint

Db2 subsystem that processed the JDBC request

service

Db2

Db2 Deadlock calls

Db2 Deadlock span that describes the system and Db2 server where the deadlock occurred

Click on the image to enlarge

Instana Db2 Deadlock screenshot

Metadata

duration

Not set and therefore < 1ms is observed.

endpoint

Db2 subsystem name that detected the deadlock

service

Db2

Db2 deadlock resource name (RNA) child spans

Each child span represents a Db2 RNA that was listed in the IFCID 172 Db2 deadlock trace. For more information about how z/IRIS constructs the call name, click here.

Click on the image to enlarge

Db2 deadlock waiter and holder child spans

Db2 waiter and holder spans provide details regarding the JDBC connections that are holding up (i.e. blocking) or waiting for the Db2 resource, including Db2 LUWIDs, network address and Instana APM trace ids. 

Click on the image to enlarge

Db2 Deadlock participants

For more information about Db2 Deadlock Participant traces, click here.

It is possible to have JDBC SQL calls that have participated in multiple deadlock events.

Click on the image to enlarge

Instana Db2 Deadlock participant screenshot

Db2 Performance calls

For more information about Db2 Performance traces, click here.


click to enlarge image

Metadata

duration

Not set and therefore < 1ms is observed.

endpoint

Db2 subsystem that processed the JDBC requests

service

Db2


z/IRIS distributed Db2 for z/OS deadlock events

z/IRIS will also create an Instana event for each Db2 z/OS deadlock trace (IFCID 172).

Click on the image to enlarge

Event title

Deadlock event detected on db2-subsystem-name involving Db2 resources at db2.zos.deadlock.timestamp, where:

db2-subsystem-name

The Db2 Subsystem ID on z/OS, where the deadlock occurred.

n

The number of Db2 resources impacted by the deadlock.

db2.zos.deadlock.timestamp

The timestamp at which Db2 for z/OS detected the deadlock.

Event details

Complete deadlock details can be found at in the following call: trace.id = trace-id.

Use the Instana Analyze dashboard to search for traces with the trace.id provided in the deadlock event details.