The RACF DFP segment only provides default values for the three SMS classes. The ACS routines still make the final decision in SMS and can honor or ignore the defaults as they see fit.
-----Original Message----- From: Darth Keller [mailto:snip] Sent: Thursday, May 01, 2008 8:20 AM To: [email protected] Subject: Re: SMS PUZZLE In the case of a smaller shop with simple needs, DFP segments might be the way to go. One of the companies we brought in & merged into our environment used them. But I've just finished ripping all that code out as for our needs, it proved to be too simple and didn't provide us with the granularity we needed. We use DFP segments to provide TSO user defaults, but everything else gets decided in the SMS code where I have the control. One thing to keep in mind is that by giving control over to the DFP segment, you're generally depending on a RACF adminstrator to provide your values. While they're great at understanding RACF, I think it's a bit unfair to expect them to understand your storage environment and applications' needs. Also getting changes made when needed can prove to be a challenge too as their priorities don't necessarily match yours. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
