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.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.