Tony B. wrote: >Brevity on my part has led to lack of clarity. My interpretation of "protecting ADRDSSU" was to build a profile in the program class, then selectively permit it to some trusted users. This approach is nonsense.
Agreed. Anoter example is the program AMAZAP. It is better to use RACF (or other ESM) to protect the OBJECTS (datasets, volumes, etc) not the tools used. If you plug ADRDSSU, someone will use FTP, IEBCOPY, whatever, to bypass the PROGRAM class. That subject is an old horse beaten (again) to death... ;-D >That which is illustrated below I am interpreting as "protecting the various different functions of ADRDSSU" by building profiles in RACF's facility class, then selectively permitting them to trusted users. This approach has merit. Thanks. >I promise to elaborate in the future. Do not feel bad, it is Ok with me. I value and appreciate your posts. Please keep them coming. ;-D PS: After all those replies, I have nothing to add to the original topic of FTP and loadlibs... Sorry for this topic drift. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- 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
