Have you reviewed the RNL requirements for GRS and CATALOG
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieag400/catgrs.htm
Catalogs are VSAM data sets, but VSAM recognizes, catalogs, and manages access
to them in a special way. Converting catalog reserves can reduce contention
caused by catalog activity. Depending on your system configuration, you need to
do the following to convert catalog reserves:
To avoid a data integrity exposure, verify that all systems using a catalog
are part of the complex.
Place a generic entry for SYSIGGV2 in the RESERVE conversion RNL.
Lizette
-----Original Message-----
>From: Allan Staller <[email protected]>
>Sent: Apr 5, 2017 10:33 AM
>To: [email protected]
>Subject: Re: RLS for catalogs
>
>GRS ring or GRS star?
>
>-----Original Message-----
>From: IBM Mainframe Discussion List [mailto:[email protected]] On
>Behalf Of Joe Owens
>Sent: Wednesday, April 5, 2017 11:44 AM
>To: [email protected]
>Subject: RLS for catalogs
>
>We are experiencing general issues with catalog contention, seeing a lot of
>SYSIGGV2 enqueue waits. We have shared DASD between multiple LPARS in a sysplex
>
>I was wondering if anyone had experience of using RLS for catalogs, as
>introduced with with Z/OS 2.1?
>
>In particular, anyone using this with MIM. MIM has to be initialised before
>RLS can start (several references to this in APARS). We use RLS with endevor
>VSAM datasets, and this is not an issue, but as catalog access is so basic to
>the system, I am thinking we might have to initialise MIM before JES (and have
>it's parmlib in the master catalog), to avoid a chicken and egg situation.
>
>Just wondering if anyone else has considered this.
>
>Regards,
>
>Joe Owens
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
