× 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.


  1.  Home
  2. MIDRANGE-L
  3. November 2016

RE: Job run times occasionally seriously spike. How do I start to figure this out?

Hi Rob,

Being a rookie, I would do this:

I would not use Navigator for i. I am fed up with its erratic behaviour. (I
also encountered the same issue as you.) I would start with good ol' green
screen GO PERFORM. I would start to compare ERP* job's running times (using
the history log, filtering job start/end messages), to see when it started.
Then I would check performance data to see if there is a job, or LIC task
eating up performance during the jobs running time. Has the program ran by
those ERP* jobs changed? Is the running time in seconds showed by the
CPF1164 messages in the History log significantly shorter then the "real"
running time (end time -start time)? If yes, I would suspect some other
waits increase (DLYJOB statements in the application for instance.)

My two cents worth.

Regards,
Fred

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.