Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-25 Thread Edward Jaffe
On 7/13/2012 5:47 AM, Shmuel Metz (Seymour J.) wrote: In <6700504004248585.wa.paulgboulderaim@listserv.ua.edu>, on 07/12/2012 at 10:41 PM, Paul Gilmartin said: TYPRUN=SCAN's "checking" is a bad joke. IIRC, it fails to report errors as fundamental as DSNAME >44 characters. Is that tru

Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-25 Thread Edward Jaffe
On 7/12/2012 3:57 PM, Paul Gilmartin wrote: On Thu, 12 Jul 2012 21:27:37 +, Gibney, Dave wrote: Using the ST(atus) display instead of I, H, or O generally shows all the info you want. However, IIRC, it does not show SYSOUT dynamically allocated from a z/OS UNIX (USS) session. Something

Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-13 Thread John Mattson
a is there. From: Paul Gilmartin To: john_matt...@ea.epson.com Date: 07/13/2012 08:34 AM Subject: Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN? On Fri, 13 Jul 2012 07:43:45 -0700, John Mattson wrote: >Paul, you are on the right track. I do not care about TYPERUN=SC

Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-13 Thread John Mattson
X LOCAL JESJCL JES2 3 AFITJLM X LOCAL JESYSMSG JES2 4 AFITJLM X LOCAL $INTTEXT JES2 5 AFITJLM A 101 AFITJLM X From: Paul Gilmartin To: IBM-MAIN@LISTSERV.UA.EDU Date: 07/12/2

Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-13 Thread Shmuel Metz (Seymour J.)
In <6700504004248585.wa.paulgboulderaim@listserv.ua.edu>, on 07/12/2012 at 10:41 PM, Paul Gilmartin said: >TYPRUN=SCAN's "checking" is a bad joke. IIRC, it fails to report >errors as fundamental as DSNAME >44 characters. Is that true in JES3 or only in JES2? That particular error should

Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-13 Thread Elardus Engelbrecht
John Mattson wrote: >In SDSF "INPUT ON" will show you the //SYSIN DD * lines for a job on the >input or executing queues. >Is there any way to show what is between the //SYSIN DD * ... and /* lines >when using TYPRUN=SCAN? >I know I could look at the input JCL and see it right there, but the

Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-12 Thread Paul Gilmartin
On Thu, 12 Jul 2012 16:15:50 -0700, Lizette Koehler wrote: >> >>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. > >So I guess I would be curious as to what you are working on? >Are you looking for

Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-12 Thread John Mattson
REXX? From: Lizette Koehler To: IBM-MAIN@LISTSERV.UA.EDU Date: 07/12/2012 04:16 PM Subject: Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN? Sent by:IBM Mainframe Discussion List > >In SDSF "INPUT ON" will show you the //SYSIN DD * lin

Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-12 Thread Lizette Koehler
> >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,

Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-12 Thread Paul Gilmartin
On Thu, 12 Jul 2012 21:27:37 +, Gibney, Dave wrote: >Using the ST(atus) display instead of I, H, or O generally shows all the info >you want. > However, IIRC, it does not show SYSOUT dynamically allocated from a z/OS UNIX (USS) session. Something about such sessions are not jobs, thus not

Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-12 Thread John Mattson
ssage- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Dennis Trojak > Sent: Thursday, July 12, 2012 2:01 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN? > > Use "SJ" to see the in

Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-12 Thread Mitch
, Legacy Modernization Consultant -Original Message- From: John Mattson To: IBM-MAIN Sent: Thu, Jul 12, 2012 1:52 pm 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 nput or executing queue

Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-12 Thread Gibney, Dave
is Trojak > Sent: Thursday, July 12, 2012 2:01 PM > To: IBM-MAIN@LISTSERV.UA.EDU > 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:IB

Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-12 Thread Dennis Trojak
Use "SJ" to see the input data. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John Mattson Sent: Thursday, July 12, 2012 3:51 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Show the //SYSIN DD * lines when using TYPRUN=SCAN

Re: Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-12 Thread McKown, John
; From: IBM Mainframe Discussion List > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John Mattson > Sent: Thursday, July 12, 2012 3:51 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Show the //SYSIN DD * lines when using TYPRUN=SCAN? > > In SDSF "INPUT ON" will sho

Show the //SYSIN DD * lines when using TYPRUN=SCAN?

2012-07-12 Thread John Mattson
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 IB