Could the messages have expired? In that case, they would show up in the
queue depth but wouldn't actually go away until you did the MQGET.
- Bruce
Giordano
Riyaz <[EMAIL PROTECTED]>
To:
[EMAIL PROTECTED]
Sent by: MQSeries List cc:
<[EMAIL PROTECTED]> Subject: Strange problem in
MQSeries
Thursday October 23, 2003 05:37 AM
Please respond to MQSeries List
Hi,
The problem -
Some messages were added to few queues in a Q manager using a COBOL
program.
The number of messages that were added was verified by issuing a MQINQ
call and checking the message count. The same number of messages could
be fetched using MQGET.
However after some time (say overnight), when an MQINQ is issued, the
message count returned is proper and corresponds to the number of
messages added. However if an MQGET is issued on the same queue
immediately after MQINQ, no messages are fetched and the MQGET fails
with 2033 (i.e. no messages available)! Simply put - the MQINQ
returns a proper message count but the MQGET says that no messages are
available.
This behaviour was not exhibited earlier.
The setup is MQSeries on OS/390.
What could be reason for this? Could it be because of any changes in
the way messages are stored (something to do with the storage classes
being changed)?
Thanks in advance,
Riyaz.
________________________________________________________________________
Want to chat instantly with your online friends? Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
