File lasting access block (FLAB)

The FLAB serves as an anchor for the set of file request thread elements (FRTEs) that belong to a specific file in a given transaction and a given environment.

If a transaction accesses several files from the same environment, there is one FLAB for each file. If a transaction accesses the same file from more than one environment, there is one FLAB for each environment.

The FLAB contains pointers to the FCTE for the file, to the owning FRAB, to the chain of FRTEs owned by the FLAB, and to the next FLAB in the chain of FLABs for the unit of work.

The FLAB is used by file control for the following purposes:
  • To anchor the FRTEs for the file in the unit of work and environment
  • To ensure that a file cannot be closed if there are any FRTEs associated with it, or if there have been recoverable updates made by units of work that have not yet reached syncpoint phase 2
  • To ensure that the corresponding file entry cannot be reallocated to a different data set, even if the file is closed and disabled, when there is uncommitted recoverable work associated with the file
  • To hold READ SET storage control information across intermediate syncpoints
  • To ensure that units of work which have updated the file reach syncpoint before a copy or BWO copy for a file opened in RLS mode is allowed to proceed
  • To record the reason for a failure during syncpoint, and keep track of the fact that the file has uncommitted updates in a unit of work as a result of the failure

The file lasting access block is built by DFHFCFR as part of processing of the first file control request for a specific file in a given transaction and environment. FLABs for recoverable files are also rebuilt by DFHFCIR at warm and emergency restart.

The storage for the FLAB is obtained from a FLAB storage subpool in 31-bit storage.

The FLAB is deleted after all the FRTEs have been processed during syncpoint terminate processing, providing that there have been no syncpoint failures for the file in the unit of work. The FLAB storage is not returned to the FLAB storage subpool, but is instead added to a chain of free FLABs, anchored from file control static storage. Subsequent requests to build a FLAB are, if possible, satisfied by a quick cell mechanism from this chain.

If a unit of work is shunted as a result of a syncpoint failure, the FLABs for any files which suffered the syncpoint failure are also shunted.

The chain of FLABs for a unit of work is anchored from field FRAB_FLAB_CHAIN_ADDRESS in the FLAB.

The layout of the FLAB is defined by the DFHFLAB structure and the DFHFLAB DSECT.



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