Resource definition for BTS
You can use BTS API commands to define most BTS resources such as processes, activities, events, and containers at run time. However, you must define some BTS resources on the CICS® system definition file (CSD).
The only BTS resources that must be defined on the CICS system definition file (CSD) are as follows:
- 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 might want to use the PROCDEF object if you are using BTS in a sysplex, with routing of processes and activities controlled by CICSPlex SM. For information about BAS, see Administering BAS.
- 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 FILE attributes. BTS uses two kinds of data set:
- Local request queue data set. See Local request queue data set.
- Repository data sets, on which process and activity records are stored. See 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 JOURNALMODEL resources.