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(nnnnM) for SOS above the line
where nn or nnnn 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 DFHSMnnnn message for SOS to issue the CEMT
transaction via the console to alter the limit.
--
______________________________________________________________________
Regards,
Thomas Dunlap Chief Technology Officer t...@themisinc.com
Themis, Inc. http://www.themisinc.com 908 400-6485
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
