> The above will "work" but not sure what the ramifications are, however, if > you establish a TSO environment in a long-running "job" such as a started > task.
The most obvious one is that you cannot stop (p) the STC that has a batch TSO environment. You will always have to cancel it, unless everything else running in that batch TSO asid has established a way to listen to operator commands. And be very very careful that you don't invoke *authorized* TSO commands from two tasks in parallel when they also deal with PDSE (as in any library accessed in the address space is a PDSE data set). The result can be as easy as PDSE latch contention to address space hang to having to restart SMSPDSE to ENQ contention on SYSIEFSD Q10 and good night, system. I was told that that can also happen if your installation runs VSAM RLS or any other IBM component that uses latches, but while I have seen the PDSE problems first and second hand, I have never seen it happen for any other component. Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
