First, Never panic if jes2 reaches 100% TGS. It can recover Second, hold all INITS, stop TSO LOGONs Third- Breath
Review the $POJ command. Very powerful and has lots and lots of options. If you have a queue that you would purge daily, Say OUTPUT CLASS X is output that is not needed longer than a day or two. Then in an emergency you can issue a $POJ1-*,CLASS=X to purge all output in class X $POJ1-*,AGE>3 to purge jobs older than 3 days $POJ1-*,JOBMASK=XX* for a job on the output queue you know as having a large number of outputs. Next, review the OFFLOAD function in JES2. If you have Tape, which I like for this, you just start an offloader for output and just write it all to tape. You can restore it to jes2 later and the SYSLOG will have a listing of all jobs it offloaded. Again this has a lot of functionality that requires practice If you have Sacrifice output classes in JES2, then you just $POJ them. JES2 is still functional when 100% TGS. It just cannot run work or accept jobs. Logons are jobs entering the system You might also have a TSO session up in Operations full time (never logs off) just for such situations. You might also look at the spool volumes $DSPOOL Look to see the % usage. If they are high (80% or more on average) then you might consider adding a new volume Checkout the JES2 Redbook http://www.redbooks.ibm.com/abstracts/redp3940.html Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of baby eklavya Sent: Wednesday, September 25, 2013 5:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Issue with JES SPOOL Lizette , Thank you for quick response as always ! I"ll look at the settings which you suggested and setup automation alerts . But , am also interested to know if there is a way i could avoid a cold start of JES2 when the TGS utilization reaches 100 % . In our case , we did not have spare spool volumes to add space dynamically . As we had to do a Cold start of JES2 being the last option , am just trying to understand if i had a different option other than that . On Thu, Sep 26, 2013 at 5:18 AM, Lizette Koehler <stars...@mindspring.com>wrote: > One of my favorite things to look at for this situation is > > 1) Put the warning message lower for $HASP050 > 2) Look at your settings for ESTPAGE, ESTLINE, ESTBYTE > 3) Put some automation in place (emails or alerts) > a) Automation of the $P command to purge data based on AGE > 4) Use SDSF to see if Purging is being done > 5) In SDSF turn off any filtering, Use the ST command and SORT on QUEUE. > Then find MASCOMM (MASC works) and scroll back one page. > If there are jobs that have HOLD just above MASCOMM then you > have users issuing a HOLD against running jobs. They never purge > until they are released > > Just a few thoughts. You should not need exits. JES2 has lots of > controlling functions. You can have JES2 abend a job producing too > much output with a S722. Be careful you do not hurt production. > > > Lizette > > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of baby eklavya > Sent: Wednesday, September 25, 2013 4:11 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Issue with JES SPOOL > > Hello everyone , > > > Is there a different way to come out of the below situation other than > a cold start of JES2 > > *$HASP050 JES2 RESOURCE SHORTAGE OF TGS - 100 % UTILIZATION REACHED * > > Recently , we ended up in a situation where nobody could logon to the > system , and when tried to purge the jobs from console ,it didnt work > either . We are currently tuning the JESPARMS and setting up exits to > avoid such issues in future . But i was wondering if there was > anything else we could have done when the issue really happened . > > > Unfortunately , we didnt have spare spool volumes to start and i felt > that > JES2 was not accepting any commands at that point of time . Any thoughts ?? > > Thanks in Advance , > Baby > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
