The CSDINTEG parameter specifies the level
of read integrity for the CSD if it is accessed in RLS mode.
- CSDINTEG={UNCOMMITTED|CONSISTENT|REPEATABLE}
- If the CSD is not accessed in RLS mode (CSDRLS=NO), a value for CSDINTEG
of CONSISTENT or REPEATABLE will be changed to UNCOMMITTED.
- UNCOMMITTED
- The CSD is read without read integrity. For each read request, CICS obtains
the current value of the record as known to VSAM. No attempt is made to serialize
this read request with any concurrent update activity for the same record.
The record returned may be a version updated by another RDO task but not yet
committed, and this record could change if the update is subsequently backed
out.
- CONSISTENT
- CICS reads the CSD with consistent read integrity. If a record is being
modified by another RDO task, the READ request waits until the update is complete,
the timing of which depends on whether the CSD is recoverable or non-recoverable:
- For a recoverable CSD, the READ request completes when the updating transaction
completes its next syncpoint or rollback.
- For a non-recoverable CSD, the READ completes as soon as the VSAM request
performing the update completes.
- REPEATABLE
- CICS reads the CSD with repeatable read integrity. If the record is being
modified by another RDO task, the READ request waits until the update is complete,
the timing of which depends on whether the CSD is recoverable or non-recoverable:
- For a recoverable CSD, the READ request completes when the updating transaction
completes its next syncpoint or rollback.
- For a non-recoverable CSD, the READ completes as soon as the VSAM request
performing the update completes.
After the CSD read completes, a shared lock remains held until syncpoint.
This guarantees that a CSD record read within an RDO task cannot be modified
until the end of the task (for example, a CEDA transaction) that is reading
the CSD.