With my experience with cluster, Issue REFRESH CLUSTER and wait. It
usually, works. MQ takes time to propagate the information.
Thanks,
AkBar E. Dar
The United Illuminating Company
New Haven, CT
Off: (203) 499-5981
Cell: (203) 623-9270
Potkay, Peter M
I am not duplicating the Queue Manger, rather we moving to a new machine.
Once New machine is imaged, I will turn off the other machine and configure
the same Queue Manager on the New machine with the information like Server
Name(CONNAME) and reset the Channel Sequence Number. Then run the
Hi:
We are moving One of our Queue Manager in the Cluster to a New Machine. I
have downloaded MS03 SupportPac(saveqmgr) to copy the Queue definitions and
amqoamd to copy over the Security information.
I am wondering that Is there way of creating the Channel and Cluster
information to a Script
Hi:
We have to move to new server where we have MQ SERIES loaded. In this move
I/P address is also going to change.
We have Two Queue Manger defined on this machine, and these Queue Managers
have Regular, Alias(part of a cluster), and Cluster Queue defined.
I would appreciate if you folks can
OK, I knew that I would forget the to mention the environment.
We are moving to new Windows NT machine.
And, By the Way, we have circular logging( I know the recovery is difficult
with it).
(Embedded image moved to file: pic25477.gif)
Akbar Dar
We are using WMQ 5.3 with CSD04.
We have four Queue Managers(3 on NT and one on AIX Unix) defined in a
Cluster environment. And, One of NT Queue Manger is connected to SAP via
R3 Link.
It works fine, but sometime, SAP cannot put a message on the R3 Link Queue
and we get a Reason Code 2085. In
We are using WMQ 5.3 with CSD04.
We have four Queue Managers(3 on NT and one on AIX Unix) defined in a
Cluster environment. And, One of NT Queue Manger is connected to SAP via
R3 Link.
It works fine, but sometime, SAP cannot put a message on the R3 Link Queue
and we get a Reason Code 2085. In
