View previous topic :: View next topic
|
Author |
Message |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
did You care to read Pandora-box quote from the manual ??? |
|
Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
|
|
|
|
OUTDATASET worked because it was using the "new" VSAM dataset.
Read what people have posted. If you have to use OUTDD, you'll need to either not delete it at all, or delete/define in a previous step.
Choice from those options is yours, but you can't choose a different option which doesn't work, and which is documented as not working. |
|
Back to top |
|
|
Sheerin banu
New User
Joined: 10 Apr 2013 Posts: 10 Location: INDIA
|
|
|
|
Thanks all for your valuable comments .. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Quote: |
Hi , when i gave REPRO in differnt step it worked , but cant i use in same step ... ?
I think OUTDATASET worked with same step because it makes a exclusive lock on the DATASET ..
correct me if im wrong.
Also to clarify the file i delete is same as the file i create . |
You are wrong. OUTDATASET works because it is referencing the NEW data set, not the OLD data set. Putting the REPRO (or the DELETE) in a separate step works because you are then referencing the NEW data set with the OUTFILE. Putting it all in one step will not work because JES allocates the files before the step executes, so using OUTFILE means you are attempting to write data to a data set that no longer exists -- hence the 168 return code.
And the file you delete is the same you create -- we got that the first post. However, the file you REPRO to is not the same as the file you create when using OUTFILE in the same step. This is what you did not get. |
|
Back to top |
|
|
|