× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I encounter this problem frequently after running debug and then
recompiling the program.  It's been going on since at least V5R1 (and
I'm on V5R3 now).

-reeve


On Wed, 26 Jan 2005 13:20:04 -0600, Dan Kimmel <dkimmel@xxxxxxxxxxx> wrote:
> MCH3601 is a corrupted pointer. Which probably means you wrote something
> else over part of the memory space that contained a pointer to a value you
> passed to Get_Random_DB_Record. Since you were using RPG that probably
> means the key or key list used on a chain operation. Remember, the key
> VALUE is not corrupted but the pointer to the key value is corrupted. This
> is usually kind of hard to do in RPG.
> 
> Dan
> 
> "Syaz" <syazwanh@xxxxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 01/26/2005 12:56 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> 
> To
> <midrange-l@xxxxxxxxxxxx>
> cc
> 
> Subject
> Error in Get_Random_DB_Record
> 
> 
> Hi,
> 
> I hit error MCH3601 at statement 179 from procedure Get_Random_DB_Record
> in
> module QRNXDBIO of service program QRNXIO.
> 
> Now, I have a CL program calling an RPG program (where all the logic is).
> It
> seems that when this error occured, the QRNXDB... kicked out from the RPG
> environment and the only error I get is from the CL call stack, making it
> impossible for me to track back which RPG line caused the error. There is
> no
> mention of my RPG program in the job call stack after the error ocurred.
> 
> Has anyone encountered this before?
> 
> Thanks and regards,
> Syaz
> 
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> 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@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> 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 thread ...

Replies:

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

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.