CallPath/CICS for OS/390 is an application enabler for coordinating voice and data applications. It provides the application program interface (API) defined by IBM's CallPath Services Architecture, and provides supporting administrative functions to assist you in developing and implementing coordinated voice and data applications.
CallPath/CICS is a set of Customer Information Control System (CICS) application programs that provides access to the services of a telephone switch for application programs written in COBOL, PL/I, C, or Assembly Language. (For full details of languages supported, see "Environmental Requirements".) The term switch is used to refer to any telephone switching system, for example private branch exchanges (PBXs).
CallPath/CICS runs on the IBM OS/390 operating system. CICS multiregion operation (MRO) is supported. Multiple copies can run simultaneously, provided each copy is in a separate CICS region.
The communications between CallPath/CICS and a switch are managed by IBM CallPath SwitchServer/2, which runs on OS/2 on a personal computer. See "Books for related products" for details.
CallPath SwitchServer/2 performs a conversion to and from switch protocols. It is transparent to your applications.
CallPath/CICS consists of:
Sample programs are also provided to help application programmers write new CallPath Services applications. For more information about the sample programs, refer to the CallPath/CICS for OS/390 Application Programming Guide.
The application program interface (API) is a set of library programs for application programmers. CICS applications written in COBOL, PL/I, C or Assembly Language can make calls to these programs. When a CallPath/CICS system is running, all applications share one copy of the API programs.
The API presents a consistent interface (through program calls) to applications independent of the switch protocols. However, the availability of functions might be limited by the capabilities of the switch.
When an application program issues a program call for a switch function, CallPath/CICS sends a request to the switch through CallPath SwitchServer/2. The switch sends messages back to the application, if requested.
For more information about the API, refer to the CallPath/CICS for OS/390 Application Programming Guide.
The communications protocol that CallPath/CICS uses when communicating with CallPath SwitchServer/2 is Systems Network Architecture (SNA) logical unit (LU) 6.2. CallPath/CICS uses the LU6.2 verbs supported by CICS to hold conversations with CallPath SwitchServer/2. CICS routes the messages to CallPath SwitchServer/2 through the Advanced Communications Function for the Virtual Telecommunications Access Method (ACF/VTAM or VTAM for short).
Communications are handled by two components:
The administration subsystem is the part of CallPath/CICS that allows you to configure, control, and monitor CallPath/CICS. You can sign on to the administration subsystem from any CICS terminal. However, you do not need to remain signed on because all messages concerning CallPath/CICS operation are written to either the CallPath/CICS message log or a user-specified CICS TD queue (transient data queue).
The switch simulator is a component of CallPath/CICS you can use to test application programs without having a CallPath SwitchServer/2 and switch connected to the test system. The simulator checks the validity of program calls issued by applications running in simulation mode and puts messages on their message queues. You can control whether responses are positive or negative, the content of other messages, and the timing of message arrival. By varying these conditions, you can perform a wide range of program tests using the simulator.
For more information about the switch simulator, refer to the CallPath/CICS for OS/390 Application Programming Guide
The installation verification program is a component of CallPath/CICS you can use to check CallPath/CICS is installed correctly.