On Tuesday 24 September 2002 15:56, Donaldson, Mark wrote:
> bpschedreq has a "predictive" output.  You could use it to find out what
> the scheduler thinks is going to happen over the next HH:MM hours...
>
> -M
>
> bpschedreq:
>    -terminate -jobid <jobid>
>    [-M <master_server,...,master_server>]
>    -tables
>    -read_stunits
>    -predict datetime [-L]
>       format for datetime is mm/dd/yyyy hh:mm:ss

>

I should clarify. I wasn't too clear. I need to know what WAS supposed to run 
YESTERDAY, in order to compare with what actally ran, today.


>
>
> -----Original Message-----
> From: Steven L. Sesar [mailto:ssesar AT rcn DOT com]
> Sent: Tuesday, September 24, 2002 1:38 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] what's SUPPOSED to run?
>
>
> I'm banging my head against the wall on this one.
>
> I'd like to write a script, which will report a summary of what was
> scheduled
> to run versus what actually happened.
>
> How do you glean what was SUPPOSED to run from NBU? I can parse through
> bpclsched, but that doesn't tell me how many jobs were scheduled to run.
>
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu