Fw: Translation Problems with Compiler

Forwarded from a friend:


>Joe, I'm writing you cause I don't know who else to ask. The
>strangest thing happened this morning.
>
>We have a product in our department called CPT that we wrote the
>end of '99. I noticed a problem w/a report where it was printing the
>job name instead of the workstation id, so I was going to recompile
>it in my library and run a test. It wouldn't compile. I got a service
>dump and machine error MCH3203 (doesn't tell ya much - just that
>it failed). There were no errors on the compile listing - just said at
>the end that "an error occurred during translation".
>
>After much digging and trying everything I could think of, I noticed
>that further on down in the joblog there were other messages about
>QAQQINI in QUSRSYS. This is that thing I was running into problems
>with when some other  sql programs wouldn't compile after the V4R4
>upgrade. I don't know if you remember this or not, but I had to dup the
>QAQQINI from QSYS into QUSRSYS, and then we could compile.
>
>So, then I tried compiling my CPT701 program at V4R4 and guess
>what - it compiled. Only problem is, I don't want it at V4R4. All the
>other programs are at the previous release. I don't understand why
>I don't have a problem recompiling any of them - I tried and they
>compile just fine.
>
>Looks like, if we want *PRV for our compile version, that we need to
>have the previous version of QAQQINI in QUSRSYS. If we want to
>compile at V4R4, then we need the new QAQQINI in QUSRSYS. I'm
>not sure how we could/can handle this. Do we need to force our
>customer to V4R4? Do you have any idea why the other programs
>for CPT compile ok?


Has anyone run accross this same problem? Any hints where I
should look?

TIA,  Joe Teff

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