System Management Guide

Chapter 2. Planning for Installation

This section helps you plan for CallPath/CICS installation.   To prepare for installation:

• Check you have the required software
• Check you have the required disk space.

Environmental Requirements

The following sections list the hardware and software you need to run CallPath/CICS.

Hardware

CallPath/CICS needs no hardware in addition to that needed by CICS for OS/390.

Software

The following prerequisite and co-requisite software products must be installed on the IBM S/390® host computer:

• One of the following:    
  • CICS for MVS/ESA V4.1
  • CICS Transaction Server for OS/390 V1.2 or
  • CICS Transaction Server for OS/390 V1.3 or later

• Advanced Communication Function/Virtual Telecommunications Access Method (ACF/VTAM) as appropriate for your version of CICS  

• System Modification Program Extended (SMP/E) Release 5 or later    

• Virtual Storage Access Method (VSAM) support: DFP/XA Release 2.3    

You do not need a programming language to run CallPath/CICS, including the sample program. However, you do need a programming language to develop applications that operate with CallPath/CICS. The following languages are supported:

• IBM COBOL for MVS and VM
• IBM PL/I for MVS and VM
• C
• Assembly Language

CallPath/CICS also needs IBM CallPath SwitchServer/2.

Distribution Package

When you order CallPath/CICS for OS/390, you receive either a nine-track magnetic tape recorded at 6250 BPI, or a 3840 cartridge, or a 4MM DAT cartridge. CallPath/CICS for OS/390 (CallPath/CICS) is one of the features on the tape.

The tape or cartridge contains the CallPath/CICS programs in the form of load modules in SMP/E format. You must use SMP/E to install CallPath/CICS.

With the tape, you receive a set of documents that includes the CallPath/CICS for OS/390 Program Directory.   Read the program directory before installing CallPath/CICS. If there are any differences between this book and the program directory, use the information in the program directory.

Storage Requirements

The total size of the CallPath/CICS load modules and CICS basic mapping support (BMS) maps is approximately 3.1 MB (MB equals 1 048 576 bytes). The main storage and disk space used by the system depends on the number of switches defined, the number of active telephone numbers, and the type and volume of application program calls.

Table 1 shows an example of the storage requirements for a configuration with:

• Fifty concurrently active applications, each with four call profiles and four outstanding switch requests

• Five switches

• One hundred concurrently active telephone numbers, each with one ownership registration

• No buildup of application message queues; the applications receive messages as soon as they arrive.

You need a total of 17 500KB (KB equals 1024 bytes) of direct access storage for the     SMP/E libraries and a total of 10 500KB of direct access storage for the CallPath/CICS libraries.

See the CallPath/CICS for OS/390 Program Directory for detailed information about storage requirements.      

Table 1. Storage Requirements

Type of Storage	Purpose	Approximate Size
CICS storage above 16MB line	Tables. For example, one call profile table and five request tag tables (one per switch), plus event and request handler load modules.	1MB. But see "Using CICS storage above the 16MB line".
CICS storage below 16MB line	API load modules and storage configuration table.	5KB (KB equals 1024 bytes)
CICS transient data queues	Message handler queues and the administration subsystem queue.	7KB
CICS temporary storage	Traffic statistics.	20KB
VSAM data sets	Trace, error, traffic, switch configuration, and control files.	9MB
Optional archive data sets (used at supplied sizes)	Archived error, trace, and traffic files.	23MB

Using CICS storage above the 16MB line