Back-end transaction initiation

The back-end transaction is initiated either by an attach header received from the partner system or by a transaction name included in the incoming data, and is started with the session as its principal facility.

Initially, the back-end transaction should determine the convid from EIBTRMID. This is not strictly necessary because the session is the back-end transaction’s principal facility making the CONVID parameter optional for DTP commands on this conversation. However, the convid is very useful for audit trails. Also, if the back-end transaction is involved in more than one conversation, then always specifying the convid improves program readability and problem determination.

A CICS® transaction can be the back-end transaction in CICS-to- IMS™ communication only in the special case of SEND/RECEIVE asynchronous processing. The transaction is initiated by an LUTYPE6.1 attach FMH received from the remote IMS system, and is allowed to issue a single RECEIVE command only, possibly followed by an EXTRACT ATTACH command.

It is possible that the back-end transaction might fail to start. This will result in the front-end transaction abending.



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