venkat kulkarni wrote: >... 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. Somehow you need to find how you are counting the lines already written out and only write those lines not written out. Something like using REXX + SDSF to get your lines (all of them), place them somewhere in a dataset and then using a counter to call IDCAMS from your program to do a REPRO like this one: REPRO INFILE(IN) OUTFILE(AF) SKIP(<lines to skip>) COUNT(<how many?>) Of course you can, from REXX, play with SDSF Print functions to do your printing to another dataset (new, old, mod), DD or yet another SYSOUT. Or using other fancy solutions... All the while your STCs output just grow and grow until JES2 says 'stop' using whatever limits you placed. I have done similar stunts [1] , but not copying certain lines from a live running STC to a dataset. Groete / Greetings Elardus Engelbrecht [1] - In the prehistoric days, I have written a REXX program which copies SYSOUT from a completed batch job to three different datasets, each having x thousand pages by counting how many '1' there were on ASA column. All to split up printing on 3 different printers to speed up printing and chopping down trees faster... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
