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 not happen when setting or not setting patch byte x'54' to x'00' or x'11' or x'FF'. Maybe I should have focused more on literacy in grade school.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile [email protected] [email protected] > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Marc Manuel > Sent: Wednesday, December 30, 2015 10:20 AM > To: [email protected] > Subject: Re: Experience with ADRDSSU patch X'54' to enable usage of Catalog > Search INterface (CSI) > > 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 <[email protected]>: > > > 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 Search Interface (CSI) instead of Generic > > Catalog Locates to search for data set matching the INCLUDE mask. The > > new function is enabled via PATCH area, offset X'54'. > > > > > > Has anyone enabled the CSI interface by patching ADRDSSU? Any > > expecience you're willing to share? > > > > > > > > > > -- > > Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
