On 5/7/2013 5:02 AM, Lizette Koehler wrote:
The only way I can think of restricting is an exit in JES2. Or if this is a TSO User you may wish to look at IKJEFT10 exit.
You'd be surprised how many "secure" installations permit a TSO user to allocate an internal reader and write a job to it.
I once installed a package at a hush-hush installation (program needed configuration data, then submitted assembly/link jobs) and was told it wouldn't work because they prohibited TSO job submission. They were surprised when my jobs started running. Next time I talked to them, they had modified JES2 so that internal reader allocation went to class B (punch) instead!
Gerhard Postpischil Bradford, Vermont ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
