Using the PL/I Preprocessor - IBM CICS Interface for Teradata

IBM CICS Interface for Teradata® Reference

IBM CICS Interface for Teradata
Release Number
June 2020
English (United States)
Last Update
Product Category
Teradata Tools and Utilities

When using PL/I Preprocessor1 with the CICS Interface, and writing a pseudo-conversational program that links or transfers control to another program processed by the PL/I Preprocessor1, the structure DBCCONS defined within DBCBUFFER (sent by the PL/I Preprocessor1) must be included in the CICS COMMAREA.

The COMMAREA is specified either on RETURN to CICS in a transid or in a CICS LINK statement.

This communication data must move to DBCCONS on any entry when the COMMAREA length is non-zero.

DBCLEN defines the length of the DBCCONS structure, which the PL/I preprocessor generates; it equals 516 bytes.

The DBCCONS structure generated by the PL/I preprocessor is placed immediately before the first occurrence of ACTIVITYCOUNT, ERRORMESSAGE, or the RETURNCODE preprocessor statements.

DBCCONS information is not relevant to the PL/I Preprocessor2.

The symbol DFHCOMMAREA is used to name the CICS communications area structure.

See Sample CICS PL/I Program for an example of a PL/I program using the Preprocessor2 with CICS.

With respect to the PL/I Preprocessor1, note that when data returns from the database, preprocessor runtime code routes data to the structure DBCBUFFER and to the variables identified between the DATA-BEGIN and DATA-END statements in the application program.