In a recent note, Walt Farrell said: > Date: Tue, 19 Sep 2006 14:00:51 -0400 > > ... Generally it is more a question, I think, > of whether the program is doing something that you would want run under > TSO, given the dispatching priority of TSO users, and some environmental > characteristics (how long the user will be waiting while it runs, for > example) that determines whether you allow the programs to run under > TSO/E or not. > Alas, this misses the mark considerably in that it fails to distinguish between interactive TSO sessions and use of the TMP in batch. AUTHPGM NAMES is the same for both, isn't it?
Perhaps for this purpose AUTHPGM should govern only calling programs from interactive sessions, and batch TMP should be free to invoke any authorized program, listed or not. There are similar concerns with dynamic allocation of tape drives. The administrators' reasonable desire not to allow drives to be monopolized during programmers' think time should not be addressed by the crude expedient of prohibiting (or allowing) all dynamic allocation and mounting of tapes. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
