Thank you for asking the question!
It's time for the IBM folks to chime in on this one.
We are 1.12 going to 2.1 or 2.2.
What is the current default and which zap does what?
Best Regards,
Doug
.
> On Dec 30, 201, at 16:36, Peter Hunkeler wrote:
>
> But a search in IBMLINK for
Hello,
I first came across the CATALOG ENQUEUE problem with ADRDSSU DUMP with GENERIC
INCLUDE MASK in 2001.
In general the use of the CSI catalog search interface does provide a shorter
catalog enqueue elapsed time.
The bypass solution we came up with was to provide a 300 line REXX exec to
In the APAR, I understand that since z/OS 1.11, the default is that ADRDSSU
will use CSI...
You can patch if you want to go back to Generic Catalog Locate
2015-12-30 13:59 GMT+01:00 Peter Hunkeler :
> I'm chasing a problem where some ADRDSSU dump jobs are holding the catalog
>
I'm not a storage guy and cannot comment on the actual effect of using or not
using CSI. But a search in IBMLINK for the APAR cited yields a number of hits,
one of which is info APAR II14616 . I have perused this doc and confess to not
understanding what is being said about what will or will
>But a search in IBMLINK for the APAR cited yields a number of hits, one of
>which is info APAR II14616 .
I was pointed to this and other APARs by a colleague after I posted here. The
net as I understand now is:
o The new, optional function was introduced with an APAR in z/OS V1.9. The
default
I'm chasing a problem where some ADRDSSU dump jobs are holding the catalog
enqueue SYSIGGV2 for an unexcted long time. The jobs specify a couple of
generic dsn specifications in the INCLUDE clause.
I found APAR OA25644 from 2009 which introduces the choice to tell ADRDSSU to
use the Catalog