|
AFAIK the IBM subsystem monitors already should run in the *BASE pool, WRKACTJOB/F11 will show you. I do agree with changing sysval QTSEPOOL to *BASE to purge long running jobs; note that you must also set the Time slice and Eligible for purge parameters in the QINTER class to make this work. The default Time slice has been 2000 ms since the S/38 days(I use 50 ms on one prod system and 100 ms on another) and Eligible for purge must be *YES or the job will ignore the QTSEPOOL setting. I would rather have the performance adjuster give QINTER all the memory that it needs than create a bunch of additional sbsds and pools to manage. We have had more than 800 users in QINTER with no complaints, in fact the last 100 thought that it was an improvement. I do like to make sure that batch runs in it's own pool rather than in *BASE or *INTERACT. I would think that you could easily run 1000 or more users in a sbs with an 11 processor LPAR. What kind of application is it and what is your avg. response time? Regards, Scott Ingvaldson AS/400 System Administrator GuideOne Insurance Group -----Original Message----- date: Tue, 23 Sep 2003 15:22:50 +0100 from: Jeff Bull <Jeff.Bull@xxxxxxxxxxxxxxx> subject: RE: QINTER problems: CPF5390, CPF1317, CPF1189, CPF1196 I recall having this problem a couple of years ago, as far as I can remember, the symptoms and cause where near enough identical. I never did solve it as such, but managed to reduce the frequency of occurences ... Split the QINTER subsystem monitor job and the interactive jobs into separate pools (subsystem-pools in different system pools - I moved SBS-pool-1 to *BASE, used the routing entries to put the interactive jobs into sbs-pool-2, *INTERACT). The *NOMAX activity level on QINTER-sbsd is bad news, particularly when developers (super users) run batch-style jobs there. Use the TimeSlicePoolEnd value to purge them to the batchpool. Use multiple QINTERx sbs's and workstation name/type entries to keep the overall number of jobs in a subsystem down to 200 or less. This may of course necessitate the purchase of more system memory. ... my tuppence worth ... Kind regards, Jeffrey E. Bull OS400 Software Support Consultant IBM Certifiied iSeries System Implementation Expert IBM Certified AS/400 System Administrator tel. +44 [0] 149 454 9533 swb. +44 [0] 149 454 9400 mbl. +44 [0] 786 750 4961 fax. +44 [0] 149 454 9454 web. http://www.itm-group.co.uk ITM Group Ltd, Latimer Square, White Lion Road, Amersham, Buckinghamshire, HP7 9JQ, United Kingdom -----Original Message----- From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] Sent: 22 September 2003 20:11 To: Midrange Systems Technical Discussion Subject: Re: QINTER problems: CPF5390, CPF1317, CPF1189, CPF1196 IBM's response: It appears that the subsystem was busy processing device errors, and didn't respond to the Retrieve Group Attributes request. After the interactive job wits 30 seconds for the subsystem to reply, it will post the CPF1317. . Out first recommendation would be to check the number of users in the interactive subsystem. We recommend only having 250 - 300 users in an interactive subsystem, and we may see a variety of errors if that number is exceeded. The subsystem is just bogged down too much with device processing if we have too many devices. . Second, there are a few PTFs we'd recommend for general subsystem concerns. I'd recommend downloading and applying SI09702 and SI09642 for 5722SS1. There is a third PTF for APAR SE11621, but this third PTF is not yet available. . Hopefully, these recommendations should help prevent this problem from occurring again. By the way, this error occurred in SYS501C. Some of you know what that program is, and also know that I do not have access to the source, etc. I'll order the ptf's and see what they do. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin _______________________________________________ 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 e-mail has been scanned for all viruses by ITM. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, email marketing@xxxxxxxxxxxxxxx ITM - Managing Communication and Information through technology Company registration number - 3783433 ________________________________________________________________________ DISCLAIMER Any opinions expressed in this email are those of the individual and not necessarily the Company. This email and any files transmitted with it, including replies and forwarded copies (which may contain alterations) subsequently transmitted from the Company, are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this email in error and that any use is strictly prohibited. If you have received this email in error please notify the IT manager by telephone on +44 (0)870 871 2233 or via email to Administrator@xxxxxxxxxxxxxxx, including a copy of this message. Please then delete this email and destroy any copies of it. ________________________________________________________________________This e-mail has been scanned for all viruses by ITM. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, email marketing@xxxxxxxxxxxxxxx ITM - Managing Communication and Information through technology Company registration number - 3783433_____________________________________________________________________ ___ ------------------------------ _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest 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. End of MIDRANGE-L Digest, Vol 2, Issue 1462 ******************************************* This message and accompanying documents are covered by the Electronic Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information intended for the specified individual(s) only. This information is confidential. If you are not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, copying, or the taking of any action based on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
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.