Checking the outcome of a DTP command

Checking the response from a DTP command can be separated into two stages:

  1. Testing for request failure
  2. Testing for indicators received on the conversation.

Testing for request failure is the same as for other EXEC CICS® commands in that conditions are raised and may be handled using HANDLE CONDITION or RESP. EIBRCODE will also contain an error code.

If the request has not failed, it is then possible to test for indicators received on the conversation. These are returned to the application in the EIB. The following EIB fields are relevant to all DTP commands. (See the CICS Application Programming Reference for programming information on the contents and format of EIB fields.)

EIBFREE
when set to X'FF' indicates that the partner transaction has ended the conversation. It should be tested in conjunction with EIBSYNC to determine exactly how to end the conversation.
EIBSYNC
when set to X'FF' indicates the partner transaction/system has requested a syncpoint.

Table 43 shows how these EIB fields interact.

Table 43. Interaction of some EIB fields
EIB- FREE EIB- SYNC Description
X'FF' X'00' The partner transaction or system has sent SEND LAST followed by a FREE command.
X'FF' X'FF' The partner transaction or system has issued SEND LAST followed by SYNCPOINT. The local program should reply with a SYNCPOINT command followed by a FREE command.
X'00' X'FF' The partner transactions or system has issued a SYNCPOINT.

In addition, there is a group of EIB fields that are relevant only to the RECEIVE and CONVERSE commands. These are:

EIBCOMPL
when set to X'FF' indicates that all the data sent at one time has been received. This field is used in conjunction with the RECEIVE NOTRUNCATE command.
EIBRECV
when set to X'FF' indicates the partner transaction did not use the INVITE option on its last SEND command.
EIBATT
when set to X'FF' indicates that the data received contained an attach header. The attach header is not passed to the application; however, EIBATT indicates that an EXTRACT ATTACH command is appropriate.
EIBFMH
when set to X'FF' indicates that the data passed to the application contains a concentrated FMH. This happens only when the partner CICS transaction builds an FMH in the data and the FMH option on the SEND command is specified.
Note:
Profiles specifying INBFMH (ALL) must be used in the ALLOCATE commands if FMHs are to be sent and received and EIBATT or EIBFMH to be sent appropriately. The default profile DFHCICSA used for the session allocated by the front-end transaction, has INBFMH (ALL) specified. However, the default principal facility profile DFHCICST used for the back-end transaction does not have INBFMH (ALL) specified.
[[ Contents Previous Page | Next Page Index ]]