×
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.
Hi, James,
I always used something like this:
DCL VAR(&MSGTXT) TYPE(*CHAR) LEN(255)
/* send to message line ... */
SNDPGMMSG MSGID(CPF9898) MSGF(QSYS/QCPFMSG) + MSGDTA(&MSGTXT) TOPGMQ(*EXT) +
MSGTYPE(*STATUS)
And if I also want it to appear in the job log, I add this:
/* send message to job log ... */
SNDPGMMSG MSGID(CPF9898) MSGF(QSYS/QCPFMSG) +
MSGDTA(&MSGTXT) TOPGMQ(*PRV (*)) +
MSGTYPE(*DIAG)
Hope that helps,
Mark S. Waterbury
On Friday, August 21, 2020, 4:10:26 PM EDT, James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx> wrote:
I've got a CL program that runs in a terminal session, asks the user for
confirmation, and spawns off a batch job.
And I can never remember which combination of the myriad options on
SNDPGMMSG is the one that I'd use to put (depending on the user's
response to the confirmation screen) a "FROBOZZ job submitted" or
"Aborted" message on the message line.
I really ought to have a crib sheet for that.
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
