IBM® Transaction Analysis Workbench is a tool that provides a unified platform for z/OS® transactional problem management. 

Transaction Analysis Workbench enables you to look at individual z/OS subsystems or combine them into a single unified view, including the ability to replay or track the flow of the transaction within and between various z/OS subsystems.

It does not require special agent software to collect data for analysis. Instead, Transaction Analysis Workbench uses the logs and other historical data that each subsystem generates during normal transaction processing and system operations.

Features

• **Interactive on-host log analysis: **An ISPF-based log browser shows all log records in a single, consistent interface. You can browse summarized records from multiple logs merged in time sequence, then view all fields of a single record and target details of a single field. Users familiar with the ISPF editor will quickly be familiar with the ISPF-based log browser. Scroll, find text strings, bookmark records, navigate by log record timestamps, filter records based on field values and create extracts from original logs.
• **Generate batch reports: **You can generate various batch reports that are designed to help solve common transaction analysis issues. For example, combined CICS-DBCTL transaction analysis reports can help determine whether long response time is caused by problems in IBM CICS® or IBM IMS™.
• **Transaction tracking: **Connect and understand events of logs from transactions that span subsystems. In the ISPF log browser, enter TX next to any log record. The browser displays the records related to the same transaction and hides other records. It tracks the transaction across available logs to provide a cross-subsystem timeline of events and highlights delays often absent in subsystem-specific tools. Tracking can also help developers understand the behavior and interrelationships of systems.
• **Shared problem details and history: **IBM Transaction Analysis Workbench offers an optional framework for analyzing problems in sessions. A session encapsulates information about a problem and its analysis. It includes the time period, systems involved and corresponding log files. If you create a session, other users can share that session rather than creating their own. You can also tag log records of interest and add notes to the history of a session to help other users resume work on a session that you created.
• **Workflows: **When creating a session for a problem, you can optionally select a session template that describes a workflow. A workflow is a sequence of tasks for analyzing a problem. Each task can be a written instruction or JCL for a batch job. Experts can develop workflows to help other users, such as help desk staff, begin to analyze a problem or at least select the log files necessary for analysis rather than immediately assigning the problem to an expert.
• **Automated file selection: **Automated file selection eliminates the tedious process of manually locating the log data required for analysis. You specify a time period and the systems that you are interested in and IBM Transaction Analysis Workbench locate the corresponding log files and attaches them to your problem session.
• **Off-host analytics dashboards: **You can run IBM Transaction Analysis Workbench for z/OS batch jobs that forward log data to off-host analytics platforms such as the Elastic Stack or Splunk. View your log data in Kibana or Splunk dashboards that complement on-host analysis.
• **Consistent user interface: **A consistent user interface for all log records helps make it easy to extend analysis skills into unfamiliar log types and subsystems. Learn to use the log browser to analyze log records from subsystems that are familiar to you, then reuse those skills to analyze other record types.

Benefits

• **Enjoy cross-subsystem coverage: **Analyze records from multiple z/OS subsystems, including IBM CICS®, IBM Db2®, IBM IMS™, IBM MQ, SMF, IBM WebSphere® Application Server for z/OS and IBM z/OS Connect. Over 1,500 log record types.
• **Analyze logs you already collect: **Include the logs and other historical data that each subsystem already generates during normal operation. No special agent software is required.
• **Track across logs and subsystems: **See all of the events in a heterogeneous transaction, for example CICS-Db2, CICS-DBCTL, IMS-Db2, in a single consolidated view.