Initial CICS application configuration
Company A has an existing insurance application that uses a single CICS® region for its transaction processing infrastructure. The application configuration is based on the general insurance application.
The general insurance application simulates transactions made by an insurance company to create and manage its customers and insurance policies. The application provides sample data and a 3270 interface for creating and inquiring on customers and policy information. Because the application is designed to simulate the flow of an application, some aspects of the application architecture do not use best practices. However, the application is designed to be extended and used in this scenario to demonstrate best practices around running applications in a CICSplex environment.

- CICS application
- Business users interact with a CICS 3270
insurance application, written in COBOL, for example to add new customers
and create insurance policies. The application uses a named counter
server in the coupling facility to generate unique customer numbers.
- The named counter server provides a mechanism to provide a unique number to the application. In the general insurance application it provides a unique customer number.
- The coupling facility provides a mechanism to share data across logical partitions on a z/OS® server. All CICS regions operating on the server can access the data, even if they are in different partitions.
- The application creates a customer record in DB2 and saves customer data in a VSAM file. The application uses a two-phase commit to ensure that both updates complete successfully before the change is committed. If the VSAM file update fails, the DB2 update is rolled back. The two-phase commit ensures that the application recovers correctly in the event of a failure. This feature of the general insurance application is not a best practice, but is provided as a way to test two-phase commit processing in CICS.
- The application uses two shared temporary storage queues, one
to show the range of customer numbers from the named counter server,
and the other to record errors that occur when writing to the database.
The temporary storage queues are stored in the coupling facility, which means that you can have different instances of the application accessing the same temporary storage queues in different logical partitions. These queues are not required by the general insurance application, but are provided for workload testing.
- CICS region
- The CICS region is configured with a set of system initialization parameters that enable CICS to connect with DB2 and the coupling facility. The region also contains the resources required by the application, including a TSMODEL resource with a pool name that matches the structure in the coupling facility, a DB2CONN resource for the connection to DB2, and FILE resources.
- Coupling facility
- The coupling facility is part of z/OS and
contains the named counter server and temporary storage queues that
are used by the application. The coupling facility contains a set
of structures for the named counter server and temporary storage queues.
It contains a pool that associates the structures with the CICS region.
The coupling facility provides a mechanism to share data across logical partitions on a z/OS system. All CICS regions operating can access the data, even if they are in different partitions. Using the coupling facility for an application in a single region is not typical, but because the application is designed to run in a topology, the coupling facility is used.
- Temporary storage queue (control)
- The temporary storage queue, GENACNTL, contains a record of the range of customer numbers that are allocated. The application updates the temporary storage queue (control) as each customer record is added. Using a temporary storage queue to contain this type of data is not a best practice, but is provided for workload testing.
- Temporary storage queue (errors)
- The temporary storage queue, GENAERRS, contains errors when the application is unable to write information to DB2. Using a temporary storage queue in this way is not a best practice, but is used to easily identify any DB2 problems during your testing.
- VSAM files
- The application stores information in VSAM files. The general
insurance application uses two VSAM files: KSDSCUST for
customer records and KSDSPOLY for policy records.
You can browse these files in the userid.CB12.KSDSCUST and userid.CB12.KSDSPOLY data
sets to look at the contents. The key for the KSDSCUST VSAM
file is the first 10 characters of each customer record. The key for
the policy VSAM file is the first 12 characters. The application uses
four types of policies, indicated by the initial letter:
- C is a commercial property insurance policy
- E is an endowment insurance policy
- H is a house insurance policy
- M is a motor insurance policy
- DB2
- The database contains details of the customers and insurance policies
for the application. The database contains the following tables:
- A customer table that lists all the customer records, including the customer number.
- A policy table that lists all the policies, including the customer number, policy number, and policy type.
- A policy table for each type of policy: commercial, endowment, house, and motor insurance policies.