P seudoconversational transactions

A pseudoconversation normally involves a series of transactions, each initiated by the previous transaction, which may also pass some data. The name of the next transaction to be run can be defined by the user transaction in different ways.

  1. EXEC CICS RETURN TRANSID
  2. EXEC CICS RETURN TRANSID IMMEDIATE
  3. EXEC CICS START TRANSID TERMID
  4. EXEC CICS SET TERMINAL/NETNAME NEXTTRANSID
  5. Terminal data
Note: Transactions initiated by START TERMID are not necessarily pseudoconversational. Here we are considering only those transactions initiated by a START to the principal facility (the bridge facility) where the STARTING and STARTED applications are associated in a pseudoconversation. In this case, START TERMID must specify the bridge facility.

Commands 1-4 all cause the bridge mechanism to set the next transaction identifier in the BRIH-NEXTTRANSACTIONID field to be returned to the client in the next response message.

The client responds by sending a run request for the next transaction, with BRIH-TRANSACTIONID set to the value from BRIH-NEXTTRANSACTIONID and BRIH-FACILITY set to the value returned on the allocate request. The following parameters may also be optionally defined:
  • BRIH-DATALENGTH (if BRIV vectors are appended to the message)
  • BRIH-CONVERSATIONALTASK
  • BRIH-GETWAITINTERVAL (if conversational)
  • BRIH-ADSDESCRIPTOR
  • BRIH-ATTENTIONID
  • BRIH-CURSORPOSITION
Other fields in the BRIH are ignored.
Note: The same bridge facility must be used by all transactions in the pseudoconversation.