What you want is rcdmqimg -m [QMGRName] -t all '*'
|---------+----------------------------------------------------------> | | "Raju, Arun - Contingent Staff" | | | <IMCEAEX-_O=BCBSA_OU=CHG_CN=RECIPIENTS_CN=ARAJU| | | @BCBSA.COM> | | | Sent by: MQSeries List | | | <[EMAIL PROTECTED]> | | | | | | | | | 09/27/2002 03:54 PM | | | Please respond to MQSeries List | | | | |---------+----------------------------------------------------------> >---------------------------------------------------------------------------------| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: Cancelling infinite MQGET wait | >---------------------------------------------------------------------------------| Need help with rcdmqimg.... rcdmqimg -m [QMGRName] -t all : gives out a syntactic error rcdmqimg -m [QMGRName] -t '*' : same goes for this one rcdmqimg -m [QMGRName] -t qmgr : works fine, but has information regarding the qmgr only... Have any of you used this to record the images of all objects. If not, is there any other utility that i could use in order to achieve this functionality. I know that BMC/SAVEQMGR does this, but any free external utility will help /// Thanks, Arun. -----Original Message----- From: Anupama Vaid [mailto:[EMAIL PROTECTED]] Sent: Friday, September 27, 2002 12:42 PM To: [EMAIL PROTECTED] Subject: Re: Cancelling infinite MQGET wait You are quite right and that is what I had figured. But I cannot understand how wait can continue if the queue handle that the thread is waiting on is CLOSED. This is what I was trying. In main thread, open a queue, create a thread and wait on same queue for messages. Now when it is time to close application, close queue from main thread and wait for new thread to exit. The new thread never exits! There are processes on different machines doing the same thing on the same queue. So can't post a message for shutdown because it may be received by any process. Or is there a way to post a message to specific MQClient? Thanks, Anupama -----Original Message----- From: David C. Partridge [mailto:[EMAIL PROTECTED]] Sent: Friday, September 27, 2002 10:40 AM To: [EMAIL PROTECTED] Subject: Re: Cancelling infinite MQGET wait That's because each connection to the qmgr is unique to the thread, therefore the closing of a queue on one thread is quite independent of anything on another. You need to satisfy the MQGET by putting a message to the queue. You could use a zero length message with the message type set to MQMT_REPORT and the Feedback set to MQFB_QUIT, or you could just send normal message with a predefined content to tell the application to quit. However as you say you have other processes reading from the queue this won't work ... Instead you'll need to change your code to do a get wait with a timeout in a loop and check some other flags when you exit the get with 2033 (in other words you'll need to poll). Polling is not good news but sometimes you've just got to do what you've got to do. Cheers Dave Partridge 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 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
