|
I hadn't chimed in on this topic, but here goes. Theoretically, a damaged object winds up with the "Damaged Object" flag in the object header set on. But sometimes that doesn't always work, because it's damaged, right? The two ways (neither one is fool proof, but in tandem they are pretty good) to find damage are a RCLSTG and a save option 21. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com "Walden H. Leverich" To: "'midrange-l@midrange.com'" <midrange-l@midrange.com> <WaldenL@TechSoftI cc: nc.com> Subject: RE: finding damaged objects Sent by: midrange-l-admin@m idrange.com 08/19/2002 02:19 PM Please respond to midrange-l Doesn't that just show the value of the flag on the object header? The system would have had to flag it as damaged already. I think a full save (or a save of the library/directory with the damaged object) should "find" new damage, unless of course the damage removed an object from a library, or the object wasn't in a library to begin with. I think a RCLSTG is the only fool-proof way. -Walden ------------ Walden H Leverich III President Tech Software (516) 627-3800 x11 (208) 692-3308 eFax WaldenL@TechSoftInc.com http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) -----Original Message----- From: coteijgeler@chello.nl [mailto:coteijgeler@chello.nl] Sent: Saturday, August 17, 2002 10:33 To: midrange-l@midrange.com Subject: Re: finding damaged objects Yes, it is called DSPOBJD. Direct the output of this comand to an outfile. One of the fields is "Object damaged?". Regards, Carel Teijgeler. On 17 Aug 2002 at 8:58, SANTOSH PRASAD wrote: > Is there an OS/400 command which lists all the damaged objects in the > machine? Santosh. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.