Re: Short on Storage
Have you looked at your shutdown stats? How about doing a STAT and taking a look at them. Hoping you have this setup at least... Hughes From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Barkow, Eileen <ebar...@doitt.nyc.gov> Sent: Tuesday, October 17, 2017 12:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Short on Storage Where is the storage shortage - below or above the line? The DFH* msg will tell you. If above the line, just increase the EDSALIM (you should be using IEFUSI exit set to allow max above the line storage and REGION=0M). If below, check with MVS group that DSALIM is at the max you can get for your lpar. If below and at max DSALIM, you have problems. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of gsg Sent: Tuesday, October 17, 2017 12:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Short on Storage We periodically have Short on Storage conditions with CICS. Not being a CICS person, I'm trying to find out what can be done to monitor and or prevent Short on Storage conditions. Of the top, I don't think it's really possible to expect we'd be able to absolutely prevent them. Basically, how can the CICS guys be proactive in trying to prevent the SOS condition. Also, is there a way our Operations staff could react quickly to relieve the SOS condition prior to calling the CICS guy, waiting for him to VPN into the system to troubleshoot etc... TIA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -- 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
Re: Short on Storage
Where is the storage shortage - below or above the line? The DFH* msg will tell you. If above the line, just increase the EDSALIM (you should be using IEFUSI exit set to allow max above the line storage and REGION=0M). If below, check with MVS group that DSALIM is at the max you can get for your lpar. If below and at max DSALIM, you have problems. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of gsg Sent: Tuesday, October 17, 2017 12:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Short on Storage We periodically have Short on Storage conditions with CICS. Not being a CICS person, I'm trying to find out what can be done to monitor and or prevent Short on Storage conditions. Of the top, I don't think it's really possible to expect we'd be able to absolutely prevent them. Basically, how can the CICS guys be proactive in trying to prevent the SOS condition. Also, is there a way our Operations staff could react quickly to relieve the SOS condition prior to calling the CICS guy, waiting for him to VPN into the system to troubleshoot etc... TIA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Short on Storage
On 10/17/2017 12:43 PM, gsg wrote: We periodically have Short on Storage conditions with CICS. Not being a CICS person, I'm trying to find out what can be done to monitor and or prevent Short on Storage conditions. Of the top, I don't think it's really possible to expect we'd be able to absolutely prevent them. Basically, how can the CICS guys be proactive in trying to prevent the SOS condition. Also, is there a way our Operations staff could react quickly to relieve the SOS condition prior to calling the CICS guy, waiting for him to VPN into the system to troubleshoot etc... TIA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN It is possible to dynamically raise the limit CICS is using. You have to enter the following CEMT transaction from the console: CEMT SET DSAS DSALIMIT(nnM) for SOS below the line CEMT SET DSAS EDSALIMIT(M) for SOS above the line where nn or is the number of megabytes for the new limit Caution, do not consume all of the free z/OS storage, leave a megabyte or two below the line and a couple of 100 megabytes above the line for z/OS usage. If you have a real-time monitor like Omegamon, is should be easy to monitor the DSA usage. Also, if you have an automation tool, you could run a script based upon the DFHSM message for SOS to issue the CEMT transaction via the console to alter the limit. -- __ Regards, Thomas DunlapChief Technology Officert...@themisinc.com Themis, Inc.http://www.themisinc.com908 400-6485 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Short on Storage
If you were not aware, there is also a CICS list that might be helpful To join, if you have not done so, go to this URL CICShttp://www.listserv.uga.edu/archives/cics-l.html Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of gsg > Sent: Tuesday, October 17, 2017 9:44 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Short on Storage > > We periodically have Short on Storage conditions with CICS. Not being a CICS > person, I'm trying to find out what can be done to monitor and or prevent > Short on Storage conditions. Of the top, I don't think it's really possible > to expect we'd be able to absolutely prevent them. Basically, how can the > CICS guys be proactive in trying to prevent the SOS condition. Also, is > there a way our Operations staff could react quickly to relieve the SOS > condition prior to calling the CICS guy, waiting for him to VPN into the > system to troubleshoot etc... > > TIA > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Short on Storage
Start by getting an SVC dump Issue CEMT I SYSD and set the dump table to capture a dump I very familiar with Short-On-Storage, You can contact me off list if necessary -- Original Message -- From: gsg <0053fe88ed35-dmarc-requ...@listserv.ua.edu> To: IBM-MAIN@LISTSERV.UA.EDU Subject: Short on Storage Date: Tue, 17 Oct 2017 11:43:52 -0500 We periodically have Short on Storage conditions with CICS. Not being a CICS person, I'm trying to find out what can be done to monitor and or prevent Short on Storage conditions. Of the top, I don't think it's really possible to expect we'd be able to absolutely prevent them. Basically, how can the CICS guys be proactive in trying to prevent the SOS condition. Also, is there a way our Operations staff could react quickly to relieve the SOS condition prior to calling the CICS guy, waiting for him to VPN into the system to troubleshoot etc... TIA -- 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
Short on Storage
We periodically have Short on Storage conditions with CICS. Not being a CICS person, I'm trying to find out what can be done to monitor and or prevent Short on Storage conditions. Of the top, I don't think it's really possible to expect we'd be able to absolutely prevent them. Basically, how can the CICS guys be proactive in trying to prevent the SOS condition. Also, is there a way our Operations staff could react quickly to relieve the SOS condition prior to calling the CICS guy, waiting for him to VPN into the system to troubleshoot etc... TIA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
