×
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.
Due to the lack of replies I thought I would try that test. Like Chuck
says, just because a test works once doesn't mean that's the gospel and
how it will consistently work.
I ran a program that was simply this:
SNDPGMMSG MSGID(CPF1816) MSGF(QCPFMSG) TOMSGQ(ROB/QUPSMSG)
Then I ran this other program:
DCL &MSGID *CHAR 7
ALCOBJ OBJ((ROB/QUPSMSG *MSGQ *EXCL))
RCVMSG MSGQ(ROB/QUPSMSG) WAIT(100) MSGID(&MSGID) RMV(*NO)
SNDMSG MSG(&MSGID) TOUSR(*REQUESTER)
ENDPGM
and it rapidly displayed CPF1816. Here I am thinking 'all well and good'
right? Wrong.
Run it again and it waits 100 seconds and sends a blank message. So I'm
thinking is there some internal job marker that marks a message as 'read'?
Sign off and sign back on, run the program again. Again it waits 100
seconds and sends blank message.
So now I am thinking it must mark the message 'read' in the message queue.
Which, upon reading the help on RMV(*NO), is pretty much the truth.
In summary, if I get a message after the timer expires but before I go
back into the RCVMSG wait it will work just fine and be received by the
RCVMSG. Good.
Rob Berendt
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
