Hi, Rob:

What specific object, library and object type have you ever had a
RCLSTG
fix?
Once a save flags an object as damaged, that's it. You have to
recreate
or restore from backup.

Now, I run a RCLSTG immediately prior to every save entire system and I
still have the full system save blow up because of damaged objects.
Some
are so darn common that I save them to save files first to check for
damaged objects

It's been many years since I saw such damage at a system level, but the one
that comes to mind as occurring more than once, is the QSYSOPR message queue
(back in the days of S/38, and it had to do with overflowing the 16MB size
limitation of that day).

At an application level, I have seen this more than once in recent years on
MQ objects. IBM's answer to those types of issues smells of M$ "support" :
"Can't you just restore them and stop bothering us?" is how it comes across.

But lately I'm not in that sort of operational environment, so if such
issues have been occurring for the past three years or so, I don't know
about them. What I do know is that if it's a system-level or other
IBM-supplied object, IBM should at least be made aware of it... and should
be asked to step you through finding the cause, then generating a solution.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"He who builds a better mousetrap these days runs into material shortages,
patent-infringement suits, work stoppages, collusive bidding, discount
discrimination - and taxes."
-- H.E. Martz


This thread ...

Replies:

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

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