You can do a DSPOBJD *ALL/*ALL *ALL to an outfile and then run a query
looking for objects that are damaged. Some times this bit isn't set, and
trying to Save the objects always works better (but not easy to save when
people have locks on the objects while they are using them), as those
objects that are damaged will fail to be saved.

When the system can be put into a restricted state, I would run a RCLSTG.

Pete

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mackie, Roger L.
(Precision Press)
Sent: Friday, October 12, 2007 9:52 AM
To: Midrange Systems Technical Discussion
Cc: Hughes, Alan (Precision Press)
Subject: Damaged objects after hard fall

Hi all.

Yesterday a cable came loose at the data center that hosts our System i
(iSeries 81) server. The server went down hard. After it came back up, a
damaged object kept item verification from working properly. This
morning, users are reporting other bizarre behavior on our system. With
our System i administrator out for several weeks, is there anything a
programmer can do to identify damaged objects while users are doing
their normal work?

Thanks in advance,
Roger Mackie


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2025 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.