× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: WRKSBMJOB, WRKUSRJOB slug-like
  • From: "Gary R. Patterson" <midrange-l@xxxxxxxxxxxxx>
  • Date: Thu, 28 Sep 2000 17:22:58 -0500
  • Importance: Normal

I'll bet that if you reduce the number of jobs in the system (delete 10,000
or so of those old job logs), the commands will run faster.

To keep them cleaned up, GO CLEANUP and configure a short retention period
for job logs.  You can also change key job descriptions (like QDFTJOBD) to
LOG(4 0 *NOLIST) if you do not require a job log for jobs that end normally.

Gary R. Patterson
NexSource, Inc.

Information technology services for business
http://www.nexsource.com



-----Original Message-----
From: owner-midrange-l@midrange.com
[mailto:owner-midrange-l@midrange.com]On Behalf Of D.BALE@handleman.com
Sent: Thursday, September 28, 2000 4:11 PM
To: MIDRANGE-L@midrange.com
Subject: WRKSBMJOB, WRKUSRJOB slug-like


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?

I recall getting 2- or 3-second response with WRKSBMJOB even on some RISC
boxes, and had resorted to using WRKUSRJOB JOBTYPE(*BATCH) to get the
subsecond response.  Either way, on this V3R2 box, it's a painful wait for
someone who's used to getting it FAST.

Anything I can do to improve on this?  Cleanup of some sort?

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952
+---
| 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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.