At 18:16 -0500 on 04/05/2012, Walt Farrell wrote about Re: A deep
question about VSAM SHR(4) - can you help?:
This option requires that the user's program use ENQ/DEQ to maintain
data integrity while sharing the data set, including the OPEN and
CLOSE processing. User programs that ignore the write integrity
guidelines can cause VSAM program checks, lost or inaccessible
records, uncorrectable data set failures, and other unpredictable
results. This option places responsibility on each user sharing the
data set.
</quote>
So unless there's something in CICS issuing appropriate ENQ/DEQ
macros, I think you'll need to make some program changes.
You are misreading the restrictions. This has to do with sharing the
VSAM Cluster between multiple programs NOT sharing the Cluster
between multiple tasks of the same program (as would be the case with
CICS). You are using ONE ACB so there is no interlock issue. I am not
sure what QNAME/RNAME is supposed to be used for the interlock. VSAM
itself does the ENQ/DEQ (I think) via using the CI number (it can not
be the key of the record because while that would prevent multiple
updates to that record, you can mess up the CI if there are two
records in the CI being updated) as part of the RNAME (it has been a
while).
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
