Trigger Default Path
Hello, On a UNIX platform, for a triggered application, is there a default path for the triggered application? Is it the default path where the trigger started the application from? Thanks for your help, John Dawson 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
Re: Need a utility to move messages from one queue to another.
Nastel's free MQControl Express is also a GUI which includes being able to move messages but none of these actually fit with the requirement of a long running background process: http://www.nastel.com/products/ap_wsadmin.html -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Beisher, Ethan Sent: 16 January 2004 16:48 To: [EMAIL PROTECTED] Subject: Re: Need a utility to move messages from one queue to another. CommerceQuest has a Windows freeware tool (that can connect via Client to any other platform) available that allows you to do this, as well as view and modify the MQMD. You can view the content of the messages in text, XML or Binary view. You can download it at http://www.commercequest.com/queuetoollogin01.asp Cheers, Ethan -Original Message- From: Larry Hendersen [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 9:57 AM Subject: Need a utility to move messages from one queue to another. I would like to move all messages from one queue to another. Is there a support pack that will do that? UNIX or Windows would be fine, or if the source is available any platform? I want the utility to not exit, but rather keep running and wait for more messages. _ Let the new MSN Premium Internet Software make the most of your high-speed experience. http://join.msn.com/?pgmarket=en-us&page=byoa/prem&ST=1 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
Re: How to back up authorites on Windows2000 MQ5.3
Use the amqoamd utility from a command line. amqoamd -m qmgr -s > qmgrauth.txt -Original Message- From: jan mecallon [mailto:[EMAIL PROTECTED] Sent: Friday, January 16, 2004 11:26 AM To: [EMAIL PROTECTED] Subject: How to back up authorites on Windows2000 MQ5.3 Hi all, The setmqaut commands get stored in SYSTEM.AUTH.DATA.QUEUE. How can I backup this queue in case I need to restore the access profiles? When I try to copy it to another queue or download it to a file using q.exe, I get 2042 object in useHow do the other people back up this queue? Thanks. Jan __ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus 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
Re: How to back up authorites on Windows2000 MQ5.3
Hi Jan, An easy way of backing up your OAM security settings is to use the following command: amqoamd -m QMgrName -s > oambackup.txt This will create a file called oambackup.txt with all of the OAM security settings in a setmqaut format. All you need to do is rename it from "txt" to "bat" and you can run it as is. Regards, Roger Lacroix Capitalware Inc. http://www.capitalware.biz Quoting jan mecallon <[EMAIL PROTECTED]>: > Hi all, > > The setmqaut commands get stored in > SYSTEM.AUTH.DATA.QUEUE. How can I backup this queue in > case I need to restore the access profiles? When I try > to copy it to another queue or download it to a file > using q.exe, I get 2042 object in useHow do the > other people back up this queue? > > Thanks. > > Jan > > > __ > Do you Yahoo!? > Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes > http://hotjobs.sweepstakes.yahoo.com/signingbonus > > 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
Grouping error on Z/OS (2)
Hi!, our application is running with MQ 5.3 Client on Windows and MQ 5.3 Server on Z/OS (it was install a couple days ago). We've this two errors: 1. When we're putting in group we get 2026 MQRC_MD_ERROR. 2. When we're getting in group we get 2256 MQRC_WRONG_GMO_VERSION. We prefered work with this error after the first one get fix. We know that segmentations isn't supported on MQ 5.3 for Z/OS. Also, we found in http://middleware.its.state.nc.us/middleware/Documentation/en_US/htm/csqzaw09/csqzaw091u.htm this: MQMD fields The following MQMD fields are largely concerned with message segmentation: GroupId MsgSeqNumber Offset MsgFlags OriginalLength If an application sets any of these MQMD fields to values other than their defaults, and then does a put() or get() on a queue manager which does not support these, the put() or get() will raise an MQException with MQRC_MD_ERROR. A successful put() or get() with such a queue manager will always leave the MQMD fields set to their default values. A grouped or segmented message should not normally be sent to a Java application that runs against a queue manager that does not support message grouping and segmentation. If a Java application attempts to get() a message from a queue manager which does not support these fields, and the physical message to be retrieved is part of a group of segmented message (that is, it has non-default values for the MQMD fields), it is retrieved without error. However, the MQMD fields in the MQMessage are not updated, the MQMessage format property is set to MQFMT_MD_EXTENSION, and the true message data is prefixed with an MQMDE structure that contains the values for the new fields. if the default value of MsgFlags is MQMF_NONE, I'm wondering if we assing MQMF_MSG_IN_GROUP and/or MQMF_LAST_MSG_IN_GROUP, those aren't the default values, is that the error?, however, I didn't find some documentation about programming grouping for Z/OS or neither grouping is supported or not(all the symptoms looks like it is not supported). We know MQ for Windows, AIX and Linux support segmentation and grouping, in those OSs, we ran our program succesfully (using a MQ client connected to a MQ Server). Thanks and regards, Luis Garro Muñoz Technical Support Services GBM de Costa Rica e-mail: [EMAIL PROTECTED] Tel: 2843999 ext 6216 JAVA Grouping.zip Description: Zip archive
How to back up authorites on Windows2000 MQ5.3
Hi all, The setmqaut commands get stored in SYSTEM.AUTH.DATA.QUEUE. How can I backup this queue in case I need to restore the access profiles? When I try to copy it to another queue or download it to a file using q.exe, I get 2042 object in useHow do the other people back up this queue? Thanks. Jan __ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus 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
Re: MQ 5.3 for Solaris9 ?
It is supported. http://www-306.ibm.com/software/integration/mqfamily/platforms/supported/wsm q_for_solaris_5_3.html -Original Message- From: Wesley Shaw [mailto:[EMAIL PROTECTED] Sent: Friday, January 16, 2004 12:15 PM To: [EMAIL PROTECTED] Subject: MQ 5.3 for Solaris9 ? The pdf link below states that MQ 5.3 is only available for Solaris 7 and 8. Does that infer its not approved to run on Solaris 9 ? http://www-306.ibm.com/software/integration/wmq/v53/g325-1985-01.pdf 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 This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. 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
MQ 5.3 for Solaris9 ?
The pdf link below states that MQ 5.3 is only available for Solaris 7 and 8. Does that infer its not approved to run on Solaris 9 ? http://www-306.ibm.com/software/integration/wmq/v53/g325-1985-01.pdf 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
Re: Need a utility to move messages from one queue to another.
CommerceQuest has a Windows freeware tool (that can connect via Client to any other platform) available that allows you to do this, as well as view and modify the MQMD. You can view the content of the messages in text, XML or Binary view. You can download it at http://www.commercequest.com/queuetoollogin01.asp Cheers, Ethan -Original Message- From: Larry Hendersen [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 9:57 AM Subject: Need a utility to move messages from one queue to another. I would like to move all messages from one queue to another. Is there a support pack that will do that? UNIX or Windows would be fine, or if the source is available any platform? I want the utility to not exit, but rather keep running and wait for more messages. _ Let the new MSN Premium Internet Software make the most of your high-speed experience. http://join.msn.com/?pgmarket=en-us&page=byoa/prem&ST=1 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
Re: Image backup of a Full Repository QM. Then a restore. Uh-oh
The REFRESH command does not accomplish what I need. I guess I will see what IBM says. I'll post there answer. Kumar gave me this idea. What do you guys think? 1.) Start the QM back up after the image restore. 2.) Alter the QM to be a partial repository. (Cluster now has only 1 full repository) 3.) Remove the QM from the cluster. 4.) Reintroduce the QM to the cluster as a full repository. Would reintroducing this QM again as a "new" full repository work, and cause the other full repository to push everything over? Or would I corrupt the cluster with duplicate entries for that QM, even though the QMID stayed the same? -Original Message- From: John Scott [mailto:[EMAIL PROTECTED] Sent: Friday, January 16, 2004 3:37 AM To: [EMAIL PROTECTED] Subject: Re: Image backup of a Full Repository QM. Then a restore. Uh-oh I hear what you are saying and your theory sounds fine, however, the Queue Manager Clusters manual in Chapter 7 says the following on recovering a Queue Manager: Recovering a queue manager To recover a queue manager in a cluster, restore the queue manager from a linear log. (See the WebSphere MQ System Administration Guide for details) If you have to restore from a point-in-time backup, issue the REFRESH CLUSTER command on the restored queue manager for all clusters in which the queue manager participates. There is no need to issue the REFRESH CLUSTER command on any other queue manager. So if yo do this and it does not work, then it would seem about the right time to call IBM support to find out why it doesn't work. Regards John Scott IBM Certified Specialist - MQSeries Argos Ltd -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: 15 January 2004 13:24 To: [EMAIL PROTECTED] Subject: Re: Image backup of a Full Repository QM. Then a restore. Uh-oh In the cluster manual, they do talk about fixing a QM that was restored from an image backup. But in the example, they only deal with a QM that was, is and will be a partial repository. The refresh command works fine in this case, since all it does it is PUSH out all its info to the full repositories, and then learns about other queues in the cluster on an as-need-to-know basis from the fulls. A full repository needs to PULL in info from the other full repository in this case, so that it knows everything. The problem I was having was that puts were failing because the QM did not know about the other new queues in the cluster, and being a full repository itself, it considered itself the definitive source. "If I don't know about, it must not be true!!!" It did not even bother checking with the other full. I don't see how issuing that command, even after making it a partial and using the repos yes option, would give me what I want. Consider a cluster with 1000 partial repositories and 2 full. If I made a new QM that is a partial and issued the REFRESH command, even with repos YES, that new QM would not suck in all the info for all 1000 QMs held in the full repositories. It would only push out its own info to the fulls. And it would only get new info on queues on those 1000 other QMs as it needed them. I need a particular QM (QM2FULL) to suck in ALL the info from another QM's full repository (QM1FULL). The refresh command does not do that. It pushes info our rather than pulling info in. Its almost as if I need a SYNC type command, to tell one QM to get all the Full repository info from another QM. I had hoped that QM2FULL would connect and sync with QM1FULL when I brought it back up, but it did not. I guess it almost makes sense that it didn't. Full repositories do not constantly talk to each other for no reason. They just update each other when there is new info to share. When QM2FULL was restored, QM1FULL just saw that event as his buddy coming back up, not a new QM that needed to be told everything. Since QM2FULL was the exact QM, why would QM1FULL need to push everything over again? How would QM1FULL know that QM2FULL was out of sync? Maybe QM1FULL was out of sync. And how would it even know how long it has been out of communication with its partner QM? Maybe it was only 1 second, or 1 week. These questions make me believe that the full repositories do not keep pulsing info back and forth. And why perhaps a "SYNC from QM1 to QM2" type command is needed for Full Repositories? -Original Message- From: John Scott [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 3:38 AM To: [EMAIL PROTECTED] Subject: Re: Image backup of a Full Repository QM. Then a restore. Uh-oh According to the command reference manual, REFRESH CLUSTER is not normally necessary unless: The queue manager has been restarted from an earlier point in time than it last finished, (for example, by restoring backed up data.) I assume that this command gets run on the qmgr you restored, not on the queue manager with the queue definitions. Regards John Scott IBM Certified Specialist - MQSeries Argo
Re: Grouping error on Z/OS
Hi!, thanks Doug for your answer. I know that in the attached code we didn't assign MQC.MQGMO_VERSION_2 to gmo, I forgot that. But, we already prove it assingning that, and it didn't work either. I'm wondering if message grouping has some special code lines for Z/OS, because our code already work well on other OSs. Thanks and regards, Luis Garro Muñoz Technical Support Services GBM de Costa Rica e-mail: [EMAIL PROTECTED] Tel: 2843999 ext 6216 (See attached file: Tested JAVA Grouping.zip) Tested JAVA Grouping.zip Description: Zip archive
Re: Grouping error on Z/OS
OS/390 doesn't support grouping until WMQ 5.3, and still :-( doesn't support segmentation. I *think* that earlier release of MQ on 390 don't support either V2 MD or V2 GMO Dave 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
Re: Grouping error on Z/OS
Luis, I can spell Java, but it looks like you are setting the MQMD version but not the MQGMO version. That is the one it is complaining about. Cheers Doug "Luis Garro Muôoz" To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> cc: Sent by: Subject: Grouping error on Z/OS MQSeries List <[EMAIL PROTECTED] EN.AC.AT> 01/16/2004 10:04 AM Please respond to MQSeries List Hi!, we've a MQ Series client on Windows 2000 connecting to a queue manager on Z/OS. We've a JAVA program (running on Windows) which puts and gets messages in group, this program works correctly connecting to AIX, other Windows or Linux queue managers, however if we run it connecting to Z/OS queue manager, we get error 2256 (MQRC_WRONG_GMO_VERSION) on getting (we're sure that we set version 2 to MQMD and GMO) and 2026 (MQRC_MD_ERROR) on putting. We know that segmentation is not supported on Z/OS MQ, but what about grouping?, all the symptoms looks like it is not. I attached our code, it's a little structured programming, but this is just for testing. Thanks and regards, Luis Garro Muñoz Technical Support Services GBM de Costa Rica e-mail: [EMAIL PROTECTED] Tel: 2843999 ext 6216 (See attached file: JAVA Grouping.zip)(See attached file: JAVA Grouping.zip) JAVA Grouping.zip Description: Zip archive
Grouping error on Z/OS
Hi!, we've a MQ Series client on Windows 2000 connecting to a queue manager on Z/OS. We've a JAVA program (running on Windows) which puts and gets messages in group, this program works correctly connecting to AIX, other Windows or Linux queue managers, however if we run it connecting to Z/OS queue manager, we get error 2256 (MQRC_WRONG_GMO_VERSION) on getting (we're sure that we set version 2 to MQMD and GMO) and 2026 (MQRC_MD_ERROR) on putting. We know that segmentation is not supported on Z/OS MQ, but what about grouping?, all the symptoms looks like it is not. I attached our code, it's a little structured programming, but this is just for testing. Thanks and regards, Luis Garro Muñoz Technical Support Services GBM de Costa Rica e-mail: [EMAIL PROTECTED] Tel: 2843999 ext 6216 (See attached file: JAVA Grouping.zip) JAVA Grouping.zip Description: Zip archive
Re: Use of multiple brokers/queue managers
Title: Message >Remember that WMQI is a pig Strange, I thought it was a (w)Bimbo :-)
Re: Use of multiple brokers/queue managers
Sorry I meant to say it restriction the excess load on the broker(s) server. Chris |-+> | | "Christopher D. | | | Fryett" | | | <[EMAIL PROTECTED]| | | T> | | | Sent by: | | | "MQSeries List" | | | <[EMAIL PROTECTED]| | | n.AC.AT> | | || | || | | 01/16/2004 08:17 | | | AM | | | Please respond to| | | "MQSeries List" | | || |-+> >--| | | | To: [EMAIL PROTECTED] | | cc: | | Subject: Re: Use of multiple brokers/queue managers | | | >--| Kulbir: There is nothing that will restrict you from having multiple brokers on a single server except resources on that server. What has been done in a company I am doing work at is to have client connections go through another server/qmgr so no clients will directly connect via the broker queue manager. This is using distributed and clustering queues. This elevates the load on that server and qmgr. Remember that WMQI is a pig, so you must allow for that on a server. IBM has some good performance documents for WMQI which may help you decide what type of server is required based on anticipated load. Hope this helps. Chris -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Kulbir S. Thind Sent: Friday, January 16, 2004 7:09 AM To: [EMAIL PROTECTED] Subject: Use of multiple brokers/queue managers Hi, On a single physical machine are there any advantages to using multiple MQSI brokers/queue managers other than Operational benefits. We need to connect approximately 300 MQServer installations to this one physical machine and will have messages of varying sizes being processed. What would be your recommendation and why? Thanks in advance, Kulbir. 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
Re: Use of multiple brokers/queue managers
Title: Message Kulbir: There is nothing that will restrict you from having multiple brokers on a single server except resources on that server. What has been done in a company I am doing work at is to have client connections go through another server/qmgr so no clients will directly connect via the broker queue manager. This is using distributed and clustering queues. This elevates the load on that server and qmgr. Remember that WMQI is a pig, so you must allow for that on a server. IBM has some good performance documents for WMQI which may help you decide what type of server is required based on anticipated load. Hope this helps. Chris -Original Message-From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Kulbir S. ThindSent: Friday, January 16, 2004 7:09 AMTo: [EMAIL PROTECTED]Subject: Use of multiple brokers/queue managersHi, On a single physical machine are there any advantages to using multiple MQSI brokers/queue managers other than Operational benefits. We need to connect approximately 300 MQServer installations to this one physical machine and will have messages of varying sizes being processed. What would be your recommendation and why? Thanks in advance, Kulbir.
Use of multiple brokers/queue managers
Hi, On a single physical machine are there any advantages to using multiple MQSI brokers/queue managers other than Operational benefits. We need to connect approximately 300 MQServer installations to this one physical machine and will have messages of varying sizes being processed. What would be your recommendation and why? Thanks in advance, Kulbir.
Stephen Lashinski/WBY/HLIFE is out of the office.
I will be out of the office starting 01/16/2004 and will not return until 01/20/2004. I will respond to your email when I return if it is necessary. * PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. * 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
Predefined XML - REQUIRED XML attributes
Iam using a pre defined XML which is created using a DTD.I've enabled the validation to occur in the input node.Now , I have an tag which has an attribute that is a required field, but I completely omit this attribute in the input message , it does'nt crib!Does'nt WMQI validate the XML attribute ? Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
Default values and TDS Fixed Width
Iam using the TDS format to model my output message which looks like HeaderDetail1Detail2 all fixed width and detail repeats.The header is defined as Fixed Width and the detail uses 'use data pattern'= .{length}I also have default value of space or zero assigned to all elements.It parses fine and I get the output message but the if I dont map a certain field in the detail , the default value is not taken!Is this a Bug, because if I dont map a certain field in the header it is correctly defaulted.
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
AMQ6150 MQSeries semaphore is busy
Hi all, On HP-UX MQ 5.2, I'm getting the following error. Please explain this error message and give the solution. AMQ6150: MQSeries semaphore is busy. EXPLANATION: MQSeries was unable to acquire a semaphore within the normal timeout period of 0 minutes. ACTION: MQSeries will continue to wait for access. If the situation does not resolve itself and you suspect that your system is locked then investigate the process which owns the semaphore. The PID of this process will be documented in the accompanying FFST. thanks karthik ** PLEASE NOTE: The above email address has recently changed from a previous naming standard -- if this does not match your records, please update them to use this new name in future email addressed to this individual. This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company ** 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
Re: Image backup of a Full Repository QM. Then a restore. Uh-oh
I hear what you are saying and your theory sounds fine, however, the Queue Manager Clusters manual in Chapter 7 says the following on recovering a Queue Manager: Recovering a queue manager To recover a queue manager in a cluster, restore the queue manager from a linear log. (See the WebSphere MQ System Administration Guide for details) If you have to restore from a point-in-time backup, issue the REFRESH CLUSTER command on the restored queue manager for all clusters in which the queue manager participates. There is no need to issue the REFRESH CLUSTER command on any other queue manager. So if yo do this and it does not work, then it would seem about the right time to call IBM support to find out why it doesn't work. Regards John Scott IBM Certified Specialist - MQSeries Argos Ltd -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: 15 January 2004 13:24 To: [EMAIL PROTECTED] Subject: Re: Image backup of a Full Repository QM. Then a restore. Uh-oh In the cluster manual, they do talk about fixing a QM that was restored from an image backup. But in the example, they only deal with a QM that was, is and will be a partial repository. The refresh command works fine in this case, since all it does it is PUSH out all its info to the full repositories, and then learns about other queues in the cluster on an as-need-to-know basis from the fulls. A full repository needs to PULL in info from the other full repository in this case, so that it knows everything. The problem I was having was that puts were failing because the QM did not know about the other new queues in the cluster, and being a full repository itself, it considered itself the definitive source. "If I don't know about, it must not be true!!!" It did not even bother checking with the other full. I don't see how issuing that command, even after making it a partial and using the repos yes option, would give me what I want. Consider a cluster with 1000 partial repositories and 2 full. If I made a new QM that is a partial and issued the REFRESH command, even with repos YES, that new QM would not suck in all the info for all 1000 QMs held in the full repositories. It would only push out its own info to the fulls. And it would only get new info on queues on those 1000 other QMs as it needed them. I need a particular QM (QM2FULL) to suck in ALL the info from another QM's full repository (QM1FULL). The refresh command does not do that. It pushes info our rather than pulling info in. Its almost as if I need a SYNC type command, to tell one QM to get all the Full repository info from another QM. I had hoped that QM2FULL would connect and sync with QM1FULL when I brought it back up, but it did not. I guess it almost makes sense that it didn't. Full repositories do not constantly talk to each other for no reason. They just update each other when there is new info to share. When QM2FULL was restored, QM1FULL just saw that event as his buddy coming back up, not a new QM that needed to be told everything. Since QM2FULL was the exact QM, why would QM1FULL need to push everything over again? How would QM1FULL know that QM2FULL was out of sync? Maybe QM1FULL was out of sync. And how would it even know how long it has been out of communication with its partner QM? Maybe it was only 1 second, or 1 week. These questions make me believe that the full repositories do not keep pulsing info back and forth. And why perhaps a "SYNC from QM1 to QM2" type command is needed for Full Repositories? -Original Message- From: John Scott [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 3:38 AM To: [EMAIL PROTECTED] Subject: Re: Image backup of a Full Repository QM. Then a restore. Uh-oh According to the command reference manual, REFRESH CLUSTER is not normally necessary unless: The queue manager has been restarted from an earlier point in time than it last finished, (for example, by restoring backed up data.) I assume that this command gets run on the qmgr you restored, not on the queue manager with the queue definitions. Regards John Scott IBM Certified Specialist - MQSeries Argos Ltd -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: 14 January 2004 20:45 To: [EMAIL PROTECTED] Subject: Image backup of a Full Repository QM. Then a restore. Uh-oh QM1FULL and QM2FULL are full repositories for CLUSTER1. QM3PART is a partial repository in CLUSTER1. All are on separate servers. Windows 2000 SP3 MQ 5.3 CSD04 On Day 1, full image backups are taken of all servers. On Days 2 and 3, new cluster queues are created on QM3PART. Both QM1FULL and QM2FULL see these as expected and all is working good. On Day 4, the server housing QM2FULL is restored from an image from Day 1, and QM2FULL is restarted. All the changes to QM3PART done since Day 1 are no longer reflected in QM2FULL's full repository. Puts to these new queues on QM2FULL are now failing with 2087. What is the right
