CallCoordinator provides you with some panels for problem determination. To access these panels:
V800 CallCoordinator V 2.1 System Administration 1999/11/02
Main Menu 04:30:11PM
Select one of the following. Then press Enter.
_ 1. COR Operations
2. Switch Operations
3. System Configuration
4. Resource Definition
COR Sysid: CORF TermID: S209 Local System Status: ACTIVE
5655-B34 (C) Copyright IBM Corp. 1992, 1999. All rights reserved
F1=Help F2= F3=Exit F4=2 F5=Refresh F6=
F7= F8= F9= F10= F11= F12=
|
VA10 CallCoordinator V2.1 System Administration
COR Operations
Type an action code, then press Enter
1=Start CC 2=Stop CC 3=Set Trace On 4=Set Trace Off
5=CC Status 6=Table Reload
Act COR COR CC Trace
Code ApplID SysID Status Status
_ CORA INACTIVE INACTIVE
_ CORB INACTIVE INACTIVE
_ CORC INACTIVE INACTIVE
_ IYCLZC0D CORD INACTIVE INACTIVE
_ CORE INACTIVE INACTIVE
_ IYCLZC0F CORF ACTIVE ACTIVE
_ COR3 INACTIVE ACTIVE
_ COR5 INACTIVE INACTIVE
COR Sysid: CORF TermID: S208
F1=Help F3=Exit F5=Refresh F12=
|
Codes for the status of the system (CC Status) are:
3=Set Trace On,
4=Set Trace Off,
see "Using Trace"
5=CC Status, see "CallCoordinator Status"
If you encounter a problem in running CallCoordinator you may need to collect data for IBM to solve the problem. Use the trace facility to help you collect the data.
You can use the Set Trace On activity code (3) on the COR Operations panel (VA10) to turn on trace record generation separately for each COR. In routine operation, the trace facility should be turned off to avoid logging unneeded messages and slowing down the system. The trace may be started or stopped in any COR from any COR, in a multiple COR environment.
When a problem occurs, the IBM Software Support Center will tell you if trace needs to be turned on.
Note: The trace selection remains in effect until it is turned off by selecting option 4 from the COR Operations panel. Remember to turn it off so as not to cause unnecessary logging.
If Trace is set on, it will remain on until it is explicitly turned off, even when the CICS region is recycled. This is to allow for tracing of CallCoordinator startup.
This allows you to view information on the status of
the system and the long running tasks in CallCoordinator,
and to view table usage statistics online.
VA12 CallCoordinator V2.1 COR Operations 1999/10/29
CallCoordinator Status 02:21:0 2PM
For COR: CORF System Status: ACTIVE
-------- CallCoordinator Long Running Task Status --------
Item Date Time Status
CSM (V884) 1999/12/18 01:54:57PM A
CTM (V200) 1999/12/18 01:55:24PM A
MIS (V400) 1999/12/18 01:55:24PM A
CTR (V220) 1999/12/18 01:55:24PM A
---------------- CallCoordinator Tables ------------------
Counts Current Hi-water Maximum Utilization
Event Msg Q 0000000 0000015 N/A %
Calls (CMCT) 00000 00000 03000 %
Parties 00000 00000 04000 %
Connections 00000 00000 09000 %
Agents 00000 00000 00000 %
MIS Msg Q 00000 00000 00000 %
COR Sysid: CORF TermID: S208
F1=Help F3=Exit F5=Refresh F12=
|
The following is an explanation of the display only fields on the CallCoordinator Status panel.
Long running tasks (LRT) are those tasks that begin running when the system is started, and run in the background without operator instruction until the system is shut down, unless an error condition occurs.
When a long running task is not active, the system as a whole is not active. To make the system active, identify which LRT is inactive and correct its problem, then restart the system.
The CallCoordinator long running tasks are:
This LRT (V884) periodically checks the status of the long running tasks, and displays one of the status codes in the status field to post the results of that check. You can refer to the CICS system log to determine if an error condition exists.
LRT V200 is the central transaction of CallCoordinator. It initializes and performs the shutdown of the system, maintains the status of calls, sends commands to Screen Presentation Manager (SPM) to change screen environments, and sends data to Load Balancing Manager (LBM) to update the status of queues. Data from event messages and from data processing tables and transactions are sent to MIS to provide a history of call management.
This LRT (V400) provides a history of the coordinated voice and telephony activities of an CallCoordinator call center. Call Tracking Manager (CTM) sends data from event messages, and SPM and LBM send error messages to the MIS log.
LRT V220 is the receiver task that receives event messages from CallPath/CICS for OS/390 and passes them to V200.
The CICS syslog message will appear in the syslog associated with the COR being started, not the COR from where it was started. For example, if you are on the COR Operations panels in COR A and you request a startup for COR B, the system messages will be in the COR B syslog.
