RE: STRDBG problem V5R2 on objects compiled for older release

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Walden H. Leverich III
>
> I'm glad to see there are others that agree that recompiling to "move" to
> production isn't a viable option.

Let me get this straight...

1. You compile a program to a previous release (absolutely necessary for
client support).

2. You move this program to another library, for whatever reason (promotion
from unit test to QA, for example).

3. You can no longer debug the program.  You must actually recompile the
program whenever you move it to a new library.

Is this what I'm hearing?  What is the rationale behind this behavior?  WHat
is actually occurring on the machine that causes it to "lose" its debug
information?

Reading between the lines, I get the idea that that this doesn't occur for
programs compiled on the current release.  Correct?  If so, why is this
action selective?

Joe