Bug in DSGetJobInfo DSJ.JOBELAPSED?

[cconley]

I think I have encountered a problem with the DSGetJobInfo function for the Elapsed Seconds (DSJ.JOBELAPSED). I have examples where a job starts before midnight and finishes after midnight and the function returns 0 seconds.

However, if i generate a job report with dsjob, it reflects the correct amount of seconds.

We are running version 7.5.1.A.

Has anyone else encountered this?

Thanks,

Chris

[kduke]

The elapsed time is based on after the SQL statement returns. This changes the rows per second number. I know, weird.