×
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 the help for QUPSMSGQ does say: "If the message queue is not a work
station message queue, it must be allocated by a job." However, it does
not specify what level of allocation.
I tried CHGMSGQ as a test. I used *NOTIFY. That does put an *EXCL lock
on it. This leads me to believe that the lock level should be ok. After
all, we all know that you can receive messages on a message queue you have
in *NOTIFY mode.
What else is different? The RCVMSG RMV(*NO) versus the IBM suggested
*YES?
Since I have multiple partitions let me try this experiment. I will start
some sessions on those lpars. Lock the message queue and see what
happens.
Result:
System utility power failed at 09/03/13 10:49:57.
System utility power restored at 09/03/13 10:50:11.
If that works ok, then I will abort the ups job on one lpar and see what
happens.
Result:
System utility power failed at 09/03/13 10:49:57.
System utility power restored at 09/03/13 10:50:11.
With the job running on a different lpar
Result:
Can't look at the message queue because of the lock. But the joblog does
indicate some action, just not my desired action.
I am going to assume my problem. I'll go from there...
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.