>I already wrote the idea is perfectly OK and (maybe) it's NOT violated by the >profiles. I repeat the possible explanation: separation of rules.
Juist because you've repeated your statement, it doesn't make it valid. Separate files, not commands! >Several rules could need same access to SMPE datasets, so if you want to make them separate, you need another check, access to resources is not enough here. I disagree. Give me an example; a valid one. Anything else is just rectal smoke! And, repeating what you've said without some evidence is just more smoke. Why is command protection better than resource/file protection. Separate the SYSPROG roles by files/data rather than command. For example, everbody can invoke ISPF browse, but not all can read all files. This may sound simplistic, or apples & oranges, but it illustrates my point. - Too busy driving to stop for gas! ---------------------------------------------------------------------- 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
