So it might be possible that you are seeing data that JES2 has buffered. That is why you can see all of the data on a job in the ST panel even if all that is left in O or H panels is the output from an IEBGENER.
Lizette -----Original Message----- >From: "van der Grijn, Bart (B)" <[email protected]> >Sent: May 2, 2017 2:26 PM >To: [email protected] >Subject: Re: job output into dataset > >It works pretty well except for one (minor) issue. When you do SE against a >DDNAME in SDSF it doesn't work as expected. It seem to display the first of >the outputs with the same DDNAME, independent of which one you select. At >least, that's what it does here (z/OS 2.1). >Bart > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On >Behalf Of Phil Sidler >Sent: Tuesday, May 02, 2017 4:16 PM >To: [email protected] >Subject: Re: job output into dataset > >On Tue, 2 May 2017 12:54:35 -0700, Lizette Koehler <[email protected]> >wrote: > >>I have this in place on several Products I support. The JES Messages all go >>to our output repository. No issues. > >Oh, I see it now, $HASP138 and a new DD with the same name shows up. Cool. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
