I checked the DFHSM proclib. There is no CDSSHR=RLS.
Since CDSSHR is not speicfied, RLS is not being used. Thanks for solving the
mystery
A massive thanks.
On Tuesday, November 5, 2019, 10:58:37 a.m. GMT-5, Glenn Wilcock
<[email protected]> wrote:
HSM's usage of RLS Access for the control data sets is driven by the PROCLIB
value for CDSSHR. CDSSHR=RLS indicates that HSM should access the CDSes in RLS
mode. If CDSSHR is not specified, or has any other value, then you are not
using RLS for HSM.
DCOLLECT behaves this way because it is not running under the HSM address
space, so it is how we determine the proper way to open the control data sets
concurrently with HSM.
BTW - Using RLS to access the HSM control data sets is my second rated best
practice for HSM. If you run concurrent HSM activity across multiple LPARs, it
can significantly improve elapsed times. My highest rated best practice for
HSM is to use zEDC. zEDC does wonders for HSM elapsed times and storage
reduction. If migrating to ML1, it also reduces cpu consumption.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
