| Author |
Message
|
| martinatkins |
 Posted: Sat Dec 31, 2005 11:31 pm Post subject: runmqsc -w |
 |
|
Novice
Joined: 11 Jan 2004
Posts: 10
|
Can I use runmqsc from a WINNT platform against AS400
when I run
> RUNMQSC -w 60 MQ.DPMS2 <d:\util\dpms2.txt > d:\util\a2.txt
in the file dpms2 I have DISPLAY QLOCAL(MARTINAQ)
I am always timed out, what should I do |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sun Jan 01, 2006 8:26 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
a) Is your windows qmgr the default qmgr ?
b) Do you have a default path from your windows qmgr to the AS400 ?
c) do you have a default path from the AS400 to your windows qmgr ?
d) Is the MQ command server running on the AS400 qmgr
e) if type MVS 5.3 (no pcf support) you need the -x flag as well
| Code: |
| RUNMQSC -x -w 60 MQ.DPMS2 <d:\util\dpms2.txt > d:\util\a2.txt |
I sure hope your qmgr's name is "MQ.DPMS2" i.e. more than 4 chars...
If the answer is Yes to all 3 have you tried exchanging messages ?
See API exerciser for PUT1 with AS400 qmgr + queue ....
If all runs fine try a greater value for timeout...
Enjoy  |
|
| Back to top |
|
|
| martinatkins |
| Posted: Sun Jan 01, 2006 9:55 am Post subject: |
|
|
Novice
Joined: 11 Jan 2004
Posts: 10
|
WHAT DO YOU MEAN BY A DEFAULT PATH BETWEEN THE AS400 AND THE WINNT
When I run MQJExplorer ,when on the qmanager MQ.DPMS2 using the MQSC COMMAND display qmgr Iimmediately receive the display.
When I use this
RUNMQSC -x -w 60 MQ.DPMS2 <d:\eds\dpms1.txt > d:\eds\a2.txt
this is what I receive in a2.txt
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager MQ.DPMS2.
1 : DISPLAY QMGR
AMQ8416: MQSC timed out waiting for a response from the command server.
One MQSC command read.
0 command responses received.
Last edited by martinatkins on Sun Jan 01, 2006 12:04 pm; edited 1 time in total |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Sun Jan 01, 2006 11:26 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Quote: |
| I sure hope your qmgr's name is "MQ.DPMS2" i.e. more than 4 chars... |
Why? In fact they can only be 4 characters on z/OS. As far as I recall the only name length requirement for other platforms is that they are less than 48.
Is there a documented minimum length? |
|
| Back to top |
|
|
| EddieA |
| Posted: Sun Jan 01, 2006 3:20 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Are there any messages in the DLQ on MQ.DPMS2.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| martinatkins |
| Posted: Sun Jan 01, 2006 9:24 pm Post subject: |
|
|
Novice
Joined: 11 Jan 2004
Posts: 10
|
| EddieA wrote: |
Are there any messages in the DLQ on MQ.DPMS2.
Cheers, |
No |
|
| Back to top |
|
|
| EddieA |
| Posted: Mon Jan 02, 2006 12:39 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| WHAT DO YOU MEAN BY A DEFAULT PATH BETWEEN THE AS400 AND THE WINNT |
Usually, this would mean an XMITQ of the same name as the recieiving QMGR, tied to the correct Sender channel. Do you have this, in both directions. There are also other ways of doing this.
Does "normal" MQ communication between these QMs work correctly.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| martinatkins |
| Posted: Mon Jan 02, 2006 1:13 am Post subject: |
|
|
Novice
Joined: 11 Jan 2004
Posts: 10
|
| EddieA wrote: |
| Quote: |
| WHAT DO YOU MEAN BY A DEFAULT PATH BETWEEN THE AS400 AND THE WINNT |
Usually, this would mean an XMITQ of the same name as the recieiving QMGR, tied to the correct Sender channel. Do you have this, in both directions. There are also other ways of doing this.
Does "normal" MQ communication between these QMs work correctly.
Cheers, |
Yes to both questions as I mentioned earlier the same command from the same server works on MQJExplorer . |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jan 02, 2006 7:32 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Do you have a default xmitq defined on AS400 and is it empty ?
I would suggest against default xmitqs as the messages without a destination go there and do not hit the DLQ.
Enjoy  |
|
| Back to top |
|
|
| EddieA |
| Posted: Mon Jan 02, 2006 11:44 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| I mentioned earlier the same command from the same server works on MQJExplorer |
Except that, as far as I remember, MQJExplorer uses the same commection method as the MQ Supplied MMC Explorer. It opens a direct SVRCONN channel to the remote system, and does not use the local QM aa an imtermediate hop. All that proves is that the Command Server is running correctly at the remote end. It doesn't prove communication betwenn the 2 QMs involved in the "runmqsc" method of remote administration is working.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| martinatkins |
| Posted: Mon Jan 02, 2006 12:15 pm Post subject: |
|
|
Novice
Joined: 11 Jan 2004
Posts: 10
|
TWO QMGRS
MQ.NTTEST MQ.DPMS2
XMITQ MQ.DPMS2 MQ.NTTEST
SNDR MQ.NTTEST.DPMS2 DPMS2.MQ.NTTEST
RCVR DPMS2.MQ.NTTEST MQ.NTTEST.DPMS2
Maybe there is a service on the AS400 that I should start that isn't started? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jan 02, 2006 5:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The assumption is that your xmitqs are triggered and that the channel initiator is running...
Thanks
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| martinatkins |
| Posted: Mon Jan 02, 2006 9:40 pm Post subject: |
|
|
Novice
Joined: 11 Jan 2004
Posts: 10
|
| fjb_saper wrote: |
The assumption is that your xmitqs are triggered and that the channel initiator is running...
Thanks
|
Yes
SYSTEM.CHANNEL.INITQ
But if I run ( I don't know if I should)STRTMQMCHLI I get:-
Program cannot open queue manager object.
When I connect to a different QMGR all is well and when entering a mistake on purpose
DIS
1 : DIS
I of course receive AMQ8405: Syntax error detected ....
AMQ8426: Valid MQSC commands are: ...
When I do this on DPMS2 (as400) I do not receive any notification,
only
Starting MQSC for queue manager MQ.DPMS2
DIS
1 : DIS
maybe the service of runmqsc is not started on the server |
|
| Back to top |
|
|
| martinatkins |
| Posted: Tue Jan 03, 2006 3:30 am Post subject: |
|
|
Novice
Joined: 11 Jan 2004
Posts: 10
|
I have started to use M072 MQSC client When I use the MQMON .CFG file all is well but when I tried to use it without
D:\>mqsc -m MQ.DPMS2 -h HOSTNAME
Error connecting via client to 'MQ.DPMS2' RC(2035) Not authorized.
MQSC Ended
Even after reading
Posted: Wed Jul 06, 2005 5:51 am Post subject: MCAUSER question
I tried to use mqsc to connect remotely to QMGRs from Linux and Windows platform to a QMGR in Windows. The only difference between the 2 SVRCONN channels is that in channel "CLIENT" the MCAUSER has (testuser) and channel SYSTEM.ADMIN.SVRCONN has MCAUSER( ) which is blank and that supposed to allow connection request from any user. Why can I connect to qmgr via a channel with MCAUSER set to testuser and not when the MCAUSER is set to blank? Thank you.
mqsc -c CLIENT -m CRDA01 -h '172.123.75.19' Connected to Queue Manager 'CRDA01'
mqsc -c SYSTEM.ADMIN.SVRCONN -m CRDA01 -h "172.123.75.19" Error connecting via client to 'CRDA01' RC(2035) Not authorized
I still received RC(2035) Not authorized.
MQSC Ended
Is there any way around this or do I have to build each one in the MQMON.CFG |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jan 03, 2006 3:45 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
MCAUSER(' ') works as any user only in Java.
In C environments the user of the client app is supplied.
If this user does not have the requisite permissions in can be overriden by replacing it in the MCAUSER field.
There are some new features in 6.0 that allow you to pass the user on MQCONNX. check them out.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
