Notes to Teleprocessing Monitor Users

Notes to Teleprocessing Monitor Users

This appendix describes special considerations relating to application programs running under teleprocessing (TP) monitors supported by CA IDMS (that is, CICS, INTERCOMM, SHADOW, TASK/MASTER, UTM, and WESTI).

This section contains the following topics:

TP Monitor Coding Guidelines

TP monitor Coding Requirements

TP Monitor Coding Guidelines

While there are no special coding requirements for TP monitor transactions, the following guidelines should be adhered to:

• DML statements should be coded such that all database requests (for example, BIND, READY, OBTAIN, FINISH) are executed together whenever possible to achieve maximum efficiency and ease of recovery.
• For each TP monitor, you should check with the DBA to determine the operating mode (protocol) installed. The proper mode must then be specified in the IDMS-CONTROL SECTION of the ENVIRONMENT DIVISION.
• For CICS, INTERCOMM, SHADOW, UTM, and WESTI applications, the mode as installed may require the inclusion of additional statements in the IDMS-CONTROL SECTION, WORKING-STORAGE SECTION, and LINKAGE SECTION of each program. These requirements and the applicable modes are outlined in the following table.

  Note: The same rules apply to the COPY IDMS statements used to insert logical-record source code components into the program: IDMS-RECORDS MANUAL should be coded in the ENVIRONMENT DIVISION; SUBSCHEMA-LR-NAMES should be copied into the WORKING-STORAGE SECTION; and SUBSCHEMA-CTRL, SUBSCHEMA-LR-CTRL, and SUBSCHEMA-LR-RECORDS should be copied into the LINKAGE-SECTION (except under CICS-EXEC or CICS-EXEC-AUTO, when all required components should be copied into the WORKING-STORAGE SECTION).

• The DML compiler should be executed before the teleprocessing monitor preprocessor.

TP monitor Coding Requirements