The duplication exists in the data, not in the index. On Tue, 19 Jan 2021 at 18:22, Cameron Conacher <conac...@gmail.com> wrote:
> A KSDS with duplicate full primary key values? > Are you sure? > > Sent from my iPhone > > > On Jan 19, 2021, at 10:19 AM, Steff Gladstone <steff.gladst...@gmail.com> > wrote: > > > > Greetings, > > > > We are trying to figure out how a VSAM file became compromised. That is, > > even though the primary key is unique, when we do a REPRO, we see that > the > > data contains an extra record with the same key. > > > > The file is updated from two different computers via a batch COBOL > program. > > The share options are (4,3) and an enqueue (with parameter SYSTEMS) is > > performed (using an assembler subroutine) before any update is done. The > > site has a 3rd-party product from CA that propagates the ENQ from one > > computer to the other. We even tested the ENQ and saw that an update > from > > the second computer was blocked when the first computer previously issued > > an ENQ prior to its update. > > > > It looks as if an update in one computer has not been committed from > memory > > to disk before the update in the second computer occurs. Which > definitions > > are lacking that would prevent this from happening? > > > > Thanks in advance, > > Steff Gladstone > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
