On Tue, 5 Apr 2011 08:06:50 -0500, Paul Gilmartin wrote:
>Thanks for the research. The messages indicate that your HLQ is
>SMS managed. Mine isn't. I suspect that can make the difference.
I did a test with non-SMS managed datasets. The end result is indeed not
quite as expected, and the behav
On Mon, 4 Apr 2011 05:29:26 -0500, Jan MOEYERSONS wrote:
>
>I've run your example here and it behaves exactly as I expected:
>- the allocate dd(atomic) new delete dsn(TEMP.DUP1) fails because the
>dataset already exists.
>- the delete TEMP.DUP1 simply deletes it.
>- the rename TEMP.DUP2 TEMP.DUP1
On Thu, 31 Mar 2011 23:50:43 -0500, Paul Gilmartin
wrote:
>A recent thread here mentioned "atomic rename" of Classic data sets.
>I don't think there is such a thing, but I tried to synthesize it
>with:
>
I've run your example here and it behaves exactly as I expected:
- the allocate dd(atomic)
>Indeed. But even nonsensical constructs should produce predictable
>results.
LOL. I didn't mean to say otherwise.
--
Peter Hunkeler
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama
On Fri, 1 Apr 2011 13:55:49 +0200, Hunkeler Peter (KIUP 4) wrote:
>>Afaik delete is done at unallocation of the dd. So the free command
>>should follow the allocate one. But why not just deleteing the
>>dataset without first allocating it?
>
My expectation was that if the DSN preexisted and was c
>Afaik delete is done at unallocation of the dd. So the free command
>should follow the allocate one. But why not just deleteing the
>dataset without first allocating it?
I was trying to recreate the situation gil describe in his original
post. My first thought was the delete will not work beca
>there is nothing here to loop, me thinks you've mistaken an
>enqueue/allocation issue with a loop. ya need a DO
>WHILE/UNTIL or similar in order to get a loop.
>
>what appears in the systsprnt? and jes logs?
Me thinks you need to read to original post ;-)
--
Peter Hunkeler
>//SYSTSIN DD *
>allocate dd(atomic) new delete dsn(TEMP.DUP1)
>delete TEMP.DUP1
>rename TEMP.DUP2 TEMP.DUP1
>free dd(atomic)
>//*
Two cases:
a) If TEMP.DUP1 exists, then the allocate will fail with RC=12.
In this case the delete, and thus the rename will work.
Afaik delete is done at unallocation of the dd. So the free command should
follow the allocate one. But why not just deleteing the dataset without
first allocating it?
Itschak
On Fri, Apr 1, 2011 at 12:59 PM, Hunkeler Peter (KIUP 4) <
peter.hunke...@credit-suisse.com> wrote:
> >//SYSTSIN DD
there is nothing here to loop, me thinks you've mistaken an enqueue/allocation
issue with a loop. ya need a DO WHILE/UNTIL or similar in order to get a loop.
what appears in the systsprnt? and jes logs?
--- On Fri, 4/1/11, Hunkeler Peter (KIUP 4)
wrote:
//SYSTSIN DD *
allocate dd
A recent thread here mentioned "atomic rename" of Classic data sets.
I don't think there is such a thing, but I tried to synthesize it
with:
//ATOMICJOB 505303JOB,'Paul Gilmartin',
// MSGLEVEL=(1,1),REGION=0M
//*
//* Doc: Atomic rename.
//*
//USERCOUTPUT JESDS=ALL,DEFAULT=YES,
// CLASS=R
11 matches
Mail list logo
