|
temp storage space. Will have to schedule that.... The ptf doesn't seem to indicate any of IBM's own programs might be the problem but lets hope. I just checked only other system I have put cume on, and it had a similar increase in temp storage used. I've applied ptf and was able to ipl (a development machine). Temp storage went down 1.5 gig (from 5.5 to 4.0 gig). I do see it is the QIBMHELP process that is chewing up resources after ipl, and temp storage increased from 2 to 4 gig. On a very small machine, with only 35 gig, this makes a big difference. I'll ask the QIBMHELP question in another thread. jim franz----- Original Message ----- From: <rob@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Monday, February 12, 2007 4:04 PM Subject: [SPAM] Re: temp storage since cume c7002540
Any possibility? http://www-912.ibm.com/s_dir/slkbase.nsf/ibmscdirect/064EED642D6D78A58625714E0076157B Found this at: http://www-912.ibm.com/s_dir/slkbase.nsf/recommendedfixes and selecting "Temporary Disk Space". Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Jim Franz" <franz400@xxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 02/12/2007 03:46 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To <MIDRANGE-L@xxxxxxxxxxxx> cc Fax to Subject temp storage since cume c7002540 Applied cume this weekend to a 35gig model 800. After ipl, we watched disk space usage go from 73% to 84% in first 10 minutes. Looked at archives & was a thread sort of linking temp storage space & QSRVMON and system value qsfwerrlog. Turned value off, ipl, same problem (although the 30 to 40 "srv" jobs no longer running. Temp storage usually just over a gig. Now over 4 gig. Can see a number of IBM "q" programs running after ipl, but can't see what's normal and what's not. Any ideas (before I open a ticket with IBM)? jim franz -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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 listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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.