After having been gone from my office for the last 8 months I returned to find 
NBU 3.2 has been upgraded to NBU 3.4 by my backup cohorts in crime. This is a 
good thing, however, in 3.2 I wrote a small script to extract data from the 
activity monitor data so I could keep running statistics on job elapsed time. 
It appears, under 3.4, that the numbers don't match up anymore. Has anyone else 
noticed this? Here's my example:

In the 3.4 Job Details screen for a particular job the following information is 
present:

Started: 07/02/2002 00:40:08
Elapsed: 00:01:05
Ended: 07/02/2002

This information is correct and what I need for my report.

What I see in the 3.4 Activity Monitor line for the same job is as follows:

Started: 07/01/2002 23:05:43
Elapsed: 01:35:30
Ended: 07/02/2002 00:41:13

Definitely not the same. It appears that the Activity Monitor includes within 
its Elapsed Time the time that the job was submitted and sat waiting in the 
queue. It seems to me that the queue time should be stored in a separate filed 
and the elapsed time should reflect the true time that the job actually ran 
under process.

Is this something that will be fixed or clarified in a future release? Perhaps 
4.5, which I will be migrating to sometime late this year or early next year?

This change sure has thrown my reporting off kilter.

Regards,
Dennis

Quote: "Time is not a test of the truth"
Translation: Just because you've always done it that way, doesn't make it right

Dennis F. Dwyer
Enterprise Storage Manager
Tampa Electric Company

(813) 225-5181  - Voice
(813) 275-3599  - FAX

Visit our corporate website at www.tecoenergy.com