Paul

The hung job that you see is a known problem that Aptare has already
identified and fixed.  The fix will be in an upcoming patch I believe. 

Monte

-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Paul
Keating
Sent: Friday, August 11, 2006 8:30 AM
To: Ed Wilts
Cc: Greenberg, Katherine A; veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Aptare vs. NB 6.0 NOM reporting

I submit my sincerest apologies.

I just searched through the interface to find the Command Center
Dashboard.
You are, in fact, correct.

Hmmm....it does seem however that there is one job from 2 nights ago,
showing up in the CCD, as slow, running >=12 hours, and possibly "hung",
however in Activity monitor, it's reported as 100% complete, status 0.

Hmmm.

Other than that...looks great....built in intelligence for our Ops
staff.

Again, my apologies......too bad I haven't had the time to invest in the
tool.

Paul


-- 


> -----Original Message-----
> From: Ed Wilts [mailto:ewilts at ewilts.org] 
> Sent: August 11, 2006 11:04 AM
> To: Paul Keating
> Cc: Greenberg, Katherine A; veritas-bu at mailman.eng.auburn.edu
> Subject: Re: [Veritas-bu] Aptare vs. NB 6.0 NOM reporting
> 
> This statement is absolutely false.  Bringing up the Command Center
> Dashboard, I can see the status of all of the running jobs - jobs that
> are long-running are flagged with a little clock.  Jobs that 
> are running
> slowly are flagged (I forget the symbol for that - might be a snail).
> Both of those cases have the job details flagged in red 
> versus the blue
> for the normal jobs.  All jobs include KB, KB/sec, elapsed 
> time, and the
> time data was last written for th job.  The real-time job 
> summary gives
> me the number of active jobs, queued jobs, completed jobs, etc.