|
This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. -- Kirk you are exactly right. Here is the message from the documentation... CPI0999 Storage directory threshold reached. The storage directory is nearing capacity. This is a potentially serious system condition. The system repeats this message until it receives an IPL. You must reduce the amount of storage that is used on the system. To reduce the amount of storage that is 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 >>> "Kirk Goins" <kirkg@pacinfosys.com> 02/04/02 03:47PM >>> This indicates that the total number of objs that the system can put on disk is approaching the max number. example: (I don't know the real numbers) Lets say the system can have 100,000 objects on the system, you have say 95,000 or some other high number. When you hit 100,000 it's like running out of disk. Again I don't know the real numbers this is just a example. I would run a RCLSTG and see what you get. -----Original Message----- From: Chuck Lewis [ mailto:clewis@iquest.net] Sent: Monday, February 04, 2002 12:31 PM To: midrange-l@midrange.com Subject: Re: Message Dave, Do a wrksyssts and see what % system ASP used is at. Do you have a bunch of job logs you can get rid of ? Did you just install some new software or something ? Chuck Dave Snyder wrote: > Can someone explain this message, how critical is it, what causes it, and how >can I avoid it in the future? > Thanks. > Dave > > Message ID . . . . . . : CPI0999 Severity . . . . . . . : 80 > Message type . . . . . : Information > Date sent . . . . . . : 02/04/02 Time sent . . . . . . : 14:43:49 > > 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 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 . -- [ Converted text/html to text/plain ] Kirk you are exactly right. Here is the message from the documentation... CPI0999 Storage directory threshold reached. The storage directory is nearing capacity. This is a potentially serious system condition. The system repeats this message until it receives an IPL. You must reduce the amount of storage that is used on the system. To reduce the amount of storage that is 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 >>> "Kirk Goins" <kirkg@pacinfosys.com> 02/04/02 03:47PM >>> This indicates that the total number of objs that the system can put on disk is approaching the max number. example: (I don't know the real numbers) Lets say the system can have 100,000 objects on the system, you have say 95,000 or some other high number. When you hit 100,000 it's like running out of disk. Again I don't know the real numbers this is just a example. I would run a RCLSTG and see what you get. -----Original Message----- From: Chuck Lewis [ mailto:clewis@iquest.net][1] Sent: Monday, February 04, 2002 12:31 PM To: midrange-l@midrange.com[2] Subject: Re: Message Dave, Do a wrksyssts and see what % system ASP used is at. Do you have a bunch of job logs you can get rid of ? Did you just install some new software or something ? Chuck Dave Snyder wrote: > Can someone explain this message, how critical is it, what causes it, and how can I avoid it in the future? > Thanks. > Dave > > Message ID . . . . . . : CPI0999 Severity . . . . . . . : 80 > Message type . . . . . : Information > Date sent . . . . . . : 02/04/02 Time sent . . . . . . : 14:43:49 > > 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[3] > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l[4] > or email: MIDRANGE-L-request@midrange.com[5] > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l[6] . _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com[7] To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l[8] or email: MIDRANGE-L-request@midrange.com[9] Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l[10] . _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com[11] To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l[12] or email: MIDRANGE-L-request@midrange.com[13] Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l[14] . ===References:=== 1. mailto:clewis@iquest.net] 2. mailto:midrange-l@midrange.com 3. mailto:MIDRANGE-L@midrange.com 4. http://lists.midrange.com/cgi-bin/listinfo/midrange-l 5. mailto:MIDRANGE-L-request@midrange.com 6. http://archive.midrange.com/midrange-l 7. mailto:MIDRANGE-L@midrange.com 8. http://lists.midrange.com/cgi-bin/listinfo/midrange-l 9. mailto:MIDRANGE-L-request@midrange.com 10. http://archive.midrange.com/midrange-l 11. mailto:MIDRANGE-L@midrange.com 12. http://lists.midrange.com/cgi-bin/listinfo/midrange-l 13. mailto:MIDRANGE-L-request@midrange.com 14. http://archive.midrange.com/midrange-l
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.