| Author |
Message
|
| bobc |
 Posted: Tue Jan 13, 2004 6:12 am Post subject: MQSeries on Tandem |
 |
|
Newbie
Joined: 13 Jan 2004
Posts: 3
Location: Brussels, Belgium
|
I want to install MQSeries on one Tandem. Does anyone know if it is possible for applications on another Tandem to access the Queue Manager processes of MQSeries if the 2 Tandems were connected with Expand?
Cheers
Bob  |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Tue Jan 13, 2004 7:55 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Could you be more specific as to what you wish to achieve.
Via Expand you should be able to access any process provided your userid is authorized to do so. But if you wish to access MQ executables you have to remember that your environment settings would be different on your local node and hence you may not be able to access the remote executables appropriately. It would be tedious process, but you may try and set up the environment to point to the remote system.
Cheers
Kumar |
|
| Back to top |
|
|
| martinsu |
| Posted: Mon May 03, 2004 5:35 am Post subject: |
|
|
Newbie
Joined: 20 Feb 2004
Posts: 6
|
Hi Bob,
I'm facing the same problem. Did you find any solution? |
|
| Back to top |
|
|
| bobc |
| Posted: Mon May 03, 2004 5:45 am Post subject: |
|
|
Newbie
Joined: 13 Jan 2004
Posts: 3
Location: Brussels, Belgium
|
| In the end we didn't try it - so no solution I'm afraid. |
|
| Back to top |
|
|
| mqonnet |
| Posted: Mon May 03, 2004 4:16 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Well, Let me repeat my previous post.
What exactly are you trying to do. As i asked earlier, the question is not clear. So, explain the scenario in detail and i can try and throw some more light.
Cheers
Kumar |
|
| Back to top |
|
|
| martinsu |
| Posted: Mon May 03, 2004 10:46 pm Post subject: |
|
|
Newbie
Joined: 20 Feb 2004
Posts: 6
|
Hi Kumar,
it's like described in the first message. We have two Tandem Hosts (one named \IDS , the other named \IF) that are connected via Expand, i.e. it is possible to write and read directly between the the two.
The MQ-Software (still Vers. 2) is installed and perfectly running on one of them (say \IF). Now we have an application on the second host (\IDS) which also should connect to MQ. But the MQCONN call aborts with
$DIANA BFSUT 120> run amqsget VIDSMQ02.TEST.QUEUE VIDSMQ02
$DIANA BFSUT 120..
Sample AMQSGET start
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- May 3 17:12:17 2004 |
| Host Name :- \IDS |
| PIDS :- 5697A17 |
| LVLS :- 221 |
| Product Long Name :- MQSeries Version 2 for TANDEM NSK |
| Vendor :- IBM |
| Probe Id :- ZT035000 |
| Application Name :- MQM |
| Component :- zutReadMachineIniFile |
| Build Date :- Oct 11 2000 |
| Exe File Name :- \IDS.$DIANA.BFSUT.AMQSGET |
| UserID :- IDS.SYSF |
| Process File Name :- \IDS.$Z40N:117915253 |
| Node number :- 211 |
| CPU :- 1 |
| PIN :- 475 |
| QueueManager :- VIDSMQ02 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- xecU_E_ATTR_NOT_FOUND |
| Probe Type :- MSGAMQ6118 |
| Probe severity :- Severity 2: error |
| Probe Description :- MQSeries was unable to open a message file. |
| Arith1 :- 276848709 (0x10806045) |
| |
+-----------------------------------------------------------------------------+
2004/05/03 17.12.18
MQSeries was unable to open a message file.
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- May 3 17:12:18 2004 |
| Host Name :- \IDS |
| PIDS :- 5697A17 |
| LVLS :- 221 |
| Product Long Name :- MQSeries Version 2 for TANDEM NSK |
| Vendor :- IBM |
| Probe Id :- XC001005 |
| Application Name :- MQM |
| Component :- xcsInitialize |
| Build Date :- Oct 11 2000 |
| Exe File Name :- \IDS.$DIANA.BFSUT.AMQSGET |
| UserID :- IDS.SYSF |
| Process File Name :- \IDS.$Z40N:117915253 |
| Node number :- 211 |
| CPU :- 1 |
| PIN :- 475 |
| QueueManager :- VIDSMQ02 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- lpiRC_CSPRC_UNEXPECTED_ERROR |
| Probe Type :- MSGAMQ6118 |
| Probe severity :- Severity 2: error |
| Probe Description :- MQSeries was unable to open a message file. |
| Arith1 :- 28743 (0x7047) |
| Comment1 :- Error reading machine ini file |
| |
| Comment2 :- |
| |
| |
+-----------------------------------------------------------------------------+
2004/05/03 17.12.18
MQSeries was unable to open a message file.
MQCONN ended with reason code 2058
ABENDED: $Z40N
CPU time: 0:00:00.278
Completion Code: 2058
$DIANA BFSUT 121>
I have copied the MQSINI file to the second host and set the environment MQMACHINEIFILE pointing the this but it does not change anything. Also I've weakened the file security of all INI- and Queuefiles of the QueueManager to allow access of anyone but it still does not work.
May be you have an idea now whats the problem (and may be how to solve it)
Cheers
Martin |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue May 04, 2004 6:14 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
First of all, i have never tried this myself as i did not deem it beneficial in any ways. Because if you wanted to access a qm from an application, you could as well copy that app onto the other node and access the qm. I do understand your organization may have node dependencies and most likely thats what you are talking about. But here's my take on this.
---From my understanding, you wouldnt be able to do this. Just copying the machinifile would not be enough. Because when you run an MQ app, it searches for the MQ executables in the vol.subvol that is defined in the machinifile. And i believe you cannot use node names while specifying the MQ executable locations. Which would mean, you could have local node's MQ executables path defined. And hence, your apps local to a particular node would always try and connect to the local qm. And thats what you are noticing here. If you see you are getting 2058.
---As for the FFST, it says that it was unable to open a message file. My bet again would be that you have the wrong params/env set up and hence MQ is unable to access the message catalogue file. Remember it is trying to access the message file on \IDS.
---Next FFST clearly tells you that there's something wrong with your env and the machinifile. When you said you modified the file and copied it accross to another node, what exactly did you do. Can you explain this part. Was there any changes made to this file???
---Expand is a facility provided by the Os and hence any applications that you develop may work over expand, but MQ most likely wont.
Cheers
Kumar |
|
| Back to top |
|
|
| martinsu |
| Posted: Fri May 07, 2004 5:07 am Post subject: |
|
|
Newbie
Joined: 20 Feb 2004
Posts: 6
|
Hi,
it seems that you are correct: this configuration doesn't work.
I tried to add the node name to the Vol.Subvol settings in the environment and in MQSINI. But MQ does not recognize this. It automaticcaly adds the local node name to its search path.
Thanks for your help. I think I will not waste any more time on this topic.
Greetings and thanks
Martin |
|
| Back to top |
|
|
|
|
