|
Ok, 3 questions: 1. What exactly is the directory threshold? 2. Is there any way out of this besides an IPL? 3. What causes this to get used up? > -----Original Message----- > From: Alistair Rooney [mailto:AlistairR@tbsa.co.za] > Sent: Friday, August 31, 2001 8:18 AM > To: midrange-l@midrange.com > Subject: RE: CPI0999 > > > This is a multi-part message in MIME format. > -- > [ Picked text/plain from multipart/alternative ] > Oh WAIT! It's the *directory* threshold, not the threshold! I seem to > remember that an IPL will solve that problem. I think this is > similar to > the "directory entries" in Windoze. "Similar" being the > operative word. > > Alistair > > -----Original Message----- > From: Condon, Mike, /m1c [mailto:m1c@ingersoll-imc.com] > Sent: 31 August 2001 15:14 > To: 'midrange-l@midrange.com' > Subject: RE: CPI0999 > > > It's set to 90%, which leaves this all still a mystery. > The only thing I can think of that I have changed lately is setting > the paging option for *BASE & INTERACT in wrksyssts to *CALC instead > of *FIXED. > However this does not explain the misleading percentages of ASP used. > > -----Original Message----- > From: Alistair Rooney [mailto:AlistairR@tbsa.co.za] > Sent: Friday, August 31, 2001 7:26 AM > To: midrange-l@midrange.com > Subject: RE: CPI0999 > > > This is a multi-part message in MIME format. > -- > [ Picked text/plain from multipart/alternative ] > Somebody could have fiddled with your Threshold. Check this > by STRSST to > go into service tools. Work with disk units, Work with disk > configuration and then work with ASP Threshold. > > You should have it set to 85-90% depending on your mood. > > Should help, > > Alistair > > -----Original Message----- > From: Condon, Mike, /m1c [mailto:m1c@ingersoll-imc.com] > Sent: 31 August 2001 14:17 > To: 'midrange-l@midrange.com' > Subject: CPI0999 > > > Even though wrksyssts shows: > Auxiliary storage: > System ASP . . . . . . : 77.30 G > % system ASP used . . : 32.1884 > Total . . . . . . . . : 77.30 G > Current unprotect used : 1940 M > Maximum unprotect . . : 54820 M > I am getting the following message (cpi0999). I'm IPL'ing this weekend > which > may fix the problem, but otherwise what could be > causing this? > > Storage directory threshold reached. > Message ID . . . . . . : CPI0999 Severity . . . . . > . . : 80 > > Message type . . . . . : Information > > Date sent . . . . . . : 08/31/01 Time sent . . . . . . : > 06:06:31 > > > Message . . . . : Storage directory threshold reached. > > Cause . . . . . : The storage directory is nearing > capacity. This is > a > > potentially serious system condition. This message will > be repeated > until > an IPL has been performed. > > Recovery . . . : The amount of storage used on the system must be > reduced. > To reduce the amount of storaged used, do the following: > > -- Delete objects from the system that are not needed. > > -- Save objects that are not needed online by specifying > STG(*FREE) > on > the > Save Object (SAVOBJ) command. > > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > > ********************************************************************** > 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. > > This footnote also confirms that this email message has been swept by > MIMEsweeper for the presence of computer viruses. > > www.mimesweeper.com > ********************************************************************** > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > > ********************************************************************** > 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. > > This footnote also confirms that this email message has been swept by > MIMEsweeper for the presence of computer viruses. > > www.mimesweeper.com > ********************************************************************** > _______________________________________________ > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.