BPDBJOBS - Output change after mp5

[AnotherAlan]

Morning,

I installed MP5 this morning on NB5.1.
When testing I noticed that the output from bpdbjobs is back-to-front. Or to put it another way, the active jobs are now listed at the top as opposed to the end.
Not a biggie, but it means scrolling up to see the running jobs. Anyone know if this can be changed?
I have had a look around but no joy I'm afraid.

Thanks
Alan

 

[Stumpr]

If you are using a UNIX master then you could use BPDBJOBS_COLDEFS entries in the bp.conf file.

Bob Stump
Just because the VERITAS documentation states something as certain, that does not make it a fact and that is truth.

 

[AnotherAlan]

Thanks Bob,

I am aware that you can change the entries in the bp.conf to update the format of the output in terms of order e.t.c., but cannot find any config to change the job order.

Since the upgrade my output is in reverse order, i.e. latest backups at the top.
As I said this is not my biggest problem, but the Ops are used to seeing active jobs at the bottom of the output and are complaining.

Thanks for your help though, much appreciated.
Alan

 

[Stumpr]

If you are using a UNIX master then you could use awk and sort. I guess I don't understand fully the problem since it seems you could use the column definitions and UNIX tools to output whatever format you desire.

Bob Stump
Just because the VERITAS documentation states something as certain, that does not make it a fact and that is truth.

 

[AnotherAlan]

Hi Bob,

You are of course correct. The output can be jiggled with at will, using the tools described.
The problem (even though it isn't one)is that in the previous version prior to mp5, bpdbjobs listed the jobs in date order, with the earliest backups at the top.
Our ops then just monitored the output via the command line rather than the gui. Now though the output is reversed, i.e. the latest jobs ( or active ones ) are listed at the top of the file. Therefore they need to scroll up (we have a load of jobs) to see which ones are active.
As I said this is no biggie, I was just curious as to why / how this happened and if there was a config change that could be made.
I have compared the config files with our previous version but cannot see any changes that would have done this.

I am not going to waste any more time with it, my guys will just have to adapt.
Alan
Thanks for your response though.