At 13:21 -0500 on 04/07/2009, Martin Kline wrote about Temporary Data
Set Duplicate Name Bahavior:
Sure, there are multiple ways to avoid this issue, such as using
different temp
names or using DISP=(OLD,DELETE) in steps 2 and 4. That's not the issue.
That's already taken care of.
The issue is that the behavior is unexpected and contrary to the
documentation. Has anyone run into this before and found the behavior
documented somewhere?
You had a DISP of PASS in step 2 and thus when you reference the
dataset in step 4 it gets the step 2 copy not the step 3 one (since
it is the first &TEMP dataset found). What is showing in the final
status listing for at JOB Term? I'd expect that both &TEMPs would be
listed and shown as deleted with different VOLSERs.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
