z/OS MVS Programming: Writing Transaction Programs for APPC/MVS
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Confirmation of a Transaction

z/OS MVS Programming: Writing Transaction Programs for APPC/MVS
SA23-1397-00

Figure 1. Example of a Confirmed Transaction
┌─────────┐                                 ┌─────────┐
│ PROGRAM │                                 │ PROGRAM │
│         │←───────────────────────────────→│         │
│    A    │                                 │    B    │
└─────────┘                                 └─────────┘

Call ATBALC2           1 
  TP_NAME(B)
  SYNCLEVEL(CONFIRM)

Call ATBSEND           1 

Call ATBCFM (Confirm)  3   ─────────────────→ (LU STARTS PGM B)
  .                       ALLOC, DATA, CONFIRM
  .                                        4  Call ATBGETC
  .
  .                                        5  Call ATBRCVW
  .                                           DATA_RECEIVED=DATA_COMPLETE
  .                                           STATUS_RECEIVED=CONFIRM
  .
  .
  .
RC=OK         7  ←───────────────────────  6  Call ATBCFMD Confirmed)
                             CONFIRMED

Call ATBSEND  8                           Call ATBRCVW
                                              .
                                              .
                                              .
A transaction program can request that its partner confirm that all the data sent so far has been received and processed successfully. In Figure 1:
  1. Program A allocates a conversation with program B, setting the Sync_level parameter to CONFIRM to allow confirmation processing on the conversation.
  2. Program A sends data to program B.
  3. Program A calls the Confirm service. The confirmation request forces the LU to send buffered data.
  4. Program B calls the Get_Conversation service to accept the conversation.
  5. Program B receives the data, checking for completion, and the status received. The status indicates that a confirmation has been requested.
  6. Program B calls the Confirmed service, granting the confirmation. It could have sent an error notification instead, if something was wrong.
  7. The confirmation results in a return code of OK for program A's confirmation request.
  8. Program A continues sending data.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014