Re: Mysterious MCH3601 errors at V4R3M0

Robin wrote:
>Got a dump. PARM3 was not addressable. PARM1, PARM2 and PARM4 were
>addressable and contained the expected data.
>
>The exit program is evoked many times a day. The program stack should always
>be the same (it is when the program crashes - dont get the chance to observe
>it when it works (could put a DSPJOB into the exit program)). If a program
>in the stack has changed at the 6 week mark, how does that explain the
>intermittent failure?? The exit program should always be called in the same
>manner.

OK, your program uses PARM3 only to move the data to some other
field, which is then used to access the data.  So, there is a
very short window between when the program is called and that
MOVE happens.  If some other program is corrupting the stack,
you would only notice the problem if the corruption happens
during that short window.  When the corruption happens at
other times, you won't notice it.

The bug is not in the program that fails, but in some other
program that overwrites some storage it shouldn't.  Check the
compile dates of other programs in the application to try to
narrow down the list of suspects.

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---