On Wed, 20 Feb 2019 15:51:23 +0200, Steff Gladstone <steff.gladst...@gmail.com> wrote:
>Do I understand correctly that TSOEXEC CALL creates a new subtask >environment which is "insulated" from the goings-on in the mother task? Yes. The parallel environment established by TSO/E via TSOEXEC would be clean, even if the original environment is dirty. You still need to have PROGRAM ** setup as documented, though, or that parallel environment might become dirty before the program you're CALLing gets control. >Would specifying TASKLIB further ensure that only those modules >loaded/linked/attached from the TASKLIB library need be RACF-authorized? I'm not sure where you'd specify that TASKLIB. Of course, "CALL dsn(member)" sets up dsn as a TASKLIB for the task that member runs in, but other than that I'd need more details to answer your question. The difficulty of using TSOEXEC, though, is that the program you call can't interact with ISPF at all, and that is critical for some programs. For others, it won't matter. Also, setup will be easier if you enable Enhanced Program Control, as well as more secure, especially when using programming languages where functions are provided by dynamically loaded subroutines. Again, details in the RACF Security Administrators Guide. -- Walt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
