Regarding AUTHPGM itself, I think of it this way (pretty much the way Steve Smith described it):
AUTHPGM identifies to TSO/E a program that needs to be run on the "authorized side" of the TMP. For such a program, setup must be done very carefully. While there is a program running on the "authorized side", the system makes sure, as it must do to avoid integrity problems, that nothing at all is running on the "unauthorized side". Managing the required non-dispatchability of the unauthorized side is key. If you have something TSO/E-wise that does require authorization but is not identified as such, it will be run on the unauthorized side and when it does whatever it does that requires authorization, it will be seen as not having suitable permission. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
