Created , Updated
z/IRIS enables observability for JDBC calls processed by IBM Db2 for z/OS systems. Users gain access to performance metrics and processing information related to JDBC call processing. z/IRIS will also create events with information about errors that occured on the mainframe. These events can be integrated with alerting rules, so that teams are always aware of any situations affecting business services.
z/IRIS creates Db2 z/OS traces from SMF record types 101 and 102.
Supported Db2 IFCIDs
Accounting traces provide data that helps with capacity planning and tuning.
Db2 Deadlock, Db2 Deadlock Participant
Each deadlock event, detected by the Db2 z/OS manager, creates a deadlock records. It identifies access threads and resources impacted by the deadlock. Additional information about thread locking behaviour is helpful for RCA.
Performance traces provide performance information per SQL request.
Activate these traces with discretion, as a system performance penalty is inevitable.
Db2 Accounting traces
z/IRIS processes IFCID 3 data into APM traces or spans. Db2 Accounting traces contain system identifiers, duration information and metadata about resource consumption and performance like: CPU and zIIP processor time, elapsed time (duration) and latency/wait time. This metadata can be included in capacity planning or application tuning analysis.
Db2 Deadlock traces
z/IRIS creates a deadlock trace from IFCID 172 data. The erroneous deadlock trace provides:
the timestamp of the event,
has a duration of <1ms ,
the number of database resources impacted by the deadlock
the Db2 and z/OS system names, where the deadlock occurred.
Db2 deadlock resource name span
Information about each Db2 RNA (resource name) impacted by the deadlock is available through additional child spans, that are enriched with metadata.
The call name provides the RNA locked in the deadlock event. Possible values include:
collection.id = collectionId
where smallResource could point to one of the following:
Db2 Deadlock participant
z/IRIS will detect whether JDBC applications, involved in a deadlock event, are instrumented by APM Java agents. Instrumented applications impacted by the same deadlock will have an additional Db2 Deadlock Participant call in the trace tree, that provides links to information about the Db2 resources and other applications impacted by the same deadlock event.
Db2 Performance calls
The performance class IFCIDs are expensive to activate and should be used for specific analysis purposes only.
z/IRIS creates the following APM traces using Db2 for z/OS performance class IFCIDs:
Db2 Performance: End Sql QW0058SN
Db2 Performance: Fetch start QW0059SN
Db2 Performance: QW0060ST start QW0060SN
Db2 Performance: QW0061ST start QW0061SN
Db2 Performance: QW0062ST start QW0062SN
Db2 Performance: SQL statement
Db2 Performance: QW0064ST start QW0064SN
Db2 Performance: Open Cursor start QW0065SN
Db2 Performance: Close Cursor start QW0066SN