Hi John/Gil, if you would like to open a request for enhancement (RFE) to
that effect, you can do that here https://www.ibm.com/developerworks/rfe/
-Joe
Joe Gentile
z/OS GRS Lead
(845)435-2184 (T/L 295-2184)
jwgen...@us.ibm.com
-
On Mon, 28 Sep 2015 16:04:55 -0500, John McKown wrote:
>>
>> >I seem to recall a recent enhancement to z/FTP dynamic allocation that
>> reports contention and retries some number of times at user-defined
>> intervals. TSO ALLOC and IDCAMS might take that as an example for future
>> development.
>>
On Mon, Sep 28, 2015 at 3:54 PM, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Mon, 28 Sep 2015 18:35:07 +, Dave Barry wrote:
>
> >I seem to recall a recent enhancement to z/FTP dynamic allocation that
> reports contention and retries some number of times at user
On Mon, 28 Sep 2015 18:35:07 +, Dave Barry wrote:
>I seem to recall a recent enhancement to z/FTP dynamic allocation that reports
>contention and retries some number of times at user-defined intervals. TSO
>ALLOC and IDCAMS might take that as an example for future development.
>
So instead
[mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Wednesday, September 23, 2015 3:58 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset enqueue, how to find the culprit.
On 2015-09-23 11:54, Dave Barry wrote:
> The problem is that the SVC99 dynamic allocation is unconditional.
ember 2015 1:44 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Dataset enqueue, how to find the culprit.
>
> On Thu, 24 Sep 2015 14:33:03 +, Pommier, Rex wrote:
> >
> >Commands for viewing ENQs and ENQ contention:
> >
> >o Enq
> >Show existing ENQs on the
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Friday, 25 September 2015 1:44 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset enqueue, how to find the culprit.
On Thu, 24 Sep 2015 14:33:03 +, Pommier, Rex wrote:
>
>Commands for viewing ENQs and ENQ cont
On Thu, 24 Sep 2015 14:33:03 +, Pommier, Rex wrote:
>
>Commands for viewing ENQs and ENQ contention:
>
>o Enq
>Show
Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Thursday, September 24, 2015 8:18 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset enqueue, how to find the culprit.
On 2015-09-18, at 10:47, Steely, Mark wrote:
> I created a REXX called WHI (w
On 2015-09-18, at 10:47, Steely, Mark wrote:
> I created a REXX called WHI (who has it). Here is the code:
>
> PROC 1 DSN
> /* CLRSCRN */
> ISRDDN E &DSN
>
> Then in 3.4 enter WHI and it will display any enqueue.
>
And it's better than the RENAME approach in that it identifies
Good point. Some SVC99's specify not to wait for the ENQ (S99CNENQ I
think). GRS considers this "waitless" contention. GRS also issues ENF 51
signals for contention (including waitless contention). RMF uses these
signals to report on contention, so you may be able to track waitless
contention t
On 2015-09-23 11:54, Dave Barry wrote:
> The problem is that the SVC99 dynamic allocation is unconditional. If the
> resource is already owned, the subsequent allocation request fails. ...
>
Not if the requesting program is entitled to use S99WTDSN.
> Static allocation is an option because all
AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Dataset enqueue, how to find the culprit.
>
> Hi, you could also run ISGECJES from SAMPLIB (z/OS 2.1). It is a simple
> dataset enqueue contention monitor written in assembler.
> It won't go back in time. It will alert you to
Of Joseph W Gentile
Sent: Tuesday, September 22, 2015 11:04 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset enqueue, how to find the culprit.
Hi, you could also run ISGECJES from SAMPLIB (z/OS 2.1). It is a simple dataset
enqueue contention monitor written in assembler.
It won't go ba
Hi, you could also run ISGECJES from SAMPLIB (z/OS 2.1). It is a simple
dataset enqueue contention monitor written in assembler.
It won't go back in time. It will alert you to dataset contention going
forward. We wrote an article about it in z/OS Hot Topics Issue 27, page
54. http://publibfp.dhe
Very nice, Mark Steely. Consider WHI stolen!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
ENQ)
--- acbi...@gmail.com wrote:
From: Toni Cecil
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset enqueue, how to find the culprit.
Date: Fri, 18 Sep 2015 21:46:12 +0100
Hello everyone,
I wnat to know how to debug this situation after it occurred, in this case,
the next day.
rom: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Toni Cecil
> Sent: Friday, September 18, 2015 12:21 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Dataset enqueue, how to find the culprit.
>
> Hello,
> yesterday I got the following dsn enqueu
mpany
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Ted MacNEIL
Sent: Friday, September 18, 2015 1:56 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset enqueue, how to find the culprit.
There is NO SUCH THINGS as a culprit!
They
DETAIL)
--- stars...@mindspring.com wrote:
From: Lizette Koehler
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset enqueue, how to find the culprit.
Date: Fri, 18 Sep 2015 11:16:35 -0700
So, it will depend on how often the TSO message for enqueue is produced. If it
is not frequent, you may have to set sl
-l_listserver/
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Toni Cecil
Sent: Friday, September 18, 2015 11:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Dataset enqueue, how to find the culprit.
Hello,
yesterday I got the following dsn
BM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Lizette Koehler
Sent: Friday, September 18, 2015 11:17 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset enqueue, how to find the culprit.
So, it will depend on how often the TSO message for enqueue is produced. If it
is no
===> Scroll
===> CSR
14 ENQ(DETAIL)
--- stars...@mindspring.com wrote:
From: Lizette Koehler
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset enqueue, how to find the culprit.
Date:
might provide better diags or alternatives.
Lizette
>-Original Message-
>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
>Behalf Of Toni Cecil
>Sent: Friday, September 18, 2015 12:21 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Dataset enqueu
-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Steely, Mark
Sent: Friday, September 18, 2015 9:47 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset enqueue, how to find the culprit.
I created a REXX called WHI (who has it). Here is the code:
PRO
usma, David
Sent: Friday, September 18, 2015 11:25 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset enqueue, how to find the culprit.
Sorry, you have to hit PF1 twice to get the display I mentioned.
_
Dave Jousma
Assistant
The old RMF TSO command RMFMON suboption SENQR will also tell you
this information.
--- stars...@mindspring.com wrote:
From: Lizette Koehler
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset enqueue, how to find the culprit.
Date: Fri, 18 Sep 2015 09:24:56 -0700
If
UA.EDU] On
> Behalf Of Jousma, David
> Sent: Friday, September 18, 2015 9:25 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Dataset enqueue, how to find the culprit.
>
> Sorry, you have to hit PF1 twice to get
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Toni Cecil
> Sent: Friday, September 18, 2015 9:21 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Dataset enqueue, how to find the culprit.
>
> Hello,
> ye
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jousma, David
Sent: Friday, September 18, 2015 12:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset enqueue, how to find the culprit.
One of the quickest ways, is to go to ISPF option
i Cecil
Sent: Friday, September 18, 2015 12:21 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Dataset enqueue, how to find the culprit.
Hello,
yesterday I got the following dsn enqueue:
IKJ56225I DATA SET TLF.ZPT.JCL.CNTL ALREADY IN USE, TRY LATER+ IKJ56225I DATA
SET IS ALLOCATED TO ANOTHER JOB OR USER S
Hello,
yesterday I got the following dsn enqueue:
IKJ56225I DATA SET TLF.ZPT.JCL.CNTL ALREADY IN USE, TRY LATER+
IKJ56225I DATA SET IS ALLOCATED TO ANOTHER JOB OR USER
SDAA004I - RETURN=(DD),PERM=YES DSN=TLF.ZPT.JCL.CNTL(ZZZTXXXB),
DISP=SHR
SDAB005I - ERR=0210, INFO=, REQUESTED DATA SET NOT AVA
32 matches
Mail list logo
