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
