In the case of #2, and if you are an E(JES) customer, and you run their standalone VTAM interface, then logging on to TSO with a full spool is not an issue.
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Skip Robinson > Sent: Thursday, December 17, 2015 11:04 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Delete part of spool for active job > > There are two distinct conditions that must be considered. > > 1. A large output needs to be managed but is not causing a spool problem. > 2. An ginormous output--together with benign output--has pushed spool > utilization to 100%. > > In the case of #1, others have suggested ways to preserve at least some of the > output. Basically, assuming that the JCL was not coded to anticipate this > situation, you need to copy some portion of the output to another class or > destination. You could also save output to a data set. All spool management > tools I know of have this capability. Once desired output has been preserved > outside the jumbo job, El Gordo can be purged. > > In the case of #2, your options are limited. If spool shortage cannot be > relieved, you may not even be able to logon to the MAS because even a TSO > address space needs some spool space. I don't believe that you can purge an > individual segment while a job is still writing to it. When spool-full > condition > has hit us, the offending job is usually still running, so that space > recovered by > purging some disposable output is immediately filled up again by the same > job. If this situation occurs, you have little choice but to cancel *and > purge* > the offending job, which unfortunately means losing all the output. > > . > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > jo.skip.robin...@att.net > jo.skip.robin...@gmail.com > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Lizette Koehler > Sent: Thursday, December 17, 2015 06:08 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: Delete part of spool for active job > > So, you may wish to contact your z/OS Sysprog for assistance. They will > probably be able to help. > > So in SDSF you go to the ST display for the job and do a ? next to it. It > will > show you the Jes2 Dataset Numbers. You can then use that for the $TO > commands as needed. > > But talking to your Sysprog would be a good thing. > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM- > m...@listserv.ua.edu] > > On Behalf Of Hilary Hurwitz > > Sent: Thursday, December 17, 2015 6:36 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: Delete part of spool for active job > > > > We have SDSF > > > > I am not familiar with $TO > > > > (I am actually a DBA, not a SYSPROG) > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM- > m...@listserv.ua.edu] > > On Behalf Of Lizette Koehler > > Sent: Thursday, December 17, 2015 15:33 > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: Delete part of spool for active job > > > > There are a couple of options, > > > > If the JCL has coded on the SYSOUT FREE=CLOSE,SPIN=UNALLOC then you > > can purge just that portion of the job without impacting anything else. > > > > You can use SDSF (if you have that) and change the one DD statement > > that has > the > > huge spool output to a different class (There are JES2 $TO commands > > also) and > then > > route the output from the rest of the job to the destinations they > > need to > go. > Once > > all the good parts have been handled, you can then purge the offending > > piece > of > > output > > > > You can use the JES2 XMIT/RECEIVE process to offload the whole job or > > any part > to > > a tape/dasd dataset You can use SDSF (if you have it) to print (XDC > > commands) > to a > > dataset to save the good parts and then purge the offending section. > > > > There may be some other options I am missing. IMO - the > > FREE=CLOSE,SPIN=UNALLOC is a good standard for SYSOUT datasets. > > > > So it will depend on how much effort that is needed on doing this. To > > save > all of the > > job with the exception of this one SYSOUT will require a little effort. > > > > Do you use SDSF? Or have you researched the $TO commands? > > > > Lizette > > > > > > > -----Original Message----- > > > From: IBM Mainframe Discussion List > > > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hilary Hurwitz > > > Sent: Thursday, December 17, 2015 6:13 AM > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > Subject: Delete part of spool for active job > > > > > > If a job is running and putting out many lines of spool - maybe > > > there was an > > over > > > active programmer that printed all details of every customer in a > > > multimillion > > line file > > > - is there a way of deleting the lines that have been written to the > spool ? > > > > > > Or do I have to purge the job ? > > > > > > Hilary Hurwitz > > > NIOI > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
