background: OS390 2.10 MQseries 5.2                                    
390 connects to 1 Windows 2000 MQSeries 5.2 box       
                          
We have a hot and a cold Windows 2000 box in case of problems.               
QMGR names are HDQMST1 and HDQMST2.           
We are not using clustering... and the w2k qmgrs will never be up at the same time.                           
                                                                       
So we are testing bringing up the COLD box and shutting down/killing the Hot box:
brought W2k box (HDQMST1) down ...and brought up HDQMST2.           
On 390, I stop my Sender channel to point to new IP address, and Change my remote queues
definitions to point to QMGR HDQMQST2.                                 
                                                                       
But before I get all my remote defs changed... messages come into 390   
qmgr and it reads the defs for the unchanged remote
queue and then the messages sit in the Channel.INITQ waiting for the channel to start.                                         
                                                                       
When all is well and HDQMST2 is up... I start the 390 Sender channel and it        
runs...but many messages end up on the DEAD LETTER QUEUE on HDQMST2    
...because they were looking for HDQMST1.                           
                                                                       
I hope you followed that.  My questions then is Does it work the way I 
am assuming? 
And if so, is there a way to get messages to reread the defs on the remote queue before being sent across? Would we really want to do this? 
And if we cannot do this then is there a real good reason why our HOT/COLD Windows 2000 QMGRs can't be the same name or
is there a better way to do the 390 remote queue definitions?               
 
Michael S. Lawrence
Systems Programmer
Atlas Van Lines
[EMAIL PROTECTED]
wk# (812) 424-4326 x2652
fax# (812) 421-7153

Reply via email to