On Tue, 8 Oct 2019 16:15:38 +0000, Pesce, Andy wrote: >I have "JOBA" that executes a COBOL program to update a particular member in a >PDS. Within the program, it calls an internal utility that someone >wrote years ago that puts an enqueue on the dataset and its member that it is >updating. The dd associated with the parmlib uses DISP=SHR. > >I have "JOBB" that executes a COBOL program to do the same thing, but it is a >different member within the same dataset as "JOBA". It is coded >to open the dataset as I/O. After it reads the member, it then does a >REWRITE. It doesn't follow the rules as above and use the internal utility. >The dd associated with the parmlib also uses DISP=SHR. > >Here is the issue. Occasionally the member in "JOBA" is becoming "empty", >while the member in JOBB is always OK. I have looked at SMF >records and I see these jobs run at the same time. And it is usually the same >down to the hundreds of seconds. > >My suggestion was that JOBB needs to be fixed to use the "enqueue and dequeue" >utility, since it is using DISP-SHR. This parmlib is >used heavily and extensively by applications, and no way to get it DISP=OLD. >Any thoughts or explanation would truly be appreciated.
Your ENQ on DSNAME+member will not help you when the two jobs are updating a different member. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
