Hi,
CATDSNS might have a negative impact on RACF and system performance because 
RACF must verify that data sets are cataloged before it allows them to be 
opened.

When CATDSNS(FAILURES) is active, RACF blocks access to a data set unless one 
of these conditions is met:    
   
   - The data set is cataloged in the master catalog.
   
   - The data set is newly created in the current job or is a system temporary 
data set.
   
   - The data set resides on tape and the request is for UPDATE access.
   
   - The data set has a discrete profile.
   
   - The user possesses the SPECIAL attribute or has access to the ICHUNCAT 
facility class resource. 













iyi çalışmalar,saygılar / Regards

____________________________________

Kayhan TANRIVERİR
Senior Systems Programmer &Consultant

VBT Yazılım A.Ş

www.vbt.com.tr  














 

    2 Eylül 2026 Çarşamba 16:53:57 GMT+3 tarihinde, Ituriel do Neto 
<[email protected]>şunu yazdı:  
 
 If the datasets are SMS, they must be cataloged.


Best Regards

Ituriel do Nascimento Neto
z/OS System Programmer






Em quarta-feira, 2 de setembro de 2026 às 10:16:48 BRT, [email protected] 
<[email protected]> escreveu: 





Hi!

We have always run our PRODUCTION Lpars with the RACF SETROPTS CATDSNS option 
active in FAILURES mode. This way, access to uncataloged datasets is basically 
disallowed (unless some specific conditions are met, like access to a proper 
ICHUNCAT resource in FACILITY class).
On the other hand, this option implies a catalog check for every dataset that 
is opened (plus a RACF check for the appropiate ICHUNCAT resource, in case the 
dataset is indeed uncataloged).
In your experience, does CATDSNS have a NOTICEABLE performanceimpact?
>From security viewpoint (my viewpoint), I prefer to have CATDSNS, to prevent 
>normal users from playing around with uncataloged datasets. But if switching 
>to NOCATDSNS represents a real performance gain, we are open to evaluate the 
>change.
Thanks in advance for your help,




Juan Mautalen


----------------------------------------------------------------------
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
  

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to