CEDA DEFINE PROCESSTYPE

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.

Note:
Records for multiple process-types can be written to the same repository data set.

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.

Figure 37. PROCESSTYPE definitions, FILE definitions, and repository data sets
 The picture shows the relationships between PROCESSTYPE definitions, FILE definitions, and BTS data sets. It shows four PROCESSTYPE definitions (A through D), three FILE definitions (1 through 3), and two repository data sets (X and Y). PROCESSTYPE A relates to FILE 1, which relates to repository X. PROCESSTYPEs B and C both relate to FILE 2, which relates to repository Y. PROCESSTYPE D relates to FILE 2, which relates to repository Y.

DEFINE panel

Figure 38. The DEFINE panel for PROCESSTYPE
 Processtype  ==>
  Group        ==>
  DEScription  ==>
 
INITIAL STATUS
 STAtus       ==> Enabled           Enabled | Disabled
DATA SET PARAMETERS
 File         ==>
AUDIT TRAIL
 Auditlog     ==>
 Auditlevel   ==> Off                Off | Process | Activity | Full

Options

AUDITLEVEL({OFF|PROCESS|ACTIVITY|FULL})
specifies the initial level of audit logging for processes of this type. If you specify any value other than OFF, you must also specify the AUDITLOG option.
ACTIVITY
Activity-level auditing. Audit records will be written from:
  1. The process audit points
  2. The activity primary audit points.
FULL
Full auditing. Audit records will be written from:
  1. The process audit points
  2. The activity primary and secondary audit points.
OFF
No audit trail records will be written.
PROCESS
Process-level auditing. Audit records will be written from the process audit points only.

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.

AUDITLOG(name)
specifies the name of a CICS journal to which audit trail records will be written, for processes of this type and their constituent activities. The name can be up to eight characters long. If you do not specify an audit log, no audit records will be kept for processes of this type.
DESCRIPTION(text)
You can provide a description of the resource you are defining in this field. The DESCRIPTION text can be up to 58 characters in length. There are no restrictions on the characters that you may use. However, if you use parentheses, ensure that for each left parenthesis there is a matching right one. For each single apostrophe in the text, code two apostrophes.
FILE(name)
specifies the name of the CICS file definition that will be used to write the process and activity records of this process-type to its associated repository data set. The name can be up to eight characters long. The acceptable characters are A-Z 0-9 $ @ and #. Lowercase characters are converted to uppercase.

You must specify the FILE option.

PROCESSTYPE(name)
specifies the name of this PROCESSTYPE definition. The name can be up to eight characters in length. The acceptable characters are A-Z a-z 0-9 $ @ # . / -_ % & ? ! : | " = ¬ , ; < >. Leading and embedded blank characters are not permitted. If the name supplied is less than eight characters, it is padded with trailing blanks up to eight characters.
STATUS({ENABLED|DISABLED})
specifies the initial status of the process-type following a CICS initialization with START=COLD or START=INITIAL. After initialization, you can use the CEMT SET PROCESSTYPE command to change the status of the process-type. The status of the process-type following a restart is recovered to its status at the previous shutdown.
DISABLED
Processes of this type cannot be created. An EXEC CICS DEFINE PROCESS request that tries to create a process of this type results in the INVREQ condition being returned to the application program.
ENABLED
Processes of this type can be created.

Related concepts
What are CICS business transaction services?
Related tasks
Defining the LRQ file to the CSD
Defining repository files to the CSD
[[ Contents Previous Page | Next Page Index ]]