At 19:04 -0500 on 04/22/2011, Patrick Roehl wrote about Re: Mixing
Auth and Non-Auth Modules:
Would this work?
Program A (non-authorized) does an ATTACHX with DCB which points to an
authorized library to start program B in a new TCB. Program B would be
authorized and service RACROUTE requests from program A via common
storage and a WAIT/POST protocol.
Program A would then be free to call all the "regular" modules from STEPLIB,
and program B would load from "AUTHLIB" DD which contains the authorized
library. At this point it's an assumption on my part that this scheme would
allow authorized and non-authorized programs to comingle.
Thanks for all comments, suggested variations, and pitfalls of this idea.
I think you have it backwards. The job step task needs to be
Authorized and Attach the non-authorized subtask. Your scheme would
imply a security breach since it would allow a non-authorized task to
attach an authorized task. The way I proposed is the way TSO allows
both authorized and non-authorized tasks to run in the same session.
----------------------------------------------------------------------
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
