On 26 October 2017 at 03:30, Baguley, Nicholas: Absa < [email protected]> wrote:
> Hi List > > We need to echo or trace the TSO commands processed in a batch TSO > process... > We are issuing an ADDUSER command under TSO and it returns a RC=8. > In itself not a "biggie". We run TSO via an ATTACH of IKJEFTnn(1B in this > case) so it is a subtask of an IMS address space. > As Walt points out, I don't believe this is a supported thing to do. Unless you are ATTACHing a new job step task, which raises plenty of other issues. The ADDUSER command is passed to IKJEFT as a PARM on the attach svc/macro > as opposed to SYSTSIN. > > We don't see the command "echoed" to SYSTSPRT as you "normally" do when > using SYSTSIN. > Is anyone aware of a mechanism of switching on tracing or diagnosing PARM= > input to IKJ? > Not directly. But why not invoke a little REXX program from the PARM=, and have that program report back on the results, return codes, and so on of the actual command(s) you issue? You'd need access to this REXX program, but thst'a easily done with a SYSEXEC or SYSPROC DD. > > NB - this works fine in 99% of cases. Which suggests that your TMP is working via your ATTACH. Curious... Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
