One other complex process to leave it on SPOOL as well as archive it is to do the following
S STC1 //STC1 ... //SYSOUT dd DISP=(,CATLG),DSN=GDG(+1),....more jcl //* //ENDSTP EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT= //SYSUT1 DD DISP=OLD,DSN=GDG(+1) //SYSUT2 DD SYSOUT=* This process writes the SYSOUT to a permanent GDG (No viewing while GDG is up) When it comes down the IEBGENER step will then write the SYSOUT to SPOOL and keep the GDG for archive. But if you want to view the SYSOUT while the SYSOUT is up and then copy it to DASD/TAPE for ARCHIVE then the JES2DISK as the last step would work. I use JES2DISK all the time. Takes up all or part of the output on Spool. I even added a logging function to it so I have jobname/jobnum/date/time/CC in a nice little SEQ file to match my files I just created. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of saul anthony babonas > Sent: Tuesday, August 16, 2016 11:58 AM > To: [email protected] > Subject: Re: Capturing STC SYSOUT when the STC is shut down > > The requirement to keep and archive SYSOUT can be done as follows............ > > //SYSOUT DD > DSN=YOUR.SYSPRINT.GDG.DATASET(+1),DISP=(NEW,CATLG,DELETE),etc,etc > > The additional requirement to view while the STC is up and running..... > ......sorry but retirement has impacted by memory of gadgetry but there's a > simple method to write SYSOUT to 2 DD cards, the 2nd of which will be SDSF > viewable. Someone younger I hope can chime in. > > > > > On 8/16/2016 10:09 AM, Nims,Alva John (Al) wrote: > > I think there are at least two options: > > 1. Since you have already mentioned SDSF, yes I believe you can use SDSF to > copy the output and write it to a GDG, I have done it in the past, but > unfortunately all that code of mine is gone and I no longer have access to > SDSF to help you further. > > 2. This is also an option in that is readily available as part of z/OS and > does not require installing any additional software; it does use a UNIQUE > output class (it helps, but is not completely required) that you can start a > JES2 external writer to read the SYSOUT and write to a GDG, you might have to > submit a JOB or start a "Started Task" before leaving the original JOB to do > that, because the SYSOUT must be closed and freed before the external writer > can read the output. > > > > There is a 3rd option, but ONLY IF you have $AVERS (Software Engineering of > America (SEA)) I think it has options to do this where you do not need a > unique output class and can be done by JOBName, I think, so don't quote me on > that and if you do not already have $AVERS installed, it is a moot point, > unless you are ready to spend money. > > > > Al Nims > > Systems Admin/Programmer 3 > > UFIT > > University of Florida > > (352) 273-1298 > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Jon Bathmaker > > Sent: Tuesday, August 16, 2016 10:38 AM > > To: [email protected] > > Subject: Capturing STC SYSOUT when the STC is shut down > > > > Hi, > > We are running NVAS and the SYSPRINT file gets directed to SYSOUT=* which is > fine as we can browse it if we need to. > > > > For some reason (Audit request?) I am being asked to vacuum up the SYSOUT > file and put it into a GDG when the task is recycled, while still leaving it > as SYSOUT when the STC is active. . Based on a message I received, a disp of > PASS and SYSOUT are incompatible. I am now considering using SDSF in batch > so solve this problem (thanks to Lorne Heffer). > > > > Anyone have any ideas? Using a commercial Program Product is a non-starter > as, like everyone else the client is only interested in lower cost. Thanks. > > > > Regards, > > Jon Bathmaker > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
