CICS BAC transaction definition

About this task

Define the CICS BAC transaction so that you can activate and control CICS BAC in the CICS® region. You should define the CICS BAC transaction, even though you can start CICS BAC by including an entry in the CICS region PLTPI table.

Except for the last character, the CICS BAC transaction ID is not fixed, but KBKM is the preferred ID. If the KBK transaction prefix conflicts with existing definitions, or does not meet your installation standards, specify a different prefix, ensuring the first three characters are in the character set allowed by CICS. The fourth character of the transaction identifier must be the letter M. To avoid confusion, we recommend that you use the KBK prefix if possible. Note that you cannot change the prefix of CICS BAC program names.

You can use the CEDA command shown in Figure 1 to define the CICS BAC transaction resource definition in an active CICS region.

Figure 1. CEDA command to define the KBKM transaction in your CSD
CEDA DEFINE GROUP(cbkgroup) TRANSACTION(kbkM) PROGRAM(CBKCMNDS) 
TASKDATALOC(ANY) TASKDATAKEY(CICS)
Note:
  1. In the example shown in Figure 1, you can choose your own values for the strings shown in italics, but you are recommended to use KBKM as the transaction identifier. The transaction ID must end with the letter M.
  2. As an alternative to the CEDA commands shown in Figure 1, you can use the CICS BAC sample JCL in the SCBKSAMP data set member, CBKTRANS, to define the transaction using the CICS DFHCSDUP utility.