On Sun, 7 Apr 2013 19:55:02 -0700 Jon Perryman <[email protected]> wrote:
:>Some TSO pointers are in the TCB (mapped by IKJTCB - prefix is for TSO instead :>of another component -IHA, IEA or ???). TSO also changes TCB authorization that :>violates standard APF authorization In what way? A command runs at the top level and when the parallel TMP runs it stops the standard session. :> I suspect that violating the jobstep :>requirements would create an exposure which is not corrected by :>PARMLIB(IKJTSOxx). The TMP does leave bits and pieces laying around. It has been a while since I looked at it but there was a bit of cleaning up required after the TMP ended if you wished to restart it. :>----- Original Message ---- :>From: Walt Farrell <[email protected]> :> :>On Sun, 7 Apr 2013 15:58:35 -0400, Phil <[email protected]> wrote: :>>Clearly this is another case of RTFM. I missed JSTCB=YES on my ATTACH. :>>The manual does say 'one and only' jobstep task, but :> :>But you _should_ not do that with the TMP, as it wants to be the only :>user-specified jobstep TCB. That is, in my interpretation, it wants to be :>running in the TCB attached by the initiator. So if you have another program :>invoking the TMP it _should_ LINK or XCTL to it, so it's in the "proper" TCB. :> :>I have no idea whether it really makes a difference or not. :> :>Walt -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies.
