Re: QMHSNDPM again: How to display a message in the message line upon program end

Hello Joep,

Am 25.02.2021 um 15:20 schrieb Joep Beckeringh via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>:

Yes, it's trickier. Status messages go to *EXT, i.e. the status line of the terminal.

Basically that's what I want. My call already does this in a way, but the message doesn't stay. Why?

SNDPGMMSG MSGID(CPF9898) MSGF(QCPFMSG) MSGDTA('Cookie') TOPGMQ(*PRV)

in a CL program does exactly what I want, but *PRV isn't allowed as call stack entry parameter for the QMHSNDPM call. I maybe could exchange the API call with a QCMDEXC call, in turn calling SNDPGMMSG, but I don't want to invent a kludge I'd be carrying from program to program just because I'm apparently too dumb to understand what exactly I'm doing wrong.

I guess this mix of activation group boundaries vs. call stack vs. my general inexperience with API calls is something I need to attack in a more orderly way.

But honestly, I don't know where to start: I need to understand why the message is erased immediately. Is it a wrong call? Or another side effect?

Someone else privately hinted me to insert a DLYJOB before the program ends, but as the program is running, the keyboard is locked. And as soon as the program ends, the message ist gone again.

Completion messages go to whatever call stack entry you send it to; then it's up to that program to show it or not.

I'm not sure if I can count on qcmd to actually do this. :-)

In general I use call stack entry *CTLBDY with call stack count 0. That is mostly the program (or command line) where my program is called from. With a command line that is fine, most of the time.

Does not work for me.

But I also send completion messages to subfile programs with a message subfile. Then my messsage automatically ends up in the message subfile.

Since I can't change the calling program (qcmd), this isn't really an option.

:wq! PoC