Back-end transaction initiation

A back-end transaction is initiated as a result of the front end’s GDS CONNECT PROCESS command.

Initially the back-end transaction should determine the convid. Figure 1 shows a fragment of a back-end transaction that uses the EXEC CICS GDS ASSIGN command to obtain the convid. The back-end transaction can also obtain the transaction identifier and sync level used to start the conversation. The GDS EXTRACT PROCESS command is used to obtain this information.

The back-end transaction starts in receive state (state 5). So, after obtaining the convid, the back-end transaction can issue a GDS RECEIVE command.
Figure 1. Startup of a back-end transaction
* ...
EXEC CICS GDS ASSIGN PRINCONVID(WCONVID) RETCODE(WRETC)
*
* ...
*
EXEC CICS GDS EXTRACT PROCESS CONVID(WCONVID) *
PROCNAME(WPROC) *
RETCODE(WRETC) *
PROCLENGTH(WLENPROC) *
SYNCLEVEL(WSYNCLVL)
* ...
* Receive first data from front-end transaction.
* ...
*
WSTATE DS F
WRETC DS XL6
WCDB DS 0CL24
COPY DFHCDBLK
WCONVID DS CL4
WPROC DS CL4
WLENPROC DS F
WSYNCLVL DS F
* ...


dfhp61p.html | Timestamp icon Last updated: Monday, 5 June 2017