You are correct about using RACF, though most likely you could not use the RLIST command. I remember going to ACF2 training in 1983. The course discussed the ACF2 equivalent, and, to be honest, I couldn't make heads nor tails of the discussion. At the time I was ignorant of generalized resource security in RACF. Several years ago, in my role as a support tech for a product which utilized the security system, I learned how ACF2 did the equivalent of RACF generalized resource security. In my opinion it was screwed up in 1983, and it hasn't gotten any better.
In any event, I propose you forget about trying to drag this out of ACF2 and go to plan B. There is one thing which is unique about all LOGON procs. This is not proof it is a LOGON proc, but it reduces the number of procedures you need to inspect. Second, in most shops the LOGON procs are isolated into one library. Find out the library, and do an ISPF search in all members of the library for PGM=IKJEFT01. This will give you a list of probable LOGON procs. Armed with this list you should be able to eliminate the non-LOGON procs. The remaining procs are still subject to TSOPROC/proc-name security, of course, but at least you know what to look for.
- These users thanked the author steve-myers for the post:
- Viswanathchandru (Mon Oct 29, 2012 8:59 pm)