|
Mark, just had a situation like this...the job log was 230+ pages... Go ahead and Pring it out...or view on line...what you're looking for is the time it takes for jobsteps to run. By doing a quick scan of the log you should be able to calc time of jobsteps and then you can determine what is the anomoly for your shoppe. In this case, we took a 9hr task down to 30 minutes by adding a few LF's... But there's nothing like just eye balling the log... Don in DC Home of the JAM 2004 OS/400, linux, websphere technical conference Oct. 29 www.wash-midrange.org/jam.html ----------------------------------------------------------------- On Wed, 25 Aug 2004, Mark Allen wrote: > Have a large job taking WAY longer than normal to run. Is there an easy way > to say copy job log to a PF and do something (write a pgm) to find how long > each step ran (using time of msg in job log). It's 100+ pages long so > scrolling by hand is NOT what I want to do. > > Mark Allen > IS Manager > Wilkes Telephone & Electric > 11 W. Court Street > Washington, GA 30673 > Phone: (706) 678-9565 > Cell: (706) 498-7907 > Fax: (706) 678-1000 >
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.
midrange.com
