Preparing CICS regions for CICS BAC

The CICS BAC components that you need in your CICS® regions consist of:

You might also want to take advantage of CICS TS features that allow you to activate automatically CICS BAC support during CICS initialization and terminate it automatically during CICS shutdown processing.

Checklist

The following checklist summarizes the main steps described in the following topics:

Adding CICS BAC load modules to CICS

Ensure the CICS BAC load modules are available to your CICS region before attempting to activate CICS BAC. The load modules are installed in the SCBKLOAD load library when you installed CICS BAC. The CICS BAC Program Directory provides information about the location and name of the load library. To make the load modules available to CICS, you can:

Although the first method is recommended, it requires you to restart the CICS region after you've modified the JCL. The second method allows you make the CICS BAC modules available without restarting CICS. However, keeping product load modules in their respective data sets is normally recommended

Defining the required CICS BAC resource definitions

CICS BAC requires the following CICS resource definitions to enable CICS BAC support in a CICS region:

You can use the CICS CEDA transaction to define the above, as shown in the examples later in this section. Alternatively, the SCBKSAMP data set contains JCL and input statements that you can customize and use to define the resources using the CICS DFHCSDUP batch utility program. The SCBKSAMP members for the transaction, program, and file definitions are CBKTRANS, CBKPROGS, and CBKFILES, respectively. For more information about defining CICS resources using the DFHCSDUP utility, see the CICS Resource Definition Guide. for your release of CICS TS.

Regardless of which of the two methods you choose to define the CICS BAC resources, you should allow any parameters not explicitly specified in the commands described in this section to take their default values. Also, for ease of use, use the same group name for all definitions.

CICS BAC transaction definition

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 3 to define the CICS BAC transaction resource definition in an active CICS region.

Figure 3. CEDA command to define the KBKM transaction in your CSD
CEDA DEFINE GROUP(cbkgroup) TRANSACTION(kbkM) PROGRAM(CBKCMNDS) 
TASKDATALOC(ANY) TASKDATAKEY(CICS)
Notes:
  1. In the example shown in Figure 3, 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 3, you can use the CICS BAC sample JCL in the SCBKSAMP data set member, CBKTRANS, to define the transaction using the CICS DFHCSDUP utility.

CICS BAC program and mapset definitions

You can use the sample commands in Figure 4 to define the programs and mapsets that CICS BAC requires.

Figure 4. CEDA commands to define the CBK programs and mapset in your CSD
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCBIRS) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCENQU) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCMNDS) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCIOBJ) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCMODA) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCMODB) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCMODC) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCMODD) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCMODE) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCRHST) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCSETF) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCSETP) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCSETQ) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCSETT) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCSHUT) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCSRSC) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCSRVR) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKCSTAT) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKFSXnn) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKMTENU) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKMTxxx) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) PROGRAM(CBKSPXnn) DATALOCATION(ANY) LANGUAGE(ASSEMBLER) EXECKEY(CICS)
CEDA DEFINE GROUP(cbkgroup) MAPSET(CBKMAP1)
Notes:
  1. In the CEDA commands shown in Figure 4, replace cbkgroup with any character string allowed by the CEDA transaction that meets your installation standards. Replace the nn in the program names CBKFSXnn and CBKSPXnn with 53 if you are installing CICS BAC in a CICS TS 1.3 region; 62 if you are installing CICS BAC in a CICS TS 2.2 region; 63 if you are installing CICS BAC in a CICS TS 2.3 region; 64 if you are installing CICS BAC in a CICS TS 3.1 region; 65 if you are installing CICS BAC in a CICS TS 3.2 region; or 66 if you are installing CICS BAC in a CICS TS 4.1 region. You can also define the programs for all these CICS releases if you want to.
  2. In the CEDA commands shown in Figure 4, CBKMTxxx represents some optional language modules that you can use in CICS BAC. Always define the module CBKMTENU. You should also define any other language modules for languages that are supported by your CICS region and supported by corresponding CICS BAC CBKMTxxx modules. For more information, see Appendix B. CICS BAC national language support (NLS).
  3. As an alternative to the CEDA commands shown in Figure 4, you can use the CICS BAC sample JCL in the SCBKSAMP data set member, CBKPROGS, to define the programs and mapset using the CICS DFHCSDUP utility.

CICS BAC control file definition

Define the CICS BAC control file using the sample CEDA command shown in Figure 5.

Figure 5. CEDA command to define the CICS BAC control file in your CSD
CEDA DEFINE GROUP(cbkgroup) FILE(CBKCNTL) DSNAME(hlq.control.file) LSRPOOLID(NONE)
Notes:
  1. In the CEDA commands shown in Figure 5, replace cbkgroup with any character string allowed by the CEDA transaction that meets your installation standards. Replace the nn in the program names CBKFSXnn and CBKSPXnn with 53 if you are installing CICS BAC in a CICS TS 1.3 region; 62 if you are installing CICS BAC in a CICS TS 2.2 region; 63 if you are installing CICS BAC in a CICS TS 2.3 region; 64 if you are installing CICS BAC in a CICS TS 3.1 region; 65 if you are installing CICS BAC in a CICS TS 3.2 region; or 66 if you are installing CICS BAC in a CICS TS 4.1 region. You can also define the programs for all these CICS releases if you want to.
  2. As an alternative to the CEDA command shown in Figure 5, you can use the CICS BAC sample JCL in the SCBKSAMP data set member, CBKFILES, to define the control file using the CICS DFHCSDUP utility.

Installing the CICS BAC resource definitions

When you have defined the CICS BAC transaction, programs, and file resources, you can install the definitions in the running CICS region using the CEDA INSTALL command:

CEDA INSTALL GROUP(cbkgroup)  

where cbkgroup is the group name you specified for the CICS BAC resource group in the CSD.

To install the CICS BAC resources automatically during CICS initialization, add your CICS BAC group name to a CICS startup list using the CEDA ADD command:

CEDA ADD GROUP(cbkgroup) LIST(listname) 

where cbkgroup is the group name you specified for the CICS BAC resource group in the CSD, and listname is the name of the startup list to which you want to add the group name.

Alternatively, you can edit the ADD GROUP command in one of the sample DFHCSDUP jobs, such as CBKFILES, to specify an appropriate group name.

Other CICS services used

CICS BAC also uses following CICS services. These services are: