Thanks, all, Dave has the right approach, ST reveals the SYSIN input.  The 
ST shows the DSID's I need to see 
DDNAME   StepName ProcStep      DSID
JESJCLIN                      1
JESMSGLG JES2                 2
JESJCL   JES2                 3
JESYSMSG JES2                 4
$INTTEXT JES2                 5
                            101
        I am using a modified JES2DISK REXX from the CBT, and the command 
ADDRESS SDSF "ISFACT ST TOKEN('"TOKEN.IX"') PARM(NP SA)"  is only 
returning the values ISFDDNAME.JX for 1, 2 and 3 which correspond to 
JESMSGLG JESJCL and JESYSMSG.  I can see in SDSF  the SYSIN I need in DSID 
101, but I need to get it using the REXX because I need to read a couple 
thousand of these. 
        Any suggestions? 



From:   "Gibney, Dave" <[email protected]>
To:     [email protected]
Date:   07/12/2012 02:28 PM
Subject:        Re: Show the //SYSIN DD *  lines when using TYPRUN=SCAN?
Sent by:        IBM Mainframe Discussion List <[email protected]>



Using the ST(atus) display instead of I, H, or O generally shows all the 
info you want.

Dave Gibney
Information Technology Services
Washington State University


> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of Dennis Trojak
> Sent: Thursday, July 12, 2012 2:01 PM
> To: [email protected]
> Subject: Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?
> 
> Use "SJ" to see the input data.
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of John Mattson
> Sent: Thursday, July 12, 2012 3:51 PM
> To: [email protected]
> Subject: Show the //SYSIN DD * lines when using TYPRUN=SCAN?
> 
> In SDSF  "INPUT ON" will show you the //SYSIN DD *  lines for a job on 
the
> input or executing queues. But NOT the output queue.
> Is there any way to show what is between the //SYSIN DD * ... and /* 
lines
> when using TYPRUN=SCAN?
> I do not have CA's or other JCL analysis programs, only IBM 'vanilla'
> stuff.
> I know I could look at the input JCL and see it right there, but there 
is a couple
> of thousand jobs involved here, and I would to find a better way.
> 
> 
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
email to
> [email protected] with the message: INFO IBM-MAIN
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to