Sync pointing

The sync point cost needs to be factored into the overall transaction cost. The amount of work at sync point varies according to the number of different types of resource managers involved during the unit of work (UOW). Therefore, the cost can vary.

Typically, a sync point calls all the resource managers that have been involved during the UOW. These might have to place data in the log buffer before it is written out. For example, recoverable transient data (TD) defers putting data into the log buffer until a sync point. Recovery manager itself puts commit records into the log buffer and requests a forced write. For these reasons it is difficult to give a precise cost for a sync point, but the following information should be used as a guide:

A sync point can be split as follows:

Part Value
Basic cost 5.0
Put commit records in the log buffer 2.0
For each RM used in UOW 2.5
Write log buffer See Logging

This table shows sync point costs, in 1K instruction units, for local resources only. If distributed resources are updated, communication costs must added.

If no recoverable resources have been updated, the only cost is the transaction termination cost:

Transaction cost Assembler COBOL
Termination 6.2 10.0
Note: The transaction initialization cost is calculated from the start of transaction attach to the start of the CICS® application code. If recoverable resources have been updated, the sync pointing cost must be added to the termination cost.


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