We have faced a strange issue during automation script development and would like to ask for your assitance. We are trying to collect the statistic data for job types 22 and 28. When we gather statistic using bpdbjobs.exe and bpimagelist.exe we get multiple jobs of type 28 with the same ID but different snapshot ID. At the same time, OPScenter shows only one job of this type. Given all the above, I have a couple of questions and hope you can help me with the answers:
1. Could you please give us more details on how this job type is being produced and why we see this inconsitancy between cli commands and OPScenter?
2. How are these job types are connected?
You can match the backup id in both sets of output:
TNs explaining the fields:
this doc has the job types:
your text file has a first job 801470 which appears to be a parent job (because the parent job id for this job is itself, i.e. 801470)...
...and then we see several child jobs which have job 801471 as their parent job...
...but... you don't include job 801471 in your list...
...and my guess is that job 801471 was a child job of 801470.
The data of bpdbjobs is very structured and I have always found it to be 100% consistent. Sometimes it just takes a bit of time, and a bit of code, to work out how it all ties together.
Notably the "try list" embedded within each record as a data-structure of varying size from any one job to another. I can promise you that there is a definitive structure to it.