BRMS reporting damaged objects after a backup
When BRMS encounters a damaged object, it skips the remaing libraries and goes to the DLO. Where in BRMS can you check to see what libraries have been skipped?
Software/Hardware used:
i5 AS400 V5R4 570
Software/Hardware used:
i5 AS400 V5R4 570
ASKED:
June 20, 2011 8:37 PM
UPDATED:
July 1, 2011 5:46 AM
Answer Wiki:
Why not just go to your log and find what damaged object and in what library and troubleshoot the problem?
To see all answers submitted to the Answer Wiki: View Answer History.
Have you tried DSPLOGBRM ?
Yes, the DSPLOGBRM was used. It will show the damaged object(s) but WILL NOT show the libraries that were skipped.
Maybe try GO BACKUP. Use option 10 (Setup Backup) and again 10 (Change Backup Library List). This will show a list of all libs and their Last Save Date.
Another possibility.
DSPOBJD OBJ(QSYS/*ALL)
OBJTYPE(*LIB)
OUTPUT(*OUTFILE)
OUTFILE(QTEMP/LIBS)
From the resulting file you can extract the names of the libraries based on save date and so on.
You didn’t read the question. I said when BRMS hits a damaged object in a library the backup skips any remaining libraries to back up and goes to the DLO. The BRMS log will tell me what the damaged object it, but not the remaining libraries it did not backup. Why is it skipping any remaining libraries after hitting a damaged object?
I don’t use BRMS, so I don’t know an answer. Does DSPLOGBRM tell you which libraries were backed up? If it does, then the libraries that weren’t backed up are of the ones that were requested but that aren’t listed. If BRMS can’t list what was backed up, I don’t see much reason to use it.
And if it does tell you what was backed up, I’m not sure what the difficulty is.
I’d guess that the remaining libraries weren’t backed up because the save operation threw an exception that terminated the process. I don’t have damaged opbjects to test, so I can’t be sure. I suspect that SAVLIB (or the related API) terminates when damage causes an exception.
Tom