Using the CICS® business transaction services (BTS) API, you can define and execute complex business applications called processes. A process is represented in memory as a block of storage containing information relevant to its execution. It also has associated with it at least one additional block of information called an activity instance. When not executing under the control of the CICS business transaction services domain, a process and its activity instances are written to a data set known as a repository.
You can categorize your BTS processes by assigning them to different process-types. This is useful, for example, for browsing purposes. The activities that constitute a process are of the same process-type as the process itself.
A PROCESSTYPE definition defines a BTS process-type. It names the CICS file which relates to the physical VSAM data set (repository) on which details of all processes of this type (and their activity instances) are to be stored.
You may want to record the progress of BTS processes and activities for audit purposes, and to help diagnose errors in BTS applications. If so, you can name the CICS journal to which audit records are to be written, and the level of auditing that is required, for processes of the specified type.
Figure 37 shows the relationship between PROCESSTYPE definitions, FILE definitions, and BTS data sets. Notice that multiple PROCESSTYPE definitions can reference the same FILE definition; and that multiple FILE definitions can reference the same BTS data set.
Processtype ==> Group ==> DEScription ==> INITIAL STATUS STAtus ==> Enabled Enabled | Disabled DATA SET PARAMETERS File ==> AUDIT TRAIL Auditlog ==> Auditlevel ==> Off Off | Process | Activity | Full
For details of the records that are written from the process, activity primary, and activity secondary audit points, see Specifying the level of audit logging.
You must specify the FILE option.