Folks, perhaps this will help. The article is for V6R1, V7R1, V7R2.
Can't imagine why it wouldn't work at V7R3, V7R4.
Just putting it out there as an attempt to help.
If it's used, let me know if it worked.....

https://www.ibm.com/support/pages/damage-detection-tool


Very Respectfully,
Michael Mayer
IBM I on Power System Admin.
IT Operations.
The Florida Bar
651 E. Jefferson St
Tallahassee, Florida 32399-2300
mmayer@xxxxxxxxxxxxxx
https://www.floridabar.org
Office: 850.561.5761
Cell: 518.641.8906


Today's Topics:

1. RE: BRMS damaged object (Rob Berendt)
2. RE: BRMS damaged object (Steve Pavlichek)
3. RE: BRMS damaged object (Rob Berendt)


----------------------------------------------------------------------

message: 1
date: Fri, 21 May 2021 12:44:37 +0000
from: Rob Berendt <rob@xxxxxxxxx>
subject: RE: BRMS damaged object

Are you doing the DSPOBJD before, or after, the save?
Some years back we were having full system saves crash on certain Management Central objects. They were frequently getting damaged. We tried to check prior to the save by DSPOBJD, etc. However that damaged flag is not set until the object is tried to be saved. We got to the point of saving them to a save file prior to the full system save. If they were damaged we would delete them. Then we would proceed with the full system save. We had to do this for years, through multiple OS upgrades. IBM disavowed this was happening for a long time but they eventually got it fixed.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steve Pavlichek
Sent: Friday, May 21, 2021 8:14 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: BRMS damaged object

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


How do I determine if a file is damaged?

Customer is using the Full System Flash Copy Toolkit and their backup is failing on a large file with CPF3285 "Damage found on file F4111 in library PRODDTA". What command would show that the file is damaged? I've tried the steps in the IBM support page with DSPOBJD to an outfile but the results do not show the object as being damaged. I also ran CRTDUPOBJ on the file and it completed successfully.

I'm trying to determine if the file is getting damaged during the flash copy of if their production file is already damaged.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com


------------------------------

message: 2
date: Fri, 21 May 2021 13:38:31 +0000
from: Steve Pavlichek <spavlichek@xxxxxxxxxxx>
subject: RE: BRMS damaged object

I ran the DSPOBJD before and after the save. BRMS still thinks the file is damaged but I can not find any way to verify that.

Herman, VIOS is 2.2.5 and this is a new issue with this file.
Yes, that VIOS is old but we are migrating the customer to a new POWER9 so no need to upgrade it.

From: Rob Berendt<mailto:rob@xxxxxxxxx>
Sent: Friday, May 21, 2021 8:44 AM
To: Midrange Systems Technical Discussion<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: BRMS damaged object

Are you doing the DSPOBJD before, or after, the save?
Some years back we were having full system saves crash on certain Management Central objects. They were frequently getting damaged. We tried to check prior to the save by DSPOBJD, etc. However that damaged flag is not set until the object is tried to be saved. We got to the point of saving them to a save file prior to the full system save. If they were damaged we would delete them. Then we would proceed with the full system save. We had to do this for years, through multiple OS upgrades. IBM disavowed this was happening for a long time but they eventually got it fixed.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dekko.com%2F&amp;data=04%7C01%7C%7Ca65b772453c744c989c708d91c5639d4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637571978924486909%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=8yJFETq2Etu3hdL2W5PhyNckI4ZOzqLu7vXLujY39DI%3D&amp;reserved=0




------------------------------

message: 3
date: Fri, 21 May 2021 14:01:13 +0000
from: Rob Berendt <rob@xxxxxxxxx>
subject: RE: BRMS damaged object

If you're doing a DSPOBJD to an outfile and the column ODOBDM is not showing any damage for that object then I would open a case with IBM. You'd better hope it's not VIOS because they're pretty adamant about not supporting obsolete releases. I recently had a most unpleasant experience with this on an unrelated issue with VIOS.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steve Pavlichek
Sent: Friday, May 21, 2021 9:39 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: BRMS damaged object

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.


I ran the DSPOBJD before and after the save. BRMS still thinks the file is damaged but I can not find any way to verify that.

Herman, VIOS is 2.2.5 and this is a new issue with this file.
Yes, that VIOS is old but we are migrating the customer to a new POWER9 so no need to upgrade it.

From: Rob Berendt<mailto:rob@xxxxxxxxx>
Sent: Friday, May 21, 2021 8:44 AM
To: Midrange Systems Technical Discussion<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: BRMS damaged object

Are you doing the DSPOBJD before, or after, the save?
Some years back we were having full system saves crash on certain Management Central objects. They were frequently getting damaged. We tried to check prior to the save by DSPOBJD, etc. However that damaged flag is not set until the object is tried to be saved. We got to the point of saving them to a save file prior to the full system save. If they were damaged we would delete them. Then we would proceed with the full system save. We had to do this for years, through multiple OS upgrades. IBM disavowed this was happening for a long time but they eventually got it fixed.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dekko.com%2F&amp;data=04%7C01%7C%7Ca65b772453c744c989c708d91c5639d4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637571978924486909%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=8yJFETq2Etu3hdL2W5PhyNckI4ZOzqLu7vXLujY39DI%3D&amp;reserved=0


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com


------------------------------

Subject: Digest Footer

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


------------------------------

End of MIDRANGE-L Digest, Vol 20, Issue 710
*******************************************

________________________________
Please note: Florida has very broad public records laws. Many written communications to or from The Florida Bar regarding Bar business may be considered public records, which must be made available to anyone upon request. Your e-mail communications may therefore be subject to public disclosure.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.