RE: QMSHNDPM API

[Scott Klement <klemscot@xxxxxxxxxxxx>]

Send a *STATUS message to make the message display while the program is
running.  That's what it's for, the status of the program.

If you want it to appear after the program ends, also send a *COMP
("completion") message.

If you want the program to "end in error" send an *ESCAPE message.

Personally, I have a service program that I use to send these messages,
so when I need a status message, I just do:

                  callp    util_status('Checking inventory...')

or
                  callp    util_escape(3: 'Fatal Error: CUSTMAS ' +
                              'file not found!')

(For escape, comp, etc, messages I pass the number of call stack entries
to send the message back to, in addition to the message itself)


On Fri, 22 Feb 2002, Chris Devous wrote:

> So close, and yet so far away....
>
> This works, but the message vanishes the minute the program returns.
>
> If I use a cl to call the RPGLE (which calls the API), and put a DLYJOB DLY(5)
> immediately after the call to the RPGLE, then the message hangs around for 
>five
> seconds and disappears....
>
> If I then do my SNDPGMMSG "My message", my message appears on the status
> line, and stays there, even after the CL program returns.
>
> Is there a way to make the *Status message "sticky"?
>
> --Chris
>