ca.portal.admin

Storage Pools SOS in R16

Discussion created by ca.portal.admin on Jun 5, 2006
We're noticing that our XA storage pools are going SOS quite often even
though high water marks are showing at 75-80% of the pool. We're on
SP2
and have 55 production CVs of varying sizes and the problem is pretty
consistent. Quite often it only shows up in the JES log (message
DC015007)
and not in the DCMT storage pool displays. I suppose we could have been
getting these in R15 and didn't know it because there was no JES message
in
that release, but I believe storage management was changed in R16. The
pools do look fragmented on occasion, so that could account for some of
it.
However, something about this doesn't feel right after observing this
new
release for several months in prod, so I'm wondering if anyone else has
noticed an increase in XA storage usage in R16 and/or an increase in
number
of SOS. Any help, insights or apars to look at appreciated.



Thanks.



Linda Campbell

Informatix, Inc.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Storage Pools SOS in R16
"We're noticing that our XA storage pools are going SOS quite often even
though high water marks are showing at 75-80% of the pool. We're on SP2
and have 55 production CVs of varying sizes and the problem is pretty
consistent. Quite often it only shows up in the JES log (message DC015007)
and not in the DCMT storage pool displays. I suppose we could have been
getting these in R15 and didn't know it because there was no JES message in
that release, but I believe storage management was changed in R16. The
pools do look fragmented on occasion, so that could account for some of it.
However, something about this doesn't feel right after observing this new
release for several months in prod, so I'm wondering if anyone else has
noticed an increase in XA storage usage in R16 and/or an increase in number
of SOS. Any help, insights or apars to look at appreciated.



Thanks.



Linda Campbell

Informatix, Inc.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Performance on 16.0
"Hi,



For all those who were interested in the performance enhancement that
TB96715 provided for 16 SP2/3 there is now TB96714 for 16 SP1 systems.
We will be testing this over the next few weeks. Also TB96715 has been
changed again.



Chris Wood

Alberta Department of Energy

CANADA

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] Performance on 16.0
" Also TB96715 has been
changed again.



just curious - does CA provide notification when a provisional fix is
modified to those who have had the fix attached to an issue? (if not, it
sounds like a good idea to me)

chris (still looking for a fix for me) hoelscher



The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
CAS Question
"Hello All:

In CAS we are adding a new data base to be used with the applications.
Everything is set up properly with the DBNAME and DICTNAME but we are getting
""Application not installed""? I seem to remember that you have to define the
application with the new DBNAME somewhere in the CAS Security System but, It has
been so long since I did this I have forgotten how, can someone please help me
with this?

Bill Allen

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Broken pointer utility
"We have a problem with logicaly deleted records. idmsdban shows no
corruption. cleanup is getting an abend 3134 error status 0361. a
logically deleted owner is being pointed at by three logically deleted
members (next pointer at end of set) in three sets of the same name.
How it got to be that way is a mystery.

Lutz Petzold

Outcomes