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



Are you using F5 or F10 to view the CPU in WRKACTJOB? And how much time
are you sleeping?

I have similar jobs that do this and when sleeping take virtually zero CPU.

Brad
www.bvstools.com



On Mon, Mar 17, 2014 at 8:30 AM, Gary Thompson <gthompson@xxxxxxxxxxx>wrote:

We run a "never-ending" job that monitors for
shipments that are ready for customer delivery
and which require an EDI 856 Advance Shipment
Notice.

My question is why the amount of CPU use reported
on Work with Active Jobs shows something like 34%
when the job is in Status = TIMA ?

The exact percent CPU use appears to vary depending
on load so that the use during Status = TIMA is lower
on a busy system, and higher on a less busy system.

This job is based on an SQLRPGLE program that calls
sleep() between steps which process products as they
are prepared for customer delivery and creates the
required documents and data required for the Advance
Shipment Notice.

I wonder if it would be better to replace the call to sleep()
with a call to a CLLE module to run a DLYJOB command ?
--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.