| Author |
Message
|
| tcganesh |
 Posted: Tue Sep 17, 2002 8:25 am Post subject: MQ Series Error AMQ6183,AMQ6119 |
 |
|
Novice
Joined: 12 Sep 2002
Posts: 13
Location: New York
|
Hi,
I am trying to do a MQ Prototype using Win2k and MQV5.2.1
I have define two QManagers PAC1 & PAC2
Local Queue in PAC1 is TLQ1
Transmit Q in PAC1 is PAC2(QM Name)
Remote Queue in PAC2 is TLQ1
Transmit Q in PAC2 is PAC1(QM Name)
Defined a Sender Channel in PAC1 as PAC1.PAC2, TCP/IP Protocol, Connection Name ABC1, Transmit Q as PAC1.
Defined a Receiver Channel in PAC2 as PAC1.PAC2, TCP/IP Protocol.
What I was trying was to send data from TLQ1 to TLQ1 between PAC1 and PAC2.
But when I start the Channel I receive following error.
I would Greatly appreciate any of your Suggestions and where I need changes or so.
Added the Error Log of MQSeries
THANKS IN ADVANCE
-------------------------------------------------------------------------------
09/17/02 07:04:53
AMQ6183: An internal MQSeries error has occurred.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 1272.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
09/17/02 07:04:54
AMQ6119: An internal MQSeries error has occurred (WinNT error 1352 from
LookupAccountSid.)
EXPLANATION:
MQSeries detected an unexpected error when calling the operating system. The
MQSeries error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
THANKS AGAIN,
GANESH C.
_________________
Thanks,
Ganesh C |
|
| Back to top |
|
 |
| vennela |
| Posted: Tue Sep 17, 2002 8:51 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
Defined a Sender Channel in PAC1 as PAC1.PAC2, TCP/IP Protocol, Connection Name ABC1, Transmit Q as PAC1.
|
You said your transmission Q on PAC1 is PAC2. Now when you define the sender channel PAC1.PAC2 you should give the Transmit Q as PAC2 (NOT PAC1).
Also you should define a localQ (for example QONPAC2) on PAC2 and define a remoteQ on PAC1 and point the localQ on PAC2 (QONPAC2) and the remote Q Manager. While defining the remoteQ u also have to give the transmission Q name
Like
Local Queue in PAC1 is TLQ1
Transmit Q in PAC1 is PAC2(QM Name)
Remote Queue in PAC1 is TLQ3 (Here you have to specify the Local QName that you define on PAC2 , TLQ2 when asked for and also the remote QMGR name PAC2 in your case)
Local Queue on PAC2 is TLQ2
Channels:
Sender on PAC1: TransmissionQ = PAC2
Now when you put a message on TLQ3 (on PAC1 ) it will end up on TLQ2(on PAC2).
---
Venny |
|
| Back to top |
|
|
| tcganesh |
| Posted: Wed Sep 18, 2002 11:12 am Post subject: Channel not starting |
|
|
Novice
Joined: 12 Sep 2002
Posts: 13
Location: New York
|
I did the above. Thanks for your input.
My Channel Status Stays in Binding (Never Starts).
What would be the issue.
One more Question?
I am trying to have Local Q at Source and Remote Q as target.
Is this valid or it should be vice versa.
Thanks
_________________
Thanks,
Ganesh C |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Sep 18, 2002 2:36 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
That is not what you should do. The source should have a RemoteQ definition of the LocalQ on target QMGR.
You said you were doing this on q Win2k right
1. Open MQSeries Explorer
2. Select the QMGRs tab and expand it
3. Select the Source QMGR PAC1 and expand it.
a. Right click on queues -> New -> Local Queue
Give a name say PAC2
Ste usage (last field) as Transmission : The default is Normal
b. Right click on queues -> New -> Remote Queue
Give a name say TLQ3
** Give the remote Queue Name (Third field from bottom) TLQ2 in ur case
Give the remote Queue Manager Name (Second from bottom) PAC2 in your case
Give the transmission Queue Name (last field) PAC2 in your case (This should be same as the name you have given in 3.a)
4. Select the Target QMGR PAC2 and expand it.
a. Right click on queues -> New -> Local Queue
Give a name say TLQ2 (This should be the name that you have given at 3.b ** line.
Now define a sender channel on the source and a reciever channel on the target. Both should have the SAME name.
Now try to put a message on the Remote Q defined on the source. It will end up in the QMGR2's local Q you have defined.
I know you are pretty confused with the naming conventions right now but eventually you will get used to it.
---
Venny |
|
| Back to top |
|
|
| jc_squire |
| Posted: Wed Sep 18, 2002 5:51 pm Post subject: |
|
|
Centurion
Joined: 14 Apr 2002
Posts: 105
Location: New Zealand
|
ganesh,
please note - if the queue managers are on the same server they need to accept incoming requests (channel connections) on different ports i.e. both queue manager can't accept connections on port 1414. if the port numbers are anything other than the default ensure that the port numbers are reflected in the conname field of the channel definition.
also double check that your listener is running and that you can establish a connection to the relevant ports e.g. telnet localhost 1414
you should also check the error logs in programfiles\mqseries\qmgrs\"qmgrname"\errors
Regards
_________________
J C Squire
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
| tcganesh |
| Posted: Thu Sep 19, 2002 3:21 pm Post subject: Thanks Both |
|
|
Novice
Joined: 12 Sep 2002
Posts: 13
Location: New York
|
Yes it worked perfectly.
I had 1414 for PAC1 and 1416 for PAC2.
Connection Name I gave was IP Address(Port Nbr) like 67.202.102.231(1416) is this right or we have any other naming convention.
Also Starting sender channel alone is fine?
Integration Rule is to keep the local queues closer to source and remote q's at the target. That's why I was trying other way around.
I am very glad this is a Starting Point I know I will come across lot more.
Thanks A Lot guys.
I greatly appreciate your help.
_________________
Thanks,
Ganesh C |
|
| Back to top |
|
|
| zubin_s |
| Posted: Mon Sep 23, 2002 2:41 pm Post subject: |
|
|
Newbie
Joined: 16 Sep 2002
Posts: 4
Location: SoCal
|
| For the connection name , try giving the System name(machine name) instead of the IP address , it works in some cases. |
|
| Back to top |
|
|
| jc_squire |
| Posted: Mon Sep 23, 2002 2:59 pm Post subject: |
|
|
Centurion
Joined: 14 Apr 2002
Posts: 105
Location: New Zealand
|
It will only work if the local host can resolve the remote hosts name to an IP address (DNS, WINS, etc), but name resolution is not the problem here as the name resolution process is being bypassed by specifying an IP address ........ therefore, it is not a solution to this problem ......
_________________
J C Squire
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
| zubin_s |
| Posted: Mon Sep 23, 2002 3:03 pm Post subject: |
|
|
Newbie
Joined: 16 Sep 2002
Posts: 4
Location: SoCal
|
| I didn't know both the QMs were on the same box. In this case, just start 2 diff listners listening to diff ports (say 1415 and 1416, assuming these ports are not being used by others) for the respective QMs and it should work fine. |
|
| Back to top |
|
|
| jc_squire |
| Posted: Mon Sep 23, 2002 3:31 pm Post subject: |
|
|
Centurion
Joined: 14 Apr 2002
Posts: 105
Location: New Zealand
|
from the previous posts it is evident that this is being done already ......
_________________
J C Squire
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
|
|
