Access method control block (ACB)
The ACB identifies the file that is associated with this VSAM request to VSAM.
It is passed to VSAM by DFHFCRV for RLS, or DFHFCVR for non-RLS (it is the RPL, which points to the ACB, that is passed) to initiate a VSAM request. The ACB lasts as long as the associated CICS® file is open; that is, it is created at file open time and deleted at file close time by DFHFCN for non-RLS, or DFHFCRO for RLS.
The ACB is addressable through a pointer in the associated FCT entry. In addition, a 4-byte field appended (by CICS) to the ACB structure points back to this FCTE.
Note that the ACB is a VSAM control block.
At open time, storage is obtained from a subpool in 31-bit storage. A VSAM GENCB macro is issued to generate the ACB with attributes obtained from the FCT entry. At open time, VSAM fills in more information in the ACB. Some of this is subsequently copied back into the FCTE.
The storage for the ACB is freed when the file is closed.
There is one ACB per VSAM FCT entry.
The layout of the ACB is defined by the VSAM IFGACB structure, and also by a DSECT of the same name.
ACBs are not cataloged and are not restored across WARM or emergency starts. The ACB is rebuilt every time a CICS file is opened.
A special type of ACB, known as a base cluster ACB, is created by DFHFCM to allow for the implicit opening of a base cluster, when required by a non-RLS file access through an alternate index path. In this case, the 4-byte field appended to the ACB structure points to the associated DSNAME block for the base cluster.
A second special type of ACB, known as a control ACB is required for VSAM RLS processing. Storage for the control ACB is obtained by DFHFCCA and filled in using the GENCB macro before registering the control ACB. The storage is freed when the control ACB is unregistered by DFHFCCA. The control ACB is passed to VSAM on calls issued by DFHFCCA. It is used for all requests that are not associated with a specific file.