Tony,
Thanks for the input, I appreciate it. But Unix isn't within the scope of what we are currently doing. As far as IKJEFT01 we work fine, been that was since it was written in 2002. This is a legacy exit that I support and have been changing. Most of our changes are coming from either TSO command line , Option #6, ISPF panels, or Batch via IKJEFT01. Most of our customers wont touch Unix, don't ask me why, because I don't know. I work all the platforms , I have too.. I just wanted to make sure I was trying to cover all my bases, obviously Unix is one that's a wildcard and will go on the list. Regards, Scott Ford www.identityforge.com From: Tony Harminc Sent: Wednesday, February 19, 2014 9:53 AM To: IBM Mainframe Assembler List On 19 February 2014 13:58, Scott Ford <[email protected]> wrote: > My question was what was the best way to determine where the command > originated, if it was from > batch or TSO/ISPF...I was in the code looking at a REMOVE/CONNECT issue we > had and had fixed it ..so in my review I started to think about a new > technique for above. > > Now we are doing: > > CVT->ASCB->TSB this is working fine ... But this is giving you an answer to a question that isn't quite what you asked at first. You asked "I have a need to determine inside an exit where a RACF command was batch issued or TSO issued", but your answer is to: "is this a classic TSO session with a terminal connected?" There are several other scenarios, and you need to formulate the right question to get a useful answer. For example, there are batch TSO sessions (i.e.EXEC PGM=IKJEFT01), there are TSO commands run using the IKJTSOEV service (which could be in a batch job, an STC, or a UNIX session - in fact anywhere *except* a classic TSO session), and there are TSO commands issued from the UNIX/REXX Address TSO environment. And probably more that I haven't thought about. Tony H.
