Re: Struggling to understand QMHSNDPM API

Hello Bruce,

Am 30.01.2020 um 01:55 schrieb Bruce Vining <bruce.vining@xxxxxxxxx>:

Oh that first call corrupted your activation group, you just didn't become
aware of it until later. By replacing the first four bytes of ErrCode with
x'00000000' you told the API to return any error as an *ESCAPE message.

Oh. Okay.

NOT setting it to x'00000000' told the API to return any message
replacement data to your ErrCode structure starting at byte offset 17 (base
1). Whatever was really at that storage location just got over written...

Now I know that even in RPG it's possible to shoot yourself in the foot. I was thinking this is most easily possible with C. :-)

I put together a presentation years ago on message handling and it covered,
among other things, how to use a subfile along with QMHSNDPM. If/when I
find it I'll send it to you offline.

Thanks!

Now, after disabling ERRSFL in the DSPF and prevent a WRITE to the DSPF after the API call, the message stays, as desired. Now I'm even more confused how to cope with ERRSFL being incompatible with the implicit message line. Changes are reflected in the files on the web server.

Any hints are greatly appreciated!

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc