On Jan 9, 2008, at 7:29 AM, Richbourg, Claude wrote:
Well, thanks to all that responded and yes, I deleted the dataset.
The dataset in question was a duplicate of a cataloged dataset. I
submitted the delete job after I had the user log off TSO. It worked
well, dataset gone. Evidently I did not dig deep enough to reason out
the codes.
But, I won't forget that one.
Thanks again to all who responded to help solve my temporary problem
child.
Regards,
Claude Richbourg
Claude,
Don't worry about that. About 30 years ago I had a similar problem
with VSAM and could not get rid of the data set and indeed I logged
off and then on and suddenly I was able to delete it. Only with mine
I wasn't getting any error codes or return codes. I would enter the
delete command and it would come back with a zero and I would look
and it would still be there. This was in the early days of MVS and I
chalked it up to either me or a bug in the software. We were under
pressure to get the job done and get rid of the issue asap. I would
have run traces to figure out the problem any other time. I did not
mind do the debugging at all, the user was an important person in HQ
so we had to treat him with TLC. I could not reproduce the problem
later no matter how hard I tried. It may have been issue with vsam
volume ownership the code was kind of flaky (for VSAM) around that
time. Plus we were trying out the precursor to SDSI at the time.
Ed
----------------------------------------------------------------------
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
