Notes

Notes to Teleprocessing Monitor Users › Notes

Notes

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

DML statements should be coded so 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 MODE clause of the DECLARE SUBSCHEMA statement.
The DML precompiler should be executed before the TP-monitor precompiler.
For CICS, INTERCOMM, and SHADOW applications, the mode, as installed, may require the inclusion of additional statements in each program. These requirements and the applicable modes are outlined in the following table.
Note: The same rules apply to the INCLUDE IDMS statements used to insert logical-record source code components into the program: SUBSCHEMA_CTRL, SUBSCHEMA_LR_CTRL, and SUBSCHEMA_LR_RECORDS should be copied into the program (except under CICS_EXEC, components should be copied into the program).

TP monitor	If mode is...	Code these statements
CICS	CICS_STANDARD	DECLARE 1 TWA BASED (TPTR), 3 FILLER, 3 INCLUDE IDMS(SUBSCHEMA_CTRL), 3 INCLUDE IDMS(SUBSCHEMA_RECORDS), ADDRESS TWA(TPTR); or *INCLUDE IDMS(SUBSCHEMA_CTRL); INCLUDE IDMS(SUBSCHEMA_RECORDS); (A CICS GETMAIN must be issued for the SUBSCHEMA_CTRL and for each RECORD being copied.) INCLUDE IDMS(IDMS_WAIT);
CICS	CICS_EXEC	INCLUDE IDMS(SUBSCHEMA_CTRL); INCLUDE IDMS(SUBSCHEMA_RECORDS);
INTERCOMM	INTERCOMM	INCLUDE IDMS(SUBSCHEMA_CTRL); INCLUDE IDMS(SUBSCHEMA_RECORDS);
SHADOW	SHADOW	INCLUDE IDMS(SUBSCHEMA_CTRL); INCLUDE IDMS(SUBSCHEMA_RECORDS);

* If SUBSCHEMA_CTRL, SUBSCHEMA_RECORDS, and additional data does not exceed 4,096 bytes.

** If SUBSCHEMA_CTRL, SUBSCHEMA_RECORDS, and additional data exceeds 4,096 bytes.