Actually, it's TOO precise. Too much detail, not enough useful information.
There is a joke that is too long to post here but the punchline is "his answer was perfectly accurate and absolutely useless, so I knew it had to be the IBM Building." Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jim McAlpine Sent: Thursday, March 20, 2014 9:30 AM To: [email protected] Subject: Re: APAR OA30338 for PDSE Users Tony, thanks for making me feel a bit better. I was a bit too quick on the trigger but I was in a hurry to get some stuff done and got a bit flustered as a result. I do agree that the error message could have been a bit more precise. Jim On Thu, Mar 20, 2014 at 3:06 PM, Tony Harminc <[email protected]> wrote: > On 20 March 2014 10:48, Jim McAlpine <[email protected]> wrote: > > Thanks Tom, that was the cause of the problem. I logged off TSO and > > back > on > > again and was able to delete the offending dataset. > > > > Sorry for sending everyone off on a wild goose chase. > > Well you didn't exactly have ideal information to work with. I mean, > seriously, "IEC614I SCRATCH FAILED - RC 008, DIAGNOSTIC INFORMATION IS > (043D57D3), SYSACCT,DB2B04,E54I.OLAS.PDEFLIB" is hardly the most > friendly way of saying "dataset is in use by job xxxx" the way other > programs generally do under similar circumstances. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
