Application design and development considerations for CICS DB2

This section contains information primarily for the CICS® application developer, the CICS application reviewer, and those involved in defining standards for application design.

Note that this chapter deals only with the design recommendations that are unique to the CICS DB2® environment. The general considerations that apply only to CICS applications, or only to DB2 applications, are not covered. See the DB2 Universal Database™ for OS/390® and z/OS® Application Programming and SQL Guide for more information on DB2 application design, and the CICS Application Programming Guide for more information on CICS application design.

In the design process, decisions can be taken that have consequences related not only to the application being developed now, but also to future applications. Some of the key aspects of the design process are as follows:

The design that you implement can influence:

A well-designed CICS DB2 application should work properly when set into production for the first time. However, certain factors can affect the application's performance later on. These factors include:

It is therefore important to develop a consistent set of standards on using DB2 in the CICS environment.

If you have previously developed applications with data stored in VSAM and DL/I, be aware that there are several differences between those applications and CICS DB2 applications. Some of the main differences to consider are:

One of the major differences between batch and online program design is that online systems should be designed for a high degree of concurrency. At the same time, no compromise should be made to data integrity. In addition, most online systems have design criteria about performance.

[[ Contents Previous Page | Next Page Index ]]