|
DSPJOBTBL was not found on either our V3R2 or V3R7 boxes. We are going to proceed with changing the system values QACTJOB & QTOTJOB, if for no other reason than to follow the advice given in the IBM help text for those values. The other thing I learned is that they never IPL the V3R2 box until they have to (PTFs, what else is there?). Nobody knows for sure, but the last time they IPL'd this box was probably two or three months ago. Dan Bale IT - AS/400 Handleman Company 248-362-4400 Ext. 4952 -----Original Message----- Type in dspjobtbl and press enter. If it works at your release, it will show you how many job tables exist on the machine, how big they are, and some other data. Long "job display" times usually arise when the total size of job tables is a big number. There is a cleanup option described in V4R3 - CHGIPLA - but I don't know if it works at V3R2. Your other findings aren't the reason that it takes 30 seconds to scan all the jobs. The system values are not causing this problem - although they may be causing other issues. The RISC box manages job tables better than CISC but I seem to remember a PTF to help with job table management. Richard Jackson mailto:richardjackson@richardjackson.net http://www.richardjacksonltd.com Voice: 1 (303) 808-8058 Fax: 1 (303) 663-4325 > |-----Original Message----- > |From: owner-midrange-l@midrange.com > |[mailto:owner-midrange-l@midrange.com]On Behalf Of D.BALE@handleman.com > |Sent: Friday, September 29, 2000 8:51 AM > |To: MIDRANGE-L@midrange.com > |Subject: Re: WRKSBMJOB, WRKUSRJOB slug-li > | > | > |In addition to my last post, WRKACTJOB shows Active jobs = 127. > | > |Got smart (?) and looked up the help for the QACTJOB & QTOTJOB > |values. Seems > |clear how to set these at the lowest level. Should I set a > |value high enough > |for these so that the "additional" jobs never (or hardly ever?) > |has to kick > |in? What's the penalty for setting these too high? > | > |When do these changes take effect? Next IPL? (Help didn't say.) > | > |James, > | > |Thanks for the reply! I had never known to look for this before > |but, needless > |to say, I was a little shocked when I found the following numbers: > | > |WRKSYSSTS shows Jobs in system = 514 (for the past 10 minutes, it's been > |hovering in the 512 - 515 range) > | > |Our system values: > |QACTJOB - Initial number of active jobs 20 > |QADLACTJ - Additional number of active jobs 10 > |QADLTOTJ - Additional number of total jobs 10 > |QTOTJOB - Initial total number of jobs 30 > | > |Are these the shipping defaults from the factory? I _think_ I > |want to change > |QTOTJOB to 500, but will wait for advice from those who know > |better on the > |list. I have no reason to believe that 514 number goes much > |higher; we run > |fairly level all day long. > | > |Just to compare, we have a V3R7 box that currently has 799 "jobs in the > |system" and has the same system values as shown above. However, both > |WRKSBMJOB & WRKUSRJOB respond within 1-2 seconds. Does the RISC > |box manage > |fragmented job data better than CISC? > | > |Dan Bale > |IT - AS/400 > |Handleman Company > |248-362-4400 Ext. 4952 > | > | > |----------------- Original Message ----------------- > |Dan, > | > |You may want to look at the system values for initial number of jobs and > |additional number of jobs, then the total number of jobs on the system. > | > |I've seen this happen when job data is fragmented. > | > |D.BALE@handleman.com wrote: > |> > |> Good grief! WRKSBMJOB & WRKUSRJOB are absolutely slug-like on > |this V3R2 > |> system. It can take up to 30 seconds to get a response, > |everything else > |> (i.e., WRKSPLF, WRKACTJOB) is at or near sub-second response. > |This on a > |> system where the CPU usage is 8.2% for a two minute interval > |(right now). > | Is > |> this a V3R2 issue? > |> > |<<snip>>
>>>>>>>>>>>>>> Global CS Original External RFC822 Hdrs Begin <<<<<<<<<<<<<< X-Env-Sender: midrange-l-owner@uucphost.mcs.net X-Env-Recipient: D.BALE@handleman.com X-End-of-Envelope: Received: from uucphost.mcs.net (192.160.127.90) by ntgcs.handleman.com (NPlex 2.0.108) for D.BALE@handleman.com; 29 Sep 2000 12:17:54 -0400 Received: (from 66@localhost) by uucphost.mcs.net (8.9.3/8.9.3) with UUCP id LAA70250; Fri, 29 Sep 2000 11:24:25 -0500 (CDT) (envelope-from midrange-l-owner) X-Authentication-Warning: Kitten.mcs.net: 66 set sender to midrange-l-owner using -f Received: (from majordom@localhost) by linux.midrange.com (8.9.3/8.8.7) id KAA31600 for midrange-l-outgoing; Fri, 29 Sep 2000 10:50:08 -0500 Received: (from uucp@localhost) by linux.midrange.com (8.9.3/8.8.7) with UUCP id KAA31589 for MIDRANGE-L@midrange.com; Fri, 29 Sep 2000 10:50:05 -0500 Received: from prserv.net (out5.prserv.net [32.97.166.35]) by uucphost.mcs.net (8.9.3/8.9.3) with ESMTP id KAA62234 for <MIDRANGE-L@midrange.com>; Fri, 29 Sep 2000 10:49:30 -0500 (CDT) (envelope-from richardjackson@richardjackson.net) Received: from jacksonr01 ([32.101.226.42]) by prserv.net (out5) with SMTP id <20000929154919205028i8q1e>; Fri, 29 Sep 2000 15:49:20 +0000 From: "Richard Jackson" <richardjackson@richardjackson.net> To: <MIDRANGE-L@midrange.com> Subject: RE: WRKSBMJOB, WRKUSRJOB slug-li Date: Fri, 29 Sep 2000 09:49:14 -0600 Message-ID: <NEBBKBDJELLGCFGEOMPHEELFCKAA.richardjackson@richardjackson.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <NY654221-178b6d7f@handleman.com> Importance: Normal Sender: owner-midrange-l@midrange.com Reply-To: MIDRANGE-L@midrange.com Errors-To: list-errors@midrange.com X-List-Name: Midrange Systems Mailing List (MIDRANGE-L@midrange.com) >>>>>>>>>>>>>>> Global CS Original External RFC822 Hdrs End <<<<<<<<<<<<<<<
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.