View figure.The hardware and software needed to run the DB2 Server for VSE system varies depending on the usage of the DB2 Server for VSE system.
Depending on your requirements, your DB2 Server for VSE environment may be set-up in different ways. The purpose of this chapter is to give you an idea of the various different usage environments that can be set up. Further information about how to set up various DB2 Server for VSE environments can be found in the DB2 Server for VSE System Administration manual.
This chapter describes five different DB2 Server for VSE usage environments. You will need to consider each of these environments and choose the one appropriate for your processing requirements. It also describes the recommended and required options of the associated program products.
Figure 53. Batch/Interactive Configuration
View figure.
Batch/interactive processing ( Figure 53) is mostly execution of compiled PL/I, COBOL, C, FORTRAN or assembler programs which are batch (or VSE/ICCF) SQL applications. Some dynamic SQL processing may occur in the form of application preprocessing and compilation, and DBS Utility executions.
Operation of this type of system places minimal demands on system resources (real storage and processor power). However, there is a corresponding loss of function, because such a system cannot support the query/report writing facilities (ISQL) of the DB2 Server for VSE or online (CICS) transaction processing with DB2 Server for VSE.
There are no special prerequisites beyond the base DB2 Server for VSE prerequisites for VSE/Advanced Functions and VSE/VSAM except that one of the supported programming languages (PL/I, COBOL, C, FORTRAN, or assembler) is required. VSE/ICCF is not required, but it can be used for terminal access and invocation of the SQL applications, and for data administration activities.
A batch/interactive system should be considered for automation of fixed business applications that do not require end user access to the system. Such a system is typically developed on a larger system that is configured to support application development.
Figure 54. Online Transaction Processing Configuration
View figure.
Online transaction processing usage of the DB2 Server for VSE system (Figure 54) is mostly preplanned CICS SQL transactions. Some dynamic SQL processing may occur in the form of SQL/DS preprocessor and DBS Utility jobs, which do not run under the CICS subsystem.
Like the batch/interactive application processing usage, the online transaction processing usage demands fewer real storage and processor resources than dynamic SQL usage demands.
Online transaction processing with the DB2 Server for VSE system requires installation of |CICS Release 2.3, or an equivalent transaction processing product. The DB2 Server for VSE online support must also be installed. The CICS subsystem provides the terminal management and transaction processing environment. Programs may be written in PL/I, COBOL, C, or assembler, but not FORTRAN as the CICS subsystem does not support FORTRAN. You can, however, use FORTRAN for batch programs.
An online transaction processing system should be considered for preplanned business applications where end user access to the system is managed through CICS transactions programmed for specific end user tasks.
ISQL might be installed, but its use would be limited to data administration functions.
For the online transaction processing environment, the system should be configured as follows:
It is not required for report writing to CICS terminal printers. Only the VSE/POWER program provides multiple copy capability.
Figure 55. Application Development Configuration
View figure.
Application development usage of the DB2 Server for VSE system ( Figure 55) includes a large amount of data design, application coding, and testing. Such activities typically involve a modest level of dynamic SQL activity in the form of data definition, catalog queries, and program preprocessing. Correspondingly, there is more demand for real storage and processor resources, than that demanded by application or transaction processing.
The program products required to support application development on the DB2 Server for VSE system vary depending on the type of application being developed and the DB2 Server for VSE facilities to be used. The optional program products and their options are discussed below in terms of their value to application development usage of the DB2 Server for VSE system.
For development of programmed applications you would need one or more of the PL/I, COBOL, C, FORTRAN, or Assembler language products.
You can install VSE/ICCF (or an equivalent) to support an interactive application development capability.
The CICS subsystem is required to support development of CICS transactions or use of the ISQL facilities for application development. It should be generated with the dynamic transaction backout program (DBP), the EXEC interface program (EIP), and the CICS user exit interface. Optionally, you can generate it with the Monitoring Facility and Restart Resynchronization. Restart resynchronization is required if you want to (1) use the SQL/DS accounting facility in an online environment, and (2) support task-related user exits.
The VSE/POWER program is required for the system printer or remote workstation printer report-writing support in ISQL. It is not required for report writing to CICS terminal printers. Only the VSE/POWER program provides multiple copy capability.
Figure 56. Query/Report Writing Configuration
View figure.
The query/report-writing usage environment supports dynamic SQL query and report writing by end users. Due to the dynamic interpretation of user requests and the fact that data requests are unconstrained, this usage environment places a relatively high demand on system resources. The internal sort capability of the DB2 Server for VSE database manager is likely to be used frequently.
The program products and options required to support this environment are as follows:
ISQL operates as a set of CICS transactions. The CICS subsystem should be generated with the following options:
The VSE/POWER program is required for the system printer or remote workstation printer report-writing support in ISQL. It is not required for report writing to CICS terminal printers. Only the VSE/POWER program provides multiple copy capability.