Repositories

Repositories are the data sets where Transaction Analysis Workbench stores data related to transaction analysis. Users can share repositories. Some repositories can be shared with other products.

The following figure illustrates the repositories that Transaction Analysis Workbench can use and the products that can share them.

Figure 1. Transaction Analysis Workbench repositories
This image is described in the surrounding text.

Transaction Analysis Workbench can create, write to, and read from all of these repositories.

All repositories are optional, depending on which features of Transaction Analysis Workbench you use.

The repositories are divided into two categories: problem analysis and system definition.

Problem analysis repositories

Problem analysis repositories contain information that Transaction Analysis Workbench uses to help you analyze problems. There are two problem analysis repositories:

Session repository
Contains information about each problem session. Also contains session templates.

This repository is required if you use sessions (ISPF dialog option 1 Sessions). Using sessions is the recommended method for analyzing transactions. If you always use your personal ad hoc list of log files (ISPF dialog option 4 Process) instead of sessions, then you do not need this repository.

This is the only repository that is exclusive to Transaction Analysis Workbench.

Control repository
Contains controls: filters, forms, and object lists. This repository can be shared with IMS Problem Investigator, where it is known as the control data set (CDS).

System definition repositories

System definition repositories contain system definitions that Transaction Analysis Workbench uses for automated log file selection. For example, an IMS system definition specifies the names of the RECON data sets for that IMS system.

You need these repositories if you want to use the Transaction Analysis Workbench ISPF dialog to generate JCL for the automated file selection utility.

There are two system definition repositories:

IMS system definition repository
Can be shared with IMS Performance Analyzer, where it is known as the permanent ISPF table library, and IMS Problem Investigator, where it is known as the IMS PA profile library.

You need this repository to automate selection of IMS logs and IMS Connect Extensions journals.

CICS®, DB2®, IBM® MQ, and MVS Image system definition repository
Can be shared with CICS Performance Analyzer, where it is known as the CICS Performance Analyzer repository.

Transaction Analysis Workbench only uses CICS Performance Analyzer shared system definitions, which are saved in HDB registers, not personal system definitions, which are saved in each CICS Performance Analyzer user's personal profile library. You can use CICS Performance Analyzer to take-up (copy) personal system definitions into shared system definitions.

You need this repository to automate selection of DB2 logs and SMF files.

Sharing repositories between products and users

Sharing repositories between products is optional. When you use the Transaction Analysis Workbench ISPF dialog, you can either refer to existing repositories created by other products, or you can specify new data set names. The first time that you attempt to access a new repository, the ISPF dialog displays a panel that enables you to allocate the data set. Alternatively, to allocate these data sets without using the ISPF dialog, use the JCL member FUWALOCR in the sample library SFUWSAMP.

Sharing repositories between users is also optional. Each Transaction Analysis Workbench ISPF dialog user can specify a different set of repositories.

Sharing repositories has advantages. For example:

  • Sharing a session repository between users enables collaboration. Users can take advantage of the fact that another user has already registered a session for a problem, selected the corresponding log files, and written notes about their analysis.
  • Sharing system definition repositories between users and products avoids duplication of data entry. For example, if an IMS Performance Analyzer user has already defined an IMS system, including details of its related RECON data sets, then a Transaction Analysis Workbench user can reuse that definition to perform automated file selection of the IMS logs.

Your organization must decide how and whether to share repositories. Each user of the Transaction Analysis Workbench ISPF dialog must specify appropriate repository data set names under option 0.2 Repositories.

The first time each new user starts the Transaction Analysis Workbench ISPF dialog, the dialog searches the user's ISPF profile library for members created by the dialogs of other products that can share repositories. The Transaction Analysis Workbench ISPF dialog uses the information in these members to fill in the repository data set names under option 0.2 Repositories.