|
First, I'd go with the solution on your last paragraph first. Second, We get a hard halt during our full system save if we encounter a damaged object, and deal with it accordingly. I'd check your backup to see how it could have been ignored in the past but yet caught this time. Sometimes objects are not recorded as damaged until the first save attempt of them. Prime example, we run a RCLSTG immediately prior to our full system save. However we still have been known to get hard halts due to damaged objects on that full system save. Some objects are so often damaged that we run a special save of that library to a save file immediately prior to the RCLSTG and blast the damaged objects. Therefore hints about doing a DSPOBJD to an output file and querying that for damaged objects may help, but will not catch those objects that only get that field updated with the next save. Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.