Programs performing I/O to files will effect only a *SHRRD [shared
read] lock on the *FILE object; as part of the open -- exception being
open with clear, but clear is not I/O. The *SHRRD lock on the *FILE
would not conflict with any other I/O programs. The conflict must be
either from record locks, or locking outside of I/O [e.g. ALCOBJ; thus
member(data) lock, because again only *SHRRD on the *FILE], or from
operations other than I/O [e.g. CLRPFM, RMVM, etc.].
Doug Palme wrote:
By process I mean programs accessing, changing, updating the
information in the file.
Lock Types are typically file locks......