Sorry about the delay in responding. I had a network issue that was not resolved until now.
The correct order is 1) Allocate new VSAM Temp file 2) Split off the archive records to a GDG, and the records to be reloaded into the VSAM Temp File. 3) Del/Def the original file name 4) Repro the VSAM Temp back into the Original name Yes, the original is the one that is enqueued. I should have used the term TEMP rather than NEW in my example. This is a process that will archive of older records from the vsam dataset to a GDG and also create a temp VSAM data set that holds the records to get loaded back into the file (don't ask, this is the vendor's process). The main reason for this posting is to see if this is still annoying. That you can get the message DATA SET IN USE, but that the process is so quick there is no trail of the holder. And from this discussion it seems this is still an issue. Thanks for all the good commentary. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf > Of Tom Marchant > Sent: Friday, March 08, 2013 12:52 PM > To: [email protected] > Subject: Re: Enqueue during VSAM REPRO - Who is the culprit > > On Fri, 8 Mar 2013 12:20:07 -0700, Lizette Koehler wrote: > > >I create a new VSAM file. Then I REPRO current to new. > > > >Sometimes (not always) when this job runs I get > > > >REPRO IDS(NEW.VSAM.FILE) - > >. ODS(CURRENT.VSAM.FILE) REUSE > >.IKJ56225I DATA SET CURRENT.VSAM.FILE ALREADY IN USE, TRY LATER > >.IKJ56225I DATA SET IS ALLOCATED TO ANOTHER JOB OR USER > > Just to be clear.... > > Is the data set that shows as being in use the new one or the old one? > > Your example seems to show that you are trying to REPRO from the new to the > old, > and I assume that is not what you meant. > > -- > Tom Marchant > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
