Date:         Wed, 28 Jun 2000 01:50:14 -0700
Reply-To:     CICS List <CICS-L@LISTSERV.UGA.EDU>
Sender:       CICS List <CICS-L@LISTSERV.UGA.EDU>
From:         Bob Halpern <Bob@CPUPERFORM.COM>
Organization: CPU http://www.CPUperform.com
Subject:      Re: Resolving SOS condtions
Content-Type: text/plain; charset=us-ascii

This is when a monitor, like Omegamon/CICS or TMON/CICS would be very
handy. They would be able to tell you who is using all the storage.

"Chalker, Craig" wrote:
>
> Hi Folks,
>              I am after some thoughts here on finding the culprit for a SOS
> condition in EUDSA. I have a region that from time to time experiences this
> problem and I thought a CEMT PERFORM DUMP or PERFORM SNAP would give me the
> info I needed to find out who was eating up EUDSA. However, the region is
> effectively stalled and I can't get CEMT dispatched.
> The region EUDSA is currently about 70M and 80% of the time hovers around
> 10% used, there are infrequent peaks throughout the day where it hits around
> the 50-60% used mark. Once every couple of weeks it goes to ~100% and I get
> the stall condition.
> As I said, I need to find out who is causing the condition but can't do a
> PERFORM DUMP or SNAP. I thought maybe an MVS dump of the address space, but
> I'm not sure if I could still use the CICS verbx commands in IPCS if I took
> this approach.
> Anyone ran into this issue before ? I could use some suggestions as to the
> best way to approach getting a dump while the region is still SOS.
> BTW the region is TS 1.3 and OS/390 is 2.8
> Thanks,
> Craig.
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager of QR.
>
> This message has been swept by MIMESweeper for the presence of computer
> viruses. No warranty is given that this message upon its receipt is
> virus free and no liability is accepted by the sender in this respect.
>
> This email is a message only; does not constitute advice and should not
> be relied upon as such.
> **********************************************************************