This chapter gives the procedures for defining CallCoordinator software to CICS for a single-region operation (SRO).
Complete the tasks in this chapter, validate installation for single region operation by performing the tasks in Chapter 17, "Validating Software Load and Definition to CICS".
Then do one of the following:
This chapter gives the procedures for the following major tasks:
If you decided during planning to limit access to the CallCoordinator System Administration panel, the Problem Determination panel, and the functions accessed through these menus, use your security package or CICS provided security.
The CallCoordinator transaction is:
The individual acting as the system administrator requires access to this transaction. Data entry personnel might need access to it in order to access and populate the Agent Detail panels and other panels -- ask your call center manager.
For MRO or SYSPLEX users, CallCoordinator requires that a dummy TCTTE entry is present in the COR to enable Screen Presentation Manager to work. The DSHIPIDL and DSHIPINT SIT parameters should be set to 0 in the COR to avoid these entries beng deleted.
CallCoordinator/CICS provides the ability to Recovery/Restart resources by issuing messages to the system console (WTOs and WTORs). If you are going to use these messages for Automated Recovery, the SIT parameter OPERTIM should be set to a value that ensures they are not deleted after the default 2 minutes.
The suffixes used for the CICS Macro Table entries should be set accordingly.
Since Call Coordinator utilizes a considerable amount of memory, both above and below the 16M line, you may need to increase the SIT parameters EDSA and DSA when you install CallCoordinator software.
Consider the storage requirements listed in this section for CallCoordinator, and storage requirements for your other applications. If your initial values are not adequate, adjust the EDSA and DSA parameters in your SIT as necessary.
Table 25 summarizes the storage requirements for CallCoordinator when all tables are configured at maximum size, and default size. All tables and programs are above the 16M line.
Table 26 lists the CallCoordinator memory requirements you should use if your CallCoordinator tables are configured smaller than the maximum allowed. Reduce the CallCoordinator storage requirement according to the number of CallCoordinator table entries in your installation.
Table 27
shows the sizes for frequently-used CallCoordinator programs
that are likely to be resident in CICS. These values are
not affected by table size configuration. The table is provided for
information only. Values may
vary slightly from release to release.
Table 25. CallCoordinator Storage Requirements
|
| Default | Maximum |
|---|---|---|
| Tables | 3169K | 14878K |
| Resident Programs | 563K | 563K |
|
| ||
| Total | 3732K | 15441K |
Table 26. Memory Requirements for Major CallCoordinator Tables
| Table Name 1 | Default Entries (number) | Maximum Entries (number) | Entry Size (bytes) | Extra (bytes) | Default Total (bytes) | Maximum Total (bytes) |
|---|---|---|---|---|---|---|
| Agents (EZPSAGIL) | 1000 | 9999 | 400 | 21012 | 421412 | 4021012 |
| Event Message Queue (CAMLEMQL) 2 | -- | -- | -- | -- | 102400 | 102400 |
| MIS Message Queue (CAMLMMQL) | 400 | 4000 | 460 | 48 | 184048 | 1840048 |
| Call Management Control (CAMTACTH) | 3000 | 9000 | -- | -- | 2444944 | 7976944 |
| Message Table (CAMNL01L) | -- | -- | -- | -- | 14072 | 14072 |
| Switch Monitor Table | 99 | 99 | 16 | 16 | 1600 | 1600 |
| Total | -- | -- | -- | -- | 3168476 | 14877676 |
Footnotes
| ||||||
Note: The following files are loaded into User-maintained or Coupling Facility data tables:
| Program Name | Bytes |
|---|---|
|
| |
| CallCoordinator Programs | |
| CallPath Services Event Receiver (CAMT220C) | 32968 |
| Call Tracking Manager (CAMT200C) | 262304 |
| MIS Log Interface (CAMM400C) | 25280 |
| Screen Presentation Manager (CAMS5xxC) | 241768 |
| Total | 562320 |
This section describes how to use macro tables for defining CICS resources for Single Region Operation (SRO).
You must:
A sample procedure (CAMKPROC) is supplied to assemble and link the CICS macro tables. Unless you use a procedure of your own to perform these operations on the CICS macro tables, the supplied procedure must be customized to use the naming conventions of your environment:
To include DCT entries:
For TS 1.2 and TS 1.3: Use the supplied RDO job as listed in Table 22.
Note: To activate CallCoordinator at CICS startup and deactivate it at CICS shutdown, you must customize PLT entries.
To include PLT entries:
To include JCT entries:
For TS 1.2 and TS 1.3: Use the supplied RDO job as listed in Table 22.
To include TST entries:
This section describes the procedures for defining CallCoordinator resources to the CallCoordinator region (COR), using RDO.
Usage Notes: The jobs you need to use are different for each type of environment in which you will eventually run CallCoordinator/CICS:
where nn is the CICS version, for example, 41 represents Version 4.1.
Note: If you are on TS 1.3 and planning to run in a SYSPLEX environment, use the job CAMKSC13 and not CAMKNC13.
Before defining RDO resources in a sysplex environment, see:
Edit the selected member in the SEZPSAMP target library, customizing the job for your environment as follows:
If the group names were changed from the defaults used in the previous release, change the DELETE statement so that groups with these modified names will be deleted.
Optionally, use a group list name that conforms to your local naming conventions.
The job you need to run to create the VSAM data sets depends on whether CallCoordinator is already installed on your system or not:
Note: There are separate jobs to allocate, initialize, and migrate each file. SeeTable 24
Note: Ignore this section if you already have CallCoordinator installed, and run CAMKMIGJ instead. See "Migrating VSAM Data Sets (CAMKMIGJ)".
CAMKALLJ defines all the VSAM clusters and initializes files to default values. Edit CAMKALLJ in target library SEZPSAMP, customizing the job for your environment as follows:
Note: The job should complete with all zero return codes.
Note: Ignore this section if you are installing CallCoordinator for the first time, and run CAMKALLJ instead. See "Allocating and Initializing VSAM Data Sets (CAMKALLJ)".
CAMKMIGJ defines all the VSAM clusters and migrates files from the previous version of CallCoordinator/CICS. Edit CAMKMIGJ in target library SEZPSAMP, customizing the job for your environment as follows:
Note: The job should complete with all zero return codes.
The procedure to follow depends on the version of CICS installed.
To allocate the Trace User Journal:
Note: The number must match that in the Trace Journal Id field of the Telephony Settings panel. (See "Configuring the CallCoordinator Telephony Settings".)
To create the Archive and Extract job:
Note: The member name, CAMKTRCA, is the name specified on the JCT macro description for this journal (CAMKJCTF). Users can change this name, but they must then re-run CAMKJCTJ with the new archive name. Refer to the CICS Resource Definition Guide for more information.
In CICS, TS1.2 and TS1.3, user journals are defined to the DASD Logger or the MVS Logger. A sample job (CAMKTCFJ) is supplied, which defines the following Logstream Model to the MVS Logger.
_CICSUSERID_.CAMTRACE.MODELwhere _CICSUSERID_ is the Default CICS Userid.
The RDO jobs for defining CICS resources in the CallPath Region for TS1.2 and TS1.3 include a definition of a journal model as follows:
DEFINE JOURNALMODEL(CAMTRACE) GROUP(CAMKxxxx)
JOURNALNAME(DFHJ03) TYPE(MVS)
STREAMNAME(&USERID..CAMTRACE.DFHJ03)
This resolves to a logstream name of
_CICSUSERID_.CAMTRACE.DFHJ03being created in the MVS Logger, and is based on the logstream model defined in CAMKTCFJ.
If a customer wishes to use another user journal, a new journal model must be defined and the Journal Number must be changed using the COR Telephony Settings panel (accessed using option 3 from the main System Administration menu). Currently, only Journal Numbers are allowed. (See "Configuring the CallCoordinator Telephony Settings".)
Also, the user must make sure that a logstream model is defined to the MVS logger that will resolve the new logstream name.
CAMKJCFA is a sample extract program for user journals in the MVS Logger. This job extracts user journals to CICS V4.1 User Journal Format and then extracts them to a sequential file.
For more information on MVS or DASD Logging, see the Redbook CICS Transaction Server for OS/390 V1R2 Implementation Guide, SG24-2234-00.
The procedure to follow depends on the version of CICS installed.
To allocate the MIS User Journal:
Note: The number must match that in the User Journal Id field of the Telephony Settings panel. (See "Configuring the CallCoordinator Telephony Settings".)
To create the Archive and Extract job:
Note: The member name, CAMKMISA, is the name specified on the JCT macro description for this journal (CAMKJCTA). Users can change this name, but they must then re-run CAMKJCTJ with the new archive name. Refer to the CICS Resource Definition Guide for more information.
In CICS, TS1.2 and TS1.3 user journals are defined to the DASD Logger or the MVS Logger. A sample job (CAMKMCFJ) is supplied, which defines the following Logstream Model to the MVS Logger.
_CICSUSERID_.CAMMIS.MODELwhere _CICSUSERID_ is the Default CICS Userid.
The RDO job for defining CICS resources in the CallPath Region for TS1.2 and TS1.3 includes a definition of a journal model as follows:
DEFINE JOURNALMODEL(CAMMIS) GROUP(CAMKxxxx)
JOURNALNAME(DFHJ02) TYPE(MVS)
STREAMNAME(&USERID..CAMMIS.DFHJ02)
This resolves to a logstream name of
_CICSUSERID_.CAMMIS.DFHJ02being created in the MVS Logger, and is based on the logstream model defined in CAMKMCFJ.
If a customer wishes to use another user journal, a new journal model must be defined and the Journal Number must be changed using the COR Telephony Settings panel (accessed using option 3 from the main System Administration menu). Currently, only Journal Numbers are allowed. (See "Configuring the CallCoordinator Telephony Settings".)
Also, the user must make sure that a logstream model is defined to the MVS logger that will resolve the new logstream name.
CAMKJCFA is a sample extract program for user journals in the MVS Logger. This job extracts user journals to CICS V4.1 User Journal Format and then extracts them to a sequential file.
For more information on MVS or DASD Logging, see the Redbook CICS Transaction Server for OS/390 V1R2 Implementation Guide, SG24-2234-00.
Install CallCoordinator node-error program logic as follows:
Refer to the appropriate CICS Customization Guide, for the CICS version for more information on the node error program.
If you have not defined the VSAM file names for Dynamic Allocation (see "RDO to Define CICS Resources for SRO".), include the following member in your CICS startup JCL.
Figure 4 shows the list of the required common DD statements that must be included in your CICS startup JCL.
Figure 4. CAMKDDSJ Required CICS Startup JCL DD Statements
//*-------------------------------------------------------------------*
//* CICS VSAM FILES AND USER MAINTAINED DATA TABLES
//*-------------------------------------------------------------------*
//CAMAGRSV DD DISP=SHR,DSN=_HLQ_._VER_.CAMAGRSV.KSDS
//CAMASWIV DD DISP=SHR,DSN=_HLQ_._VER_.CAMASWIV.KSDS
//CAMASWIT DD DISP=SHR,DSN=_HLQ_._VER_.CAMASWIV.KSDS
//CAMAAGTV DD DISP=SHR,DSN=_HLQ_._VER_.CAMAAGTV.KSDS
//CAMAAGTX DD DISP=SHR,DSN=_HLQ_._VER_.CAMAAGTV.PATH
//CAMAAMRV DD DISP=SHR,DSN=_HLQ_._VER_.CAMAAMRV.KSDS
//CAMAAMRX DD DISP=SHR,DSN=_HLQ_._VER_.CAMAAMRV.PATH
//CAMAPLTV DD DISP=SHR,DSN=_HLQ_._VER_.CAMAPLTV.KSDS
//CAMADNSV DD DISP=SHR,DSN=_HLQ_._VER_.CAMADNSV.KSDS
//CAMATRKV DD DISP=SHR,DSN=_HLQ_._VER_.CAMATRKV.KSDS
//CAMASPFV DD DISP=SHR,DSN=_HLQ_._VER_.CAMASPFV.KSDS
//CAMABPNV DD DISP=SHR,DSN=_HLQ_._VER_.CAMABPNV.KSDS
//CAMALBFV DD DISP=SHR,DSN=_HLQ_._VER_.CAMALBFV.KSDS
//CAMAISTV DD DISP=SHR,DSN=_HLQ_._VER_.CAMAISTV.KSDS
//CAMAAMRT DD DISP=SHR,DSN=_HLQ_._VER_.CAMAAMRV.KSDS
//CAMAPLTT DD DISP=SHR,DSN=_HLQ_._VER_.CAMAPLTV.KSDS
//CAMADNST DD DISP=SHR,DSN=_HLQ_._VER_.CAMADNSV.KSDS
//CAMATRKT DD DISP=SHR,DSN=_HLQ_._VER_.CAMATRKV.KSDS
//CAMASPFT DD DISP=SHR,DSN=_HLQ_._VER_.CAMASPFV.KSDS
//CAMABPNT DD DISP=SHR,DSN=_HLQ_._VER_.CAMABPNV.KSDS
//CAMALBFT DD DISP=SHR,DSN=_HLQ_._VER_.CAMALBFV.KSDS
//CAMAISTT DD DISP=SHR,DSN=_HLQ_._VER_.CAMAISTV.KSDS
//CAMH01V DD DISP=SHR,DSN=_HLQ_._VER_.CAMH01V
//EZPH01V DD DISP=SHR,DSN=_HLQ_._VER_.EZPH01V
//*-CALLCOORDINATOR JOURNALS FOR CICS 4.1-----------------------------*
//DFHJ02A DD DISP=SHR,DSN=_HLQ_._VER_.MIS.JOURNALA
//DFHJ02B DD DISP=SHR,DSN=_HLQ_._VER_.MIS.JOURNALB
//DFHJ03A DD DISP=SHR,DSN=_HLQ_._VER_.TRACE.JOURNALA
//DFHJ03B DD DISP=SHR,DSN=_HLQ_._VER_.TRACE.JOURNALB
//*-------------------------------------------------------------------*
Figure 5. Example of DD Statement Customization
//DFHRPL DD ...
// DD ...
// DD DISP=SHR,DSN=_HLQ._EZPCUSTM_
// DD DISP=SHR,DSN=_HLQSMP_._VER_.SEZPLOAD
// DD ...
// DD ...
Recycle the CICS region now, or wait to recycle after you have defined common software to CICS for MRO or sysplex.
| Task Checkpoint |
|---|
| You have completed the task of defining CallCoordinator and the CallCoordinator feature to CICS for single-region operation. Now validate these definitions, following the procedures in Chapter 17, "Validating Software Load and Definition to CICS". |
