|
I'm not sure exactly where to ask this, so I'm cross posting on Midrange-L and Domino-L. We are moving from one box running V5R2 to a new box runnning V5R4. We have done a backup on the old box and then restored on the new box, and we're now testing things out. My job is to test some Domino applications that use ODBC to get information from DB2/400, and I've run into something that seems strange. Straight SQL queries seem to work fine, but if I call a stored procedure and pass it a parameter, I get a MCH3602, "Pointer not valid for requested operation", error in the job running in QSYSWRK. The thing is, the first program (the once called from the Domino application) runs fine -- it accepts the parm, removes the null terminator and pads it with spaces, and then calls a CL program passing the cleaned version as a parm. The CL program then bombs the first time it tries to use that parm. The program was a CLP, and I discovered that if I compiled it as a CLLE (no code changes) it worked fine, and if I then compiled it as a CLP progam again it bombed. The CL program calls an RPG program, and the same thing happened -- the CLLE would call the RPG program fine, but the RPG program would bomb; when I converted the RPG to RPGLE and recompiled, it ran fine. I guess I can get everything to work by recompiling all the affected programs, but the whole thing seems very strange. Does anyone have any idea what might be going on, or if there's some other solution that doesn't involve recompiling everything? I'm a little worried that this might be a symptom of a bigger problem that I should be looking into . . . . Thanks very much, Mike Naughton Senior Programmer/Analyst Judd Wire, Inc. 124 Turnpike Road Turners Falls, MA 01376 413-863-4357 x444 mnaughton@xxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
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.