×
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:
Placing a message queue into *BREAK mode in your interactive or batch job,
or sitting on a RCVMSG instruction (or QMHRCVM API) will place a lock
(*EXCLRD, I think) that prevents other jobs from "updating" the queue. The
effect is the same from an outside standpoint, but it's not the same.
What you're saying is analogous to "ALCOBJ does the same things as OPEN on a
file." Well, yeah, to a point, I guess, but not the same.
Anyway, this approach has worked for me in the past. Pseudocode:
LOOP:
Receive message immediate
If message_received
Special processing
Goto loop
End-if
Sleep 30
Go to LOOP
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Computers are not intelligent. They only think they are.
I just made an interesting discovery:
If I have a CL program monitoring QSYSOPR for messages (using a RCVMSG
command), that message queue then behaves like the user message queue
of
a signed-on user, in that you can't delete QSYSOPR messages.
I don't suppose there's an easy way for a CL program running in a batch
job to monitor the QSYSOPR message queue without actually tying it up?
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
