× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yes, it's trickier. Status messages go to *EXT, i.e. the status line of the terminal. Completion messages go to whatever call stack entry you send it to; then it's up to that program to show it or not.

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.

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

Joep Beckeringh


Op 25-2-2021 om 14:58 schreef Patrik Schindler:
Hello Joep,

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

A status message is shown while the program is running and disappears when the program is finished. What you want is a completion message (message type *COMP).
Thank you, but I tried this before. There's no (perceivable) output at all.

:wq! PoC


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.