RE: Re: QMHRCVM bug in 440?

Œ
Hello Buck,

(Copied to the list for archiving purposes)

I did a quick conversion of my sample to RPG IV and ran it.  The "problem" is 
that RPG 
III sends an impromptu message (no message identifier) and RPG IV sends a 
pre-defined 
message (RNI5344).  While the external behaviour is similar, the internal 
behaviour is 
very different.  Although I think there is a case for saying that Toronto broke 
DSPLY I 
doubt they'll fix it at this stage.

The good news is that I have a solution for you!  Firstly some background.

The RCVM0100 format of QMHRCVM returns the substitution text OR the impromptu 
message 
text.  They are two different things.  So in your case the API is doing what it 
was 
designed to do since RPG III and RPG IV handle DSPLY differently.  

The reason the RCVMSG command seems to behave differently is that I'd bet you 
are using 
the MSG parameter to return the message text.  MSG gives you back the formatted 
first 
level text including any substitution data.  That is different from the API 
behaviour 
with format RCVM0100.  

The solution is to use format RCVM0200 which returns the substitution data AND 
the 
formatted message text.

I held my tongue regarding using DSPLY.  It is an awful technique for 
production code and 
I think your intention to replace it with real message handling is the proper 
approach.

Regards,
Simon Coulter.

«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
«» FlyByNight Software         AS/400 Technical Specialists       «»
«» Eclipse the competition - run your business on an IBM AS/400.  «»
«»                                                                «»
«» Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           «»
«» Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      «»
«»                                                                «»
«» Windoze should not be open at Warp speed.                      «»
«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
+---
| 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
+---