System Management Guide

Chapter 15. Defining CallCoordinator Software to CICS for MRO

Skip this chapter if you are defining CallCoordinator software to CICS only for a single-region environment, or for a sysplex environment.

Install CallCoordinator in a Multiregion Operation (MRO) environment by performing the additional tasks described in this section. See Chapter 13, "About CallCoordinator Software" for a description of the terminology used in this section.

A summary of the MRO tasks follows:

Customize CICS table entries for MRO using resource definition (MACRO) -- in the user AOR and the TOR.
In the TOR and user AOR, define programs, transactions, and files -- using resource definition online (RDO) utilities.
Incorporate the COR in your MRO environment.
Note: The CallCoordinator AOR (the COR) has already been defined. See Chapter 14, "Defining CallCoordinator to CICS for SRO".
Define CallCoordinator in the user AORs.
Define CallCoordinator in any TORs containing terminals that participate in CallCoordinator activities.

Customizing CICS Table Entries for MRO

For all AORs and TORs:

Define the Program List Table
Customize member CAMKPLAJ in SEZPSAMP:
1. Customize the job card.
2. Use one of the following methods to assemble and link CICS tables:
  - If you are using the supplied procedure, CAMKPROC, customize the _HLQ_ and _VER_ options on the //_JCLLIB statement. This statement points to the dataset in which the provided procedure CAMKPROC resides.
  - If you are modifying your own procedure, customize its name, and remove or change the //_JCLLIB statement.
3. The job includes PLT startup and shutdown entries for CallCoordinator/CICS. Include entries for all other products in the COR (for example, CallPath/CICS).
4. Optionally, customize the table suffix.
Run member CAMKPLAJ. The expected return code is 0.

Note: This procedure enables the DFHXTENF exit program at Startup.

Defining Programs and Transactions for MRO Using RDO

The procedure to follow depends on the region type:

For AOR
1. Customize and run the appropriate job for the level of CICS installed (CAMKNAnn):
  1. Customize the job card.
  2. Use one of the following methods to assemble and link CICS tables:
    - If you are using the supplied procedure, CAMKPROC, customize the _HLQ_ and _VER_ options on the //_JCLLIB statement. This statement points to the dataset in which the provided procedure CAMKPROC resides.
    - If you are modifying your own procedure, customize its name, and remove or change the //_JCLLIB statement.
  3. Change the _COR_ to the name of the connection definition to the COR.
  4. The job includes TST entries for CallCoordinator/CICS. Include entries for all other products in the COR (CallCoordinator/CICS). Select the macro appropriate for your release of CICS. See Table 20
  5. Optionally, customize the table suffix.
2. Run member CAMKTSTJ. The expected return code is 0.
3. Update the CICS SIT to reflect the new TST suffix.
For TOR
1. Customize and run the appropriate job for the level of CICS installed (CAMKNTnn).
  1. Customize the job card.
  2. Use one of the following methods to assemble and link CICS tables:
    - If you are using the supplied procedure, CAMKPROC, customize the _HLQ_ and _VER_ options on the //_JCLLIB statement. This statement points to the dataset in which the provided procedure CAMKPROC resides.
    - If you are modifying your own procedure, customize its name, and remove or change the //_JCLLIB statement.
  3. Change the _COR_ to the name of the connection definition to the COR.
  4. Change the _AOR_ to the name of the connection definition to the user AOR.
  5. The job includes TST entries for CallCoordinator/CICS. Include entries for all other products in the COR (CallCoordinator/CICS). Select the macro appropriate for your release of CICS. See Table 20
  6. Optionally, customize the table suffix.
2. Run member CAMKTSTJ. The expected return code is 0.
3. Update the CICS SIT to reflect the new TST suffix.
See "Customizing a Job".

Incorporating the CallCoordinator COR in your MRO

This section describes the tasks you perform to incorporate the CallCoordinator region into your MRO environment. The CallCoordinator region (CallCoordinator COR) was defined earlier, following the procedures in Chapter 14, "Defining CallCoordinator to CICS for SRO".

Usage Notes:

Your programs that are defined as CallCoordinator exits must be added to the PPT in the CallCoordinator COR. (See exit fields on the CallCoordinator System Setting panel in "Configuring the CallCoordinator Telephony Settings").
Monitor the CICS shutdown statistics for an increase in inter-region communication (IRC) activity. Application programs that invoke the CallCoordinator API from a user AOR increase this activity. These application programs use IRC links to communicate with CallCoordinator. You might need to increase the number of IRC links.
If you use the Screen Presentation Exit, then:
- Your transactions IDs must be unique
- You only can move data between two queues that are in the same region.
  Note: Refer to CallPath CallCoordinator/CICS Application Programming Guide for information on temporary storage queues and on CallCoordinator exits.
If you use interactive voice responses (IVRs), they must sign themselves on to CallCoordinator either with CallCoordinator transaction VA90 or with your own transaction (which invokes the CallCoordinator Sign-On API).
Refer toCallPath CallCoordinator/CICS General Information and Part 1, "Planning" for more information on IVRs.
For information on connection and session definitions, refer to Customer Information Control System (CICS)/MVS, Resource Definition (Online), SC33-0508 (CICS 2.1).

Define the COR as follows:

In the CallCoordinator region, define any AOR or TOR that communicates with the CallCoordinator region as a remote MRO system.
If your application is outside the CallCoordinator region and you use the Screen Presentation Exit, define generic names for the queues in the DFHTST table in the CallCoordinator region as remote resources, specifying the SYSID of the region where the application runs.
Note: Refer to CallPath CallCoordinator/CICS Application Programming Guide for more information on the CallCoordinator exits and on temporary storage queues.
If the CallCoordinator region is also a TOR, add DFHZNEP--the node-error program with CallCoordinator updates--in the DFHRPL for the region. See "Installing CallCoordinator Node Error Program Logic".
If you have terminals owned by more than one region, ensure that the terminals used by CallCoordinator agents have unique names across all CICS regions concerned with CallCoordinator.

Defining CallCoordinator in the User AORs

Usage Notes:

When your application-owning region (AOR) is not the same region as the CallCoordinator region, be aware that an AOR can communicate with only one CallCoordinator region in a MRO environment.
Your programs that are defined as CallCoordinator exits must be added to the PPT in the COR, not in the user AORs. See "Incorporating the CallCoordinator COR in your MRO".

Define CallCoordinator in the user AORs as follows:

In any user AOR, define the CallCoordinator region as a remote MRO region.
For any user region that has an application that invokes a CallCoordinator API, ensure that the CallCoordinator programs for user AORs have been defined. See "Defining Programs and Transactions for MRO Using RDO"
Monitor the CICS shutdown statistics for an increase in IRC activity. Increased activity is caused by application programs that invoke CallCoordinator API from an AOR other than the CallCoordinator AOR. These application programs use IRC links to communicate with CallCoordinator. You might need to increase the number of IRC links.
Specify the CICS system initialization table (SIT) parameter MROLRM=YES to reduce the amount of overhead required by IRC link usage.
For any user AOR that invokes CallCoordinator APIs or uses EZPSXTEC, include the CallCoordinator library in the JCL for the region startup.
Concatenate the CallCoordinator SMP/E target load library _HLQSMP_._VER_.SEZPLOAD to the DFHRPL DD statement.
Concatenate the customization PDS in front of the CallCoordinator library.

Defining CallCoordinator in the TORs

Usage Notes:

If you have terminals owned by more than one region, ensure that the terminals used by CallCoordinator agents have unique names across all CICS regions concerned with CallCoordinator.
If your TOR is not the same region as the CallCoordinator region, be aware that a TOR can communicate with only one CallCoordinator region. in a MRO environment.

Define CallCoordinator software to any TORs that contain terminals that participate in CallCoordinator activities as follows:

In the TOR, define the CallCoordinator region as a remote MRO region.
Update DFHZNEP, the node-error program, with EZPZNEPA. Ensure that DFHZNEP is active in the TOR.
Ensure that the CallCoordinator programs have been defined to the CICS PPT table. See "Defining Programs and Transactions for MRO Using RDO".
Ensure that all CallCoordinator transactions have been defined as remote transactions owned by the COR. See "Defining Programs and Transactions for MRO Using RDO".
Concatenate the CallCoordinator SMP/E target load library _HLQSMP_._VER_.SEZPLOAD to the DFHRPL DD statement.
Concatenate the customization PDS in front of the CallCoordinator load library.

Task Checkpoint
You have completed the task of defining CallCoordinator software to CICS for MRO. Continue to the next task, Chapter 17, "Validating Software Load and Definition to CICS".