Re: Pointer Error

I hate to say it but you have almost certainly already been given the correct answer.

It really doesn't matter what data you are writing or most anything else - a problem like this can really only arise under two circumstances.

1) Compiler or operating system error. Both highly unlikely.

2) Application problem causing a) Memory corruption or b) The "disappearance" of an ILE Activation Group (there are other possible OPM LR situations etc. but they normally only show up when the ILI/OPM mix is first introduced).

Causes.

2a) Program A defines parm as 10 long and passes to program B. B defines parm as 100 long and evals data to it - even if the data moved in is only 10 long the next 90 bytes are now blanks and any RPG compiler generated pointers etc. have just been blown away. This kind of scenario can have existed in the application for years and years (I saw one case when I worked on the COBOL compiler team that had been in the code for over 7 years) and the simple act of recompiling even without any changes can move the corruption from a "don't care" location (e.g. record buffer just prior to read) to one that matters e.g. _pointer_ to the record output buffer. Check all lengths of parameters along the _entire_ program chain. Not just the next one called - corruption could be 10 call levels out.

2b) Program A (OPM) calls Program B (ILE) which is in a *NEW activation group (or any AG that is destroyed prior to A calling B again). The pointer to B is resolved on first call, if the AG disappears then the second call will fail as there was nothing to tell A that it needed to re-resolve the pointer.

I believe that the OP said the error occurs on the write (not on a call) - in which case 2a is the only likely option. If the OP is convinced that that is not the case then it is time to call IBM support and send them the test case that causes it.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com