|
Hi, Although I never thought about it before, I personally think that a lower limit option is a plausibly good idea. To the credit of IBM, they kept the default which was the old implicit limit of a job. A new lower limit would be an enhancement to my opinion. I will pass this on to IBM (with a bcc: to this note). Given the availability of the new system value, it strikes me that a new lower limit would be trivial for IBM to implement. Al - in Rochester, where I'm almost finishing the best two week school I've ever had (taught in four and a half days) Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com midrange-l-bounces@xxxxxxxxxxxx wrote on 06/05/2003 11:18:08 PM: > Personally, I was glad to see QMAXSPLF introduced. But I was > disappointed that the default 9999 is also the minimum value. I was > hoping to reduce the max # of spool files a job can generate; not > increase it. We have the occasional runaway JDE interactive job (in > certain programs when the session gets unexpectedly disconnected) that > loops creating job logs and dumps until it cannot create any more spool > files. It uses our interactive capacity and wastes up to about 4GB disk > space if not stopped. I would love to set the QMAXSPL to, say, 1000 to > limit the impact of these jobs. > > John > > -----Original Message----- > From: Al Barsa [mailto:barsa@xxxxxxxxxxxxxxxxxxx] > Sent: Thursday, June 05, 2003 9:34 PM > To: Midrange Systems Technical Discussion > Subject: Re: Max Spool files > > A new sysval value was added in V5R1, QMAXSPLF. The default is 9999. > The maximum value per job is 999,999. > > Caution, based on source and a number of other factors, the total number > of maximum spooled files on a system ranges between 1.2M to 3.6M. > > Al > > Al Barsa, Jr. > Barsa Consulting Group, LLC > > 400>390 > > 914-251-1234 > 914-251-9406 fax > > http://www.barsaconsulting.com > http://www.taatool.com > This e-mail is for the use of the intended recipient(s) only. If > you have received this e-mail in error, please notify the sender > immediately and then delete it. If you are not the intended > recipient, you must not use, disclose or distribute this e-mail > without the author's prior permission. We have taken precautions to > minimize the risk of transmitting software viruses, but we advise > you to carry out your own virus checks on any attachment to this > message. We cannot accept liability for any loss or damage caused > by software viruses. > > > > _______________________________________________ > 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. >
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.