Agreed - but even for defaults, I've always wanted more granularity than I get with RACF (unless I'm willing to do a whole lot of profiles) and if I'm going to do the heavy lifting in SMS anyway, I never saw any point in using the DFP segment. I can provide the same defaults plus more from within SMS and not involve RACF at all. Plus the fact that I've never been in the position where I do both RACF & SMS, so it aways meant that I had to depend on someone else for the DFP segment.
In my opinion, the allocation decisions belong in SMS - not RACF. Your opinion may differ and I'll defend your right to it to the bitter end. ddk ///////////// 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. ************************************************************************************** This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. ************************************************************************************** ---------------------------------------------------------------------- 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
