MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2008

User ASP Overflow



fixed

Good morning ... over the weekend I had to deal with a user ASP
overflow.

I tried to resolve this issue without having to IPL, but even after
identifying all the objects that overflowed and then deleting them, the
system still indicated that there was 1mb that was still overflowed into
the system ASP.

I was finally forced to do an IPL to fix this issue.

I'm now thinking of changing how I handle things when an ASP is filled
up.

I would like to change the ASP attributes from this:

ASP number . . . . . . . . . . . ASP > 03
Threshold percentage . . . . . . THDPCT > 95
Compression recovery policy . . CPRRCVPCY > *OVERFLOW

To this:

ASP number . . . . . . . . . . . ASP > 03
Threshold percentage . . . . . . THDPCT > 95
Compression recovery policy . . CPRRCVPCY > *WAIT

Generally data stored in ASP3 on this system is developer related data
as opposed to production data, which is kept in the system ASP (ASP1).

What I hope this change will do is issue a critical message indicating
that ASP3 is full and all process using it are waiting for disk space to
become available. This would then give me time to remove some data from
ASP3 so these processes can continue running without spilling over into
ASP1.

Has anyone done something like this?

If so, can I expect all processes not writing to ASP3 disk to continue
running in the event that ASP3 reached 100% utilized?




Kenneth
Kenneth E. Graap
Systems Administrator
NW Natural
keg@xxxxxxxxxxxxx
503-226-4211 x5537






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact