| Author |
Message
|
| DeepakDhiman |
 Posted: Thu Jan 31, 2013 4:28 am Post subject: MQ client 7.5 windows connection with MQ Server 7.5 Version |
 |
|
Newbie
Joined: 29 Jan 2013
Posts: 8
|
Testing with MQ Client 7.5 connection with MQ Server 7.5
Step on LINUX Server login with root
Creating the Queue Manager
./crtmqm QMSERVERCLIENT
Starte the Queue Manager
./strmqm QMSERVERCLIENT
Run the Queue Manager
./runmqsc QMSERVERCLIENT
Create the Local Queue for QMSERVERCLIENT Queue Manager
define qlocal(QSERVERCLIENT)
Create the new Channel on MQ Server for Server
DEFINE CHANNEL(SERVER.CLIENT.BIO) CHLTYPE(SVRCONN) TRPTYPE(TCP) DESCR('Server-connection to Client')
Create the new Channel on MQ Server for Client
DEFINE CHANNEL(SERVER.CLIENT.BIO) CHLTYPE(CLNTCONN) TRPTYPE(TCP) CONNAME(192.168.4.240)
QMNAME(QMSERVERCLIENT) DESCR('Client-connection to Server')
Set the Authentication for newly created channel
SET CHLAUTH(SERVER.CLIENT.BIO) TYPE(ADDRESSMAP) ADDRESS('192.168.8.111') MCAUSER('ddhiman')
ddhiman = client login user id on windows o/s
On command window of Windows XP (O/S)
Step
1. Copy the AMQCLCHL.TAB file from MQ Server to Client machine
Set the environment variable on current open command window
2. SET MQSERVER=SERVER.CLIENT.BIO/TCP/'192.168.4.240(1414)'
Set the environment variable on current open command window
3. SET MQCHLLIB=C:\IBMTAB
Folder name which contained the AMQCLCHL.TAB file
Set the environment variable on current open command window
4. SET MQCHLTAB=AMQCLCHL.TAB
RUN the following two different command to try test the connection establish with MQ Server from MQ Client ,
amqsputc QSERVERCLIENT QMSERVERCLIENT
amqscnxc -x 192.168.4.240(1414) -c SERVER.CLIENT.BIO QMSERVERCLIENT
but following ERROR generated… “MQRC_HOST_NOT_AVAILABLE”
reason code 2538
while host running, queue manager running, queue listener running |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Jan 31, 2013 4:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You don't need to set both MQSERVER and the MQCHL* variables, you should set either MQSERVER *or* MQCHLLIB and MQCHLTAB.
IF amqscnxc fails, that means you can't reach the network address of the queue manager. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jan 31, 2013 1:34 pm Post subject: Re: MQ client 7.5 windows connection with MQ Server 7.5 Vers |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| DeepakDhiman wrote: |
Testing with MQ Client 7.5 connection with MQ Server 7.5
Step on LINUX Server login with root |
Here might be your first error. If root is not part of your mqm group nothing will work correctly.
You should have used mqm .... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jan 31, 2013 1:36 pm Post subject: Re: MQ client 7.5 windows connection with MQ Server 7.5 Vers |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| fjb_saper wrote: |
| DeepakDhiman wrote: |
Testing with MQ Client 7.5 connection with MQ Server 7.5
Step on LINUX Server login with root |
Here might be your first error. If root is not part of your mqm group nothing will work correctly.
You should have used mqm .... |
has nothing to do with client connections. 
but, yes, generally one shouldn't run any kind of application program as root. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jan 31, 2013 1:39 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
I've seen the same type of error on a receiver channel (qmgr to qmgr) because the qmgr was started as root and root was not part of the mqm group, or maybe it was just the listener that was running as root...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jan 31, 2013 1:56 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| fjb_saper wrote: |
| I've seen the same type of error on a receiver channel (qmgr to qmgr) because the qmgr was started as root and root was not part of the mqm group, or maybe it was just the listener that was running as root... |
Yes.
But what was stated was that the *client side* was logged in as root.
Nothing was stated about the server. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Jan 31, 2013 2:12 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| Quote: |
| You don't need to set both MQSERVER and the MQCHL* variables, you should set either MQSERVER *or* MQCHLLIB and MQCHLTAB |
Correct, or don't specify them at all and mqclient.ini will indicate the default location of a channel table file, or code the app to use MQCONNX and specify the client connection details (as done by amqscnxc -x 192.168.4.240(1414) -c SERVER.CLIENT.BIO QMSERVERCLIENT).
_________________
Glenn |
|
| Back to top |
|
|
| DeepakDhiman |
| Posted: Fri Feb 01, 2013 3:01 am Post subject: |
|
|
Newbie
Joined: 29 Jan 2013
Posts: 8
|
SOLUTION 1:
You don't need to set both MQSERVER and the MQCHL* variables, you should set either MQSERVER *or* MQCHLLIB and MQCHLTAB
DEEPAKDHIMAN : tested it but not any impact on error message
SOLUTION 2:
Here might be your first error. If root is not part of your mqm group nothing will work correctly.
You should have used mqm ...
DEEPAKDHIMAN : I have a user deepak and root which is part of mqm group, tested with deepak user, but not any impact on error message
SOLUTION 3:
has nothing to do with client connections.
but, yes, generally one shouldn't run any kind of application program as root.
DEEPAK DHIMAN: used the deepak user of mqm group, but not any impact on error message
SOLUTION 4:
I've seen the same type of error on a receiver channel (qmgr to qmgr) because the qmgr was started as root and root was not part of the mqm group, or maybe it was just the listener that was running as root...
DEEPAK DHIMAN: Starting the Queue manager by deepak user who is part if mqm as well as deepak have the privileges of root too, listener that was running as deepak user . but not any impact on error message
SOLUTION 5:
Correct, or don't specify them at all and mqclient.ini will indicate the default location of a channel table file, or code the app to use MQCONNX and specify the client connection details (as done by amqscnxc -x 192.168.4.240(1416) -c deepak10 QMdeeepak10).
DEEPAK DHIMAN: my mqclient.ini file
#********************************************************************#
#* *#
#* <N_OCO_COPYRIGHT> *#
#* Licensed Materials - Property of IBM *#
#* *#
#* 63H9336 *#
#* (C) Copyright IBM Corporation 2011 *#
#* *#
#* <NOC_COPYRIGHT> *#
#* *#
#********************************************************************#
#***********************************************************************#
#* Module name : mqclient.ini *#
#* Type : WebSphere MQ client configuration file *#
#* Function : Define the client configuration *#
#* *#
#***********************************************************************#
TCP:
KeepAlive = Yes
ClientExitPath:
ExitsDefaultPath=/var/mqm/exits
ExitsDefaultPath64=/var/mqm/exits64
CHANNELS:
DefRecon=YES
ServerConnectionParms=deepak10/TCP/192.168.4.240(1416)
ERROR IS
C:\Documents and Settings\ddhiman>amqscnxc -x '192.168.4.240(1416)' -c deepak10
QMdeeepak10
Sample AMQSCNXC start
Connecting to queue manager QMdeeepak10
using the server connection channel deepak10
on connection name '192.168.4.240(1416)'.
MQCONNX ended with reason code 2538
reason code 2538 meaning is "MQRC_HOST_NOT_AVAILABLE" |
|
| Back to top |
|
|
| DeepakDhiman |
| Posted: Fri Feb 01, 2013 3:08 am Post subject: |
|
|
Newbie
Joined: 29 Jan 2013
Posts: 8
|
My mqm user detals on LINUX is
mqm:x:104:1000::var/mqm:/bin/false |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Feb 01, 2013 3:55 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Please post the output of dspmq on the server hosting the queue manager, thank you.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| DeepakDhiman |
| Posted: Fri Feb 01, 2013 4:58 am Post subject: |
|
|
Newbie
Joined: 29 Jan 2013
Posts: 8
|
deepak@linux240:/data/mpe3/IBM750/bin> ./dspmq
QMNAME(MGRMQ_TELSTRA) STATUS(Running)
QMNAME(QM_APPLE) STATUS(Running)
QMNAME(help) STATUS(Ended immediately)
QMNAME(QM_TELSTRA_SENDER) STATUS(Running)
QMNAME(QM_TELSTRA_RECEIVER) STATUS(Running)
QMNAME(QMLX12) STATUS(Running)
QMNAME(QMLX12O15) STATUS(Ended immediately)
QMNAME(QM_O15) STATUS(Running)
QMNAME(QMSERVERCLIENT) STATUS(Running)
QMNAME(QMSERVERCLIENT2) STATUS(Running)
QMNAME(QMdeepak) STATUS(Running)
QMNAME(QMdeepak2) STATUS(Running)
QMNAME(QMdeepak10) STATUS(Running)
deepak@linux240:/data/mpe3/IBM750/bin> |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Feb 01, 2013 5:06 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Can you telnet from the client machine to the queue manager IP and Port?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Feb 01, 2013 5:45 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
As you are attempting a client connection in V 7.5, have you made sure all the channel authorizations are in place, or disabled channel authorization checking?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| DeepakDhiman |
| Posted: Sun Feb 03, 2013 8:43 pm Post subject: |
|
|
Newbie
Joined: 29 Jan 2013
Posts: 8
|
Hi Grand,
Please tell/explain me the "channel authorizations are in place"
and If i made the disabled channel authorization then my code work ok but with enabled channel authorization, not working, display the error "reason code 2538 meaning is "MQRC_HOST_NOT_AVAILABLE"
 |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Feb 03, 2013 8:58 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9486
Location: US: west coast, almost. Otherwise, enroute.
|
on the 7.5 server qmgr use runmqsc to display the qmgr object, and post the results here
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
