On Thu, Oct 26, 2017 at 10:50 AM, Walt Farrell <[email protected]> wrote:
> On Thu, 26 Oct 2017 07:30:07 +0000, Baguley, Nicholas: Absa < > [email protected]> wrote: > > >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. > >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? > > > >NB - this works fine in 99% of cases. We suspect either we are not > building up the ADDUSER command correctly(syntax error) or we have a RACF > issue. > >Unfortunately my next opportunity to make a program change and <SPLAT> > the command to the syslog is a couple of weeks away. > >Maybe the assumption within the the bowels of TSO was that if input is > via PARM then there would be a jcl deck or job output to inspect. > > Whether the command comes in via the PARM on the ATTACH, or via SYSTSIN, > it should be echoed on SYSTSPRT as far as I remember. > Apparently not. I just tried on z/OS 1.12. The JCL looks like: //STEP0 EXEC PGM=IKJEFT1B,PARM='LU (3-5+' //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * /* The output in SYSTSPRT is simply: IKJ56702I INVALID USERID, 3-5+ -- I just child proofed my house. But the kids still manage to get in. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
