Automated Testing

Automated Testing

Automated Testing

Build an automated testing process to enable continuous integration of your hybrid cloud applications including z/OS

 View Only

  • 1.  *$HASP050 JES2 RESOURCE SHORTAGE OF TGS - 100% UTILIZATION REACHED

    Posted Mon May 09, 2016 05:50 AM

    Hi,

    We have an RDT Mainframe server which we IPLed because the SPOOL became full. 

    Our RDT is hosted on a linux machine and we have tried restarting the linux machine as well with no success. Please refer to the attached snapshots of the log. It would be really helpful if anybody can provide some pointers on what might be going wrong. 

     

    We do not have experience on the administration activities, Please suggest how to resolve. Thanks in advance.

     

     

     

    Tauro81


  • 2.  Re: *$HASP050 JES2 RESOURCE SHORTAGE OF TGS - 100% UTILIZATION REACHED

    Posted Wed May 11, 2016 05:44 PM

    Hi Vincent,

    So essentially the JES Spool Volumes that are being used are full.  The easiest and first thing that I would try is to see what is using the JOB Spool, to do this issue the operator command:

    $D JOBQ,SPOOL=(%>nnn)

    As outlined in this link:

    https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.hasa700/jinktgs.htm?lang=en-us

    This will tell you what jobs are in the spool, if there are any that you can purge this will help to clean up the spool.  The next step will be to check the JES2 configuration to see if additional volumes can be added for the spool.

    Regards,

    Rick

    rbrunkh


  • 3.  Re: *$HASP050 JES2 RESOURCE SHORTAGE OF TGS - 100% UTILIZATION REACHED

    Posted Fri May 13, 2016 01:03 AM

    Hi Rick,

     

    We have executed $D JOBQ,SPOOL=(%>10)  we found only few entries(refer the below screenshot.). Do we need to purge any of these entries?

    Also note we have run this command after IPL with cold start (option 1). 

    We have also executed $T SPOOLEF Command. (Please refer the attached screenshot).

     

    Regards,

    Vincent

     

     

    Tauro81

    Attachments

    jobq_1.png
    SPOOLDEF.png


  • 4.  Re: *$HASP050 JES2 RESOURCE SHORTAGE OF TGS - 100% UTILIZATION REACHED

    Posted Fri May 13, 2016 06:57 AM

    Sometimes this can happen during ipl because TCP/IP for whatever reason is delayed in starting.  OMVS and ZFS will not fully initialize until the TCP/IP stack is up.  Depending on the number of subsystems you are trying to start, (you are starting CICS, IMS, and DB2,) you can see this problem.  I avoid it by defining a second spool volume.  This is a relatively easy thing to do.  If you don't want a second spool volume, you can delay the start of your subsystems until after you ipl your system and the network and OMVS and ZFS are up all the way.  If you don't ipl frequently and your system is up for days, (like mine is,) its a good idea to add a $P command to your daily automation to ensure spool data does not accumulate.

     

    RDzJohn

    RDzJohn


  • 5.  Re: *$HASP050 JES2 RESOURCE SHORTAGE OF TGS - 100% UTILIZATION REACHED

    Posted Thu May 19, 2016 05:58 AM

    Hi RDzJohn,

     

    We have IPLed with the cold start option 1. (i.e Without starting subsystem like CICS, IMS and DB2). But still the error message continues and TSO user are not able to login. We restarted(IPLed) several times with the cold start. Also $P command shows a message No entries found.

    Could you please Guide us on adding the volume to spool, We have tried all the commands available on blog but nothing is working

     

    Regards,

    Vincent

    Tauro81


  • 6.  Re: *$HASP050 JES2 RESOURCE SHORTAGE OF TGS - 100% UTILIZATION REACHED

    Posted Fri July 01, 2016 04:07 PM

    Vincent,

    Most of the junk is the SMFDUMP job.  Turn off your type 99 records in SMFPRMxx, and these jobs will go from once an hour to once a day.  Be sure to go out to SDSF on at least a weekly basis and delete unnecessary output.  Also, when you get into this situation, issue this command:  $poj,age>20.  This deletes all spool datasets older than 20 days.

    Regards,

    Tom Conley

    PinnacleConsutling


Related Content