e forward.
And...
>And the lesson here is that if you have a job that requires a DISP=OLD on a
>relative GDG in some step, then the only way to avoid the IEF211I is for
>the FIRST use of the same relative GDG to also be DISP=OLD.
I think that's right, that's the only way I can th
23:17:48 +, Schmitt, Michael
wrote:
>JOB. If we were starting new we'd use STEP.
>
>-Original Message-
>From: IBM Mainframe Discussion List On Behalf Of
>Don Leahy
>Sent: Thursday, November 30, 2023 5:12 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: IE
On 12/1/2023 9:26 AM, Scott Ballentine wrote:
(When upgrading, waiting isn't allowed, so we can only upgrade it if we are the
only shared holder of the resource, otherwise the request fails.)
I just learned something here, Scott. I always assumed an upgrade would
wait just the way an ordinary
locks.
And the lesson here is that if you have a job that requires a DISP=OLD on a
relative GDG in some step, then the only way to avoid the IEF211I is for the
FIRST use of the same relative GDG to also be DISP=OLD.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
tion for the second step, etc.
But... there is an ALLOCxx parmlib setting that matters here, called SDSN_WAIT
WAITALLOC. The default is NO, and that tells Allocation that if it can't get
the enqueue, cancel the job and issue IEF211I. If it's set to YES, it will
wait - with an except
JOB. If we were starting new we'd use STEP.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Don
Leahy
Sent: Thursday, November 30, 2023 5:12 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IEF211I - DATA SET RESERVATION UNSUCCESSFUL on relative GDG
[You don't
DISP=SHR.
> > The second step has the same data set, but as exclusive: DD DSN=
> > data.set.name(0),DISP=OLD.
> >
> > Someone was browsing the data set when the job started, so they were
> > holding a shared enqueue.
> >
> > The first step ran, and then the second ste
gt;
> The first step ran, and then the second step failed with the IEF211I -
> DATA SET RESERVATION UNSUCCESSFUL error.
>
>
> My understanding is that JES acquires the enqueues at the highest level
> before starting the job, to prevent deadlocks. IBM says that because it is
> a re
the second step failed with the IEF211I - DATA SET
RESERVATION UNSUCCESSFUL error.
My understanding is that JES acquires the enqueues at the highest level before
starting the job, to prevent deadlocks. IBM says that because it is a relative
GDG, it is unable to acquire the enqueue on the *absol
The ENQ will be on the true name, not the alias name.
--
Tom Marchant
On Thu, 16 Feb 2023 14:50:47 -0600, Jason Cai wrote:
>HI Shmuel
> DSN is an alias name(a loadlib dataset).
> Could you tell me how to find which another user reser
Hi Kolusu
Thanks for your reply !
We will print this smf type today. Jason
Cai
--
For IBM-MAIN subscribe / signoff / archive access ins
HI Shmuel
DSN is an alias name(a loadlib dataset).
Could you tell me how to find which another user reserved this alias?
Thanks a lot! Jason Cai
---
>> Could you tell us which SMF type could diagnose this problem?
Check this
https://www.ibm.com/docs/en/zos/2.4.0?topic=us8r-using-smf-87-subtype-2-records-diagnose-application-problems-related-enq-deq-monitor-usage-enqdeqisgenqreserve-requests
Thanks,
Kolusu
--
M-MAIN@LISTSERV.UA.EDU] on behalf of
Jason Cai [ibmm...@foxmail.com]
Sent: Thursday, February 16, 2023 1:09 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IEF211I
Hi all
Production job gets this message -
IEF211I jobname [procstep] stepname ddname[+ xxx] - DATA SET RESERVATION
UNSUCCESSFUL
Could you t
Hi all
Production job gets this message -
IEF211I jobname [procstep] stepname ddname[+ xxx] - DATA SET RESERVATION
UNSUCCESSFUL
Could you tell us which SMF type could diagnose this problem?
Thanks a lot
Jason Cai
15 matches
Mail list logo
