Author |
Message
|
hughson |
Posted: Wed Jun 19, 2013 5:17 am Post subject: |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1959 Location: Bay of Plenty, New Zealand
|
hallmark wrote: |
AMQ6237: File '/MQTD/WMQ/QMGR1/data/QMGR1/qm.ini' missing. |
Is this true?
Cheers
Morag _________________ Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
Back to top |
|
 |
hallmark |
Posted: Wed Jun 19, 2013 5:55 am Post subject: |
|
|
 Voyager
Joined: 10 Mar 2005 Posts: 76
|
absolutely, because I haven't failed over the resource group which is the basis of this requirement  _________________ Rob |
|
Back to top |
|
 |
hughson |
Posted: Wed Jun 19, 2013 6:30 am Post subject: |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1959 Location: Bay of Plenty, New Zealand
|
OK - well thanks for trying that out, looks like the requirement you raised will need to be more than just documenting that env var! Can you add a comment in the RFE that you have tried this and what happened so we have the complete story in there.
Many Thanks
Morag _________________ Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
Back to top |
|
 |
zpat |
Posted: Wed Jun 19, 2013 6:33 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
You (IBM) can test this stuff out referring to any file path that does not exist!
It doesn't have to be a genuine HACMP filesystem. |
|
Back to top |
|
 |
hughson |
Posted: Wed Jun 19, 2013 6:36 am Post subject: |
|
|
 Padawan
Joined: 09 May 2013 Posts: 1959 Location: Bay of Plenty, New Zealand
|
zpat wrote: |
You (IBM) can test this stuff out referring to any file path that does not exist!
It doesn't have to be a genuine HACMP filesystem. |
I apologise that my answer was not accurate. I was informed this would do the trick and thought expediency was appropriate to pass it to the group.
I will try to be slower with my answers in future
Cheers
Morag _________________ Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
Back to top |
|
 |
hallmark |
Posted: Wed Jun 19, 2013 6:54 am Post subject: |
|
|
 Voyager
Joined: 10 Mar 2005 Posts: 76
|
Hi, no apologies necessary for me, I am happy to have a dialog and I appreciate the prompt responses,
thanks _________________ Rob |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Jun 19, 2013 9:17 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
One of the reasons it looks for the qm.ini file is because it needs it to find the location of the logs.
addmqinf does not specify any log location. But the qm.ini gets checked for the location of the logs and the logs get checked. So if you move the storage but forget to update the qm.ini with the new location of the storage you get an error upon running addmqinf... This is more geared towards the Multi-instance environment where your storage is shared than to the HA cluster where the storage is only on the active node. Hence the requirement to run it against an active node.... So maybe in future we will get a more relaxed way of running addmqinf...
So the way to fulfill your specific requirement would be to declare your storage as N A S and use the exact same mount points on both nodes. Now if you run the qmgr under an ldap id (ldap being shared by both nodes) you should be able to do your addmqinf without failing over...
Once the addmqinf has been run you can detach the N A S and make it a regular HA cluster resource. May be a little too much of a workaround... you be the judge!
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|