Rick Fochtman wrote:
But you still need to prevent testers from submitting jobs with a
production USERID. We used a TSO exit to remove USER/PASSWORD parms
from the JOB statement. Got a better idea?
Really?
1. You use a TSO/E user exit to block this? What if they submit a job
with USER= and PASSWORD= to INTRDR using IEBGENER in a batch job?
2. Your testers know a userid/password combination that will give them
production credentials?
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[email protected]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
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
