Synchronization

DPL provides two ways to handle synchronization:

  1. If you code SYNCONRETURN, the linked-to program commits its resource updates immediately before returning control to the linking program. There are separate units of work in the two communicating systems.

    The linked-to program may take one or more syncpoints during its execution. However, the response the linking program is given (which may be Normal or Rollback) corresponds to the outcome of the syncpoint taken by CICS® on return from the linked-to program, and does not relate to the outcome of any of the syncpoints the linked-to program may have initiated.

  2. If you do not code SYNCONRETURN, the linking program initiates commitment in both systems, either by issuing a SYNCPOINT command or implicitly at task end.

Data integrity considerations govern the decision whether or not to use the SYNCONRETURN option.

Related concepts
Introduction to DPL
Why use DPL?
DL/I and SQL databases
Restrictions when using DPL
Abends when using DPL
Related reference
CICS product communication support
[[ Contents Previous Page | Next Page Index ]]