Damaged objects will not blow up a BRMS save. You really have to review
it to even realize there was a damaged object.
I am mulling over these special instructions
DSPLOGBRM PERIOD((hhmm mmddyy) (hhmm mmddyy)) OUTPUT(*PRINT)
where the time and dates span the entire save length
DSPSPLF FILE(QP1ALG) SPLNBR(*LAST)
Browse for "libraries saved". It should appear twice. First for the *IBM
save, then for the *ALLUSR save.
Record the number of libraries saved for *IBM ___________
Record the number of libraries saved for *ALLUSR _____________
Did you see any "partially saved"? __________
Then you should see messages like the following immediately after that
CPF3741 60 *FILE SYSIXADV in QSYS2 not saved.
CPF3763 60 *DTAQ JOBNOTIFY in library QGPL previously damaged.
CPF3763 60 *DTAQ IMWDDQ in library MKSIM previously damaged.
Record these into an email to Rob Berendt. The system name should be part
of the subject line.
Do a DSPJOB. Record the job name, number and user. Add that to the email
In the joblog I see:
Message . . . . : Damage found on file SYSIXADV in library QSYS2.
Cause . . . . . : The requested operation was not done for file SYSIXADV
library QSYS2 because of damage to the file. File SYSIXADV is either
damaged or destroyed. Recovery . . . : Delete and then create file
SYSIXADV again. Then try the request again.
Message . . . . : FILE SYSIXADV in QSYS2 not saved.
Message . . . . : 810 libraries saved, 3 partially saved, 0 not saved.
Message . . . . : 292 objects saved from QSYS2. 1 not saved.
How do I fix this?
Note: Had a drastic power failure Friday.
Also, is there something like DSPOBJD which will say if the object is
flagged for damage?