First, You cannot "cut" messages from the task. You can only spin it.
I am sure there are consultants you can hire to help you write this code. This is a friendly list, but you are asking for some effort to be done. You can have JES spin the job at the number of lines you want, it does not have to be on TIME based parameter. Then setup an EXTERNAL Writer to extract the data. Spin each task at a different time and then run the writer. That way you should be able to keep things separated. After the External writer runs, then mod on to a dataset of your choice. If you are just spinning specific DD statements in the TASK, you may have an easier process. Or you could create a GDG and at the end of the day, use IEBGENER to copy all the GDGs to one dataset. The best way to get better in coding REXX is to just code rexx. The more you do the better you get. There are already some REXX code on cbttape.org that could assist you . Or there might be other tools already created you can use for your process. Do an internet search for JES2DISK. This is a good piece of code that will write from JES2 to a file or a Unix File using SDSF REXX. This is the process I use to pull data from JES Spool and write to a dataset. It can be adapted to use filters like DD names or other JES2 Elements of a job. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of venkat kulkarni > Sent: Wednesday, May 03, 2017 4:14 AM > To: [email protected] > Subject: Re: job output into dataset > > Thanks for all suggestion. Currently, we don’t have any third party product > for doing this task. So, my idea is to create rexx program, which keep > checking ( once in day) particular address spaces like IMS, CICS, or any other > which are continuously running in system and find that if the lines are exceed > in the job with the limit we set in rexx program then this program should cut > those messages from that address space and save it in one separate dataset > > we specified in rexx program and next time when this program find more message > in the address space, it should again cut messages from address space and > append in the dataset we used earlier. > > > > So, for difference address space( CICS, IMS, DB2 etc) , I would like to use > different dataset and keep appending messages on regular interval . > > > > As I am not expert in rexx, can anybody help me doing this task. > > > > Regards > > On 03-May-2017 12:40 AM, "Lizette Koehler" <[email protected]> wrote: > > > 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
