If a second request requires a record that is in a buffer in which a previous request is positioned, the second request may fail with an exclusive control error (RPLERRCD field at RPL +X'0F' = X'14'). If a message area is provided in the second RPL, VSAM record management returns the address of the RPL that has the position of the resource in the message area of the second RPL. You are responsible for relinquishing position in the initial RPL before redriving the second RPL.

An exclusive control conflict can also arise if an initial request causes a CI or CA split. A second request may receive RPLERRCD = X'14' as just mentioned, if it needs a record in the same CI or CA. You should either wait for completion of the request whose RPL is pointed to by the second RPL's message area, or issue "ENDREQ" against the RPL pointed to by the second RPL's message area before redriving the second request.

An apparent exclusive control conflict can also occur when the program is inserting a new record or updating an existing record to a compressed VSAM data set with spanned records, even though no other I/O is occurring against this data set. This occurs because of a CI or a CA split. Following the split, positioning is lost and must be reestablished, resulting in an RPL feedback word of x'D4080014'. This situation is similar to an exclusive control conflict, and requires that the VSAM user re-drive the request.