|
Hi Chris, Due to holidays I've only just seen your message. Obviously to really solve your problem you need to shell out for more interactive welly from IBM, however there IS some damage limitation you can do. I have had some success with the following technique: 1) Reduce the activity level in QINTER to 7 or less (aiming to restrict interactive work) 2) Check that the timeslice of the QINTER class is something like 300 (depending on the size of your box) - not the shipped default 2000 - if 2000, change it. 3) Ensure that your other work (batch, query, etc) does not run at normal priority (i.e. 50 for batch) - raise these priorities to 35, say. This will prevent the situation where, as soon as CFINT kicks in, all the jobs get their priorities reduced to 89 and the system feels like you're trying to walk through treacle! OK, some users will have to wait when their interactive jobs go 'ineligible', but this is the price you pay for avoiding total system sludge mode. You could also get interactive users to 'schedule' their work - i.e. orders in the morning, accounts in the afternoon etc - like we used to do years ago! The priority thing is because IBM have so called 'bands' of priority, and when an active job gets downgraded it goes to the next 'band' down. If you want any more info, or help, please e-mail me offline and I'll see what I can do, cheers, Clare Clare Holtham IBM Certified AS/400 Systems Administrator SmallBlue Services E-Mail: Clare.Holtham@btinternet.com Mobile: +44 (0)7960 665958 ----- Original Message ----- From: "Chris Wenk" <christophe.wenk@kuehne-nagel.com> To: <MIDRANGE-L@midrange.com> Sent: Monday, April 30, 2001 7:48 AM Subject: Performance problem > Hi all > > I've got a performance problem on my AS/400 720. > Most likely I've got to many users doing a signon > and therefore the task "CFINT01" is more or less > constantly over 80%. > (Have V4R4M0, and loaded the latest cumulative ptfs) > I know that an upgrade of the interactive card would help. > However, to avoid the problem as an interim solution I would like to > restrict the access on QINTER. I tried to change with > CHGJOBQE the maximum active jobs to 60. This didn't help. > After 60 entries other people can still logon. > > Any ideas/examples ? > > Thanks a lot > Chris > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.