Re: (Legacy) MVS vs. OMVS was: Re: remove() of PDSE member leaves PDS locked

2010-08-03 Thread Shmuel Metz (Seymour J.)
In , on 08/02/2010 at 08:04 AM, Paul Gilmartin said: > READY >allocate path('/u/me/nonesuch') > IKJ56228I PATH /u/me/nonesuch NOT IN CATALOG OR CATALOG CAN NOT BE >ACCESSED That probably comes from DAIRFAIL rather than DYNALLOC. Was the PMR against TSO/E? -- Shmuel (Seymour J.) Metz,

Re: (Legacy) MVS vs. OMVS was: Re: remove() of PDSE member leaves PDS locked

2010-08-02 Thread Shmuel Metz (Seymour J.)
In , on 08/02/2010 at 04:15 AM, Barbara Nitz said: >You've provided me with an excellent example for my statement above. >Because that message is issued by TSO (IKJ prefix) or rather, by >dynalloc which uses some DAIR interfaces into TSO. DAIR uses DYNALLOC; DYNALLOC does not use DAIR. I sus

Re: (Legacy) MVS vs. OMVS was: Re: remove() of PDSE member leaves PDS locked

2010-08-02 Thread Paul Gilmartin
On Mon, 2 Aug 2010 08:12:50 -0400, Shmuel Metz (Seymour J.) wrote: >In , on 08/02/2010 > at 04:15 AM, Barbara Nitz said: > >>You've provided me with an excellent example for my statement above. >>Because that message is issued by TSO (IKJ prefix) or rather, by >>dynalloc which uses some DAIR int

(Legacy) MVS vs. OMVS was: Re: remove() of PDSE member leaves PDS locked

2010-08-02 Thread Barbara Nitz
>>The reason *I* hate OMVS is that those using it via some >>C/C++/JAVA/whatever-clickable-stuff have no clue how things are >>implemented in z/OS. So in case of an error they take any return code/reason >>code they get at face value. Unfortunately, that is the completely *wrong* >>way to go abou