Resource definition for BTS

Most BTS resources (processes, activities, events, and containers) are defined at run time, using BTS API commands. The only BTS resources that must be defined on the CICS® system definition file (CSD) are:

Process-types
See CEDA DEFINE PROCESSTYPE.
Note:
As an alternative to using RDO CEDA DEFINE PROCESSTYPE commands to define your process-types, you can use the CICSPlex® SM Business Application Services (BAS) PROCDEF object. You may want to do this if you are using BTS in a sysplex, with routing of processes and activities controlled by CICSPlex SM. For information about BAS, see the CICSPlex System Manager Managing Business Applications manual.
The BTS data set files
The CICS files that relate to the physical VSAM data sets used by BTS must be defined to CICS file control in the standard way, as described in the CICS Resource Definition Guide.

BTS uses two kinds of data set:

Local request queue data set
is described in Local request queue data set.

For information about how to define the LRQ to the CSD, see Defining the LRQ file to the CSD.

Repository data sets
on which process and activity records are stored, are described in Repository data sets.

For information about how to define repository files to the CSD, see Defining repository files to the CSD.

Audit logs
The journals used for auditing purposes must be defined to the CICS log manager in the standard way, as described in the CICS Resource Definition Guide.

The rest of this section contains:

[[ Contents Previous Page | Next Page Index ]]