Running transactions

To run transactions in session mode, your client program must supply the name of the user transaction in the BRIH_TRANSACTIONID field of the bridge message header (BRIH), and set BRIH-FACILITY to the value returned by the allocate request.

The following parameters may also be optionally defined:
  • BRIH-DATALENGTH
  • BRIH-CONVERSATIONALTASK
  • BRIH-GETWAITINTERVAL
  • BRIH-ADSDESCRIPTOR
  • BRIH-ATTENTIONID
  • BRIH-STARTCODE
  • BRIH-CURSORPOSITION
Other fields in the BRIH are ignored.
For example, to run transaction NACT using the supplied default BRIH and constants:
Working-Storage Section..
copy dfhbrico..
Linkage Section.
01 msg-area.
copy DFHBRIHO.
03 msg-vectors pic x(2000)..
Procedure Division.
move brih-default to msg-area
move 'NACT' to brih-transactionid
move facility to brih-facility
move brih-datalength to len
EXEC CICS LINK PROGRAM('DFHL3270') COMMAREA(msg-area)
LENGTH(length of msg-area) DATALENGTH(len)
END-EXEC..
Your client program must also create BRIV vectors for any input commands. For example:
 move briv-receive-map-default to briv-in.
move 'DFH0MNA ' to briv-rm-mapset.
move 'ACCTMNU ' to briv-rm-map.
move '422' to briv-rm-cposn.
move length of acctmnui to briv-rm-data-len.
set address of acctmnui to address of briv-rm-data.
move low-values to acctmnui.
add briv-rm-data-len to briv-input-vector-length.
add briv-input-vector-length to brih-datalength.
Note: When adding a BRIV always remember to increment the BRIH-DATALENGTH


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