Thank you very much everyone for the replies .. They are indeed very useful and informative !
Thanks a lot ! On Thu, Sep 26, 2013 at 4:38 PM, nitz-...@gmx.net <nitz-...@gmx.net> wrote: > > But in no case did we have to cold start. > I second that. We have a 100% JES2 shortage of one kind or another about > every 3 months. So far I managed to get by without a cold start. > > The problem as I see it is reducing the shortage to the point that a logon > will be possible again. A number of display and purge commands have been > named already, but in my experience the steps are: > > 1. Determine who holds a lot of the resource. In many cases, it is an > active address space, and you want to first get it to stop further writing > to spool or to write its buffers to the spool just cleared, throwing you > back into a 100% shortage. It may be impossible to cancel such an address > space. I know that I used the force command to stop it from further filling > up spool. > > 2. Once you're sure no active address spaces are still writing like crazy, > determine who holds a lot of spool. And then use the commands named before > from the console, without resorting to SDSF. > > 3. Once you manage to get spool usage down to the point that you get into > TSO/SDSF again, you have better chances in saving output and clearing it. > > 4. Finally, prepare for the next shortage: > a) Set alerts for the HASP050 message designed to notify you early enough > so you can still login. > b) Practise purging of output via JES commands without the convenient use > of SDSF. I consider that the biggest challenge, but I never was an operator. > c) Prepare a spare spool data set to add if necessary. My advise is to > keep such a volume in reserve, but never to add it automatically. Be aware > that there are cases when you cannot add a spool volume because it would > require the resource you're short of (I forgot which that was -JOEs?) Once > you're out of your spool shortage after adding the spare, don't forget to > remove the spare, so you have it again for the next shortage. > d) Set up a procedure for spool offload and practise unloading your spool. > Presumably also practise reloading it. > > Barbara > > ---------------------------------------------------------------------- > 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
