Mysterious MCH3601 errors at V4R3M0 -- MIDRANGE-L

First, apologies for the length of this positing.

I have a problem with mysterious crashes caused by MCH3601 (pointer not
set) in system programs.  I've been on to IBM's Solution Developer
Program Ask A Question site, but to little avail (they recommended a
PTF, we installed it, it changed nothing).  Before reporting it as an
error (which it undoubtedly is) I thought I'd see whether anyone else
had had it.

We are at V4R3M0.  The symptoms are as follows, and I'll quote the way I
originally reported it to the SDP.  Any thoughts greatly appreciated.


We have two problems with mysterious crashes in ILE RPG modules on a
V4R3 machine.  One looks like it is the problem that MF22101 purports to
resolve, but we have that PTF installed.

The text for MF22101 says,
"Message MCH3601 may be issued  during some database operations".  We
are getting that message when doing a WRITE to a file opened for update
in a program's entry-point module.  It does not happen if the file is
opened for output only.

MCH3601's from program/instruction details are:

stringEAOHighUse/000034.

In the second problem, the same message, MCH3601, is issued during a
CALLB to a module.  The module
cannot be stepped into in debug; the message is sent as soon as we press
F22.  My first reaction was that this was a parameter mismatch, but a)
the called module has not changed; b) the calling module's parameters
are set correctly, and c) it happens on more than one called module
anyway.  Also, the message RNX8001 is sent after MCH3601.

MCH3601's from/to program/instruction details are:

>From program . . . . . . . .  :   QRNXIE
>From library . . . . . . . . :     QSYS

>From module  . . . . . . . . :     QRNXINIT

>From procedure . . . . . . . :     _QRNX_SET_ModuleInfo
>From statement . . . . . . . :     4


To program . . . . . . . . . . : QRNXIE
To library . . . . . . . . . :     QSYS

To module  . . . . . . . . . :     QRNXINIT

To procedure . . . . . . . . :     _QRNX_SET_ModuleInfo
To statement . . . . . . . . :     4

This error only occurs when the called module is in a program or service
program which was
compiled at V4R3M0; if the called module is in a service program which
was created before the machine was upgraded to V4R3M0, it does not
happen.  I stress again, though, that the called module has not
changed.

I don't know that these two problems are actually linked,
but since the error message details are similar, and we started to
suffer from them at the same time (not long after going to V4R3), I
decided to
report them together.

Regards,

Martin.

--                                                                     
Martin McCallion                 
Midas-Kapiti International
Work:  mccallim@midas-kapiti.com
Home: martin.mccallion@ukonline.co.uk

Company policy says:
This email message is intended for the named recipient only.  It may be
privileged and/or confidential.  If you are not the intended named
recipient of this email then you should not copy it or use it for any
purpose, nor disclose its contents to any other person.  You should
contact Midas-Kapiti International as shown below so that we can take
appropriate action at no cost to yourself.

Midas-Kapiti International Ltd, 1 St George's Road, Wimbledon, London,
SW19 4DR, UK
Email: Postmaster@midas-kapiti.com Tel: +44 (0)208 879 1188 Fax: +44
(0)208 947 3373
Midas-Kapiti International Ltd is registered in England and Wales under
company no. 971479

.:. 
+---
| 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
+---