| Author |
Message
|
| ucbus1 |
 Posted: Fri Aug 06, 2004 7:58 am Post subject: Errors with FAT client |
 |
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
I have a FAT client on 2K that connects to the old configuration fine. now I have added a new configuration, I have copied the new MQWFCHLTAB file from the server to the 2k machine. I am getting an error "connection failed"
I looked in the errors and it says that
AMQ9516: File Error occurred
The fike ssytem returned errror code 1001 for file AMQRFCDA.DAT
When I reverted back to the old MQWFCHLTAB file and tired to connect to the old configuration, it worked fine though.
Please let me know |
|
| Back to top |
|
 |
| vennela |
| Posted: Fri Aug 06, 2004 9:11 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
After copying the new channel tab are you trying to connect to the old server or the new server or both?
Did you run fmczccd with the new channel tab? What is the output
You can build your own channel table that can connect to multiple servers. Look at the MQSeries client manual or do some search on this site on building a channel table. |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Fri Aug 06, 2004 10:13 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Thanks Vennela,
I ran fmczccd with channel tab file pointing to the channel tab file I have copied from server (AIX) when my old configuration was created.
| Quote: |
The channel table in the profile is: C:\program files\mqseries workflow\chltabs\
old.TAB
The connect name found in the profile : FMC.FMCGRP.FMCSYS,FMCQM
The channel table exists.
The current user has read access to channel table file.
The channel table contains the following information:
Queue manager : FMCQM
Protocol : TCP/IP
Connection name : xx.xx.x.xxx(xxxx)
TCP/IP-addr : xx.xx.x.xxx
TCP-Port : xxxx
Status : ok
---------------
You are using the MQSeries Client API for the queue manager communication.
Checking system identifier FMC.FMCGRP.FMCSYS,FMCQM .
Ping to server xx.xx.x.xxx was successful.
Connecting to the queue manager FMCQM was successful.
There are no checks with this utility to verify that the MQSeries Workflow Server is
running on your server. |
Now I have created a client pointing it to the new channel tab file ( that includeds new configuration) I have copied from Server (aix) node)
| Quote: |
C:\Documents and Settings\db2admin>fmczccd -y NEW
The channel table in the profile is: C:\program files\mqseries workflow\chltabs\new.TAB
The connect name found in the profile : FMC.FMCGRP1.FMCSYS1,FMCQM1
The channel table exists.
The current user has read access to channel table file.
The specified module could not be found. |
Is some thing wrong |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Aug 06, 2004 11:12 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| Is some thing wrong |
Don't you think so from seeing the output of both the channel tabs?
Yes I would say create the new channel tab.
Did you ftp the channel tab. If yes did you do a BINARY ftp? |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Mon Aug 09, 2004 5:09 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Thanks.
I did a binary FTP. I have tried it twice. but I will try once again.
The MQWFCHL table file containted information about old configuration as well as new configuration. Is that causing any problem? |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Aug 09, 2004 6:07 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
|
| Back to top |
|
|
| ucbus1 |
| Posted: Mon Aug 09, 2004 8:41 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
I think the problem is with the MQWFCHL.TAB file. I did use FTP to binary. But I tried opening with a notepad. This was messing the TAB file. So I FTPed it binary. I have updated my MQWF client connection to point to the new configuration.
Following are the results of FMCZCCD
| Quote: |
The channel table in the profile is: C:\program files\mqseries workflow\chltabs\new.TAB
The connect name found in the profile : FMC.FMCGRP1.FMCSYS1,FMCQM1
The channel table exists.
The current user has read access to channel table file.
The channel table contains the following information:
Queue manager : FMCQM
Protocol : TCP/IP
Connection name : xxx.xx.x.xxx(xx10)
TCP/IP-addr : xxx.xx.x.xxx
TCP-Port : xx10
Status : ok
---------------
Queue manager : FMCQM1
Protocol : TCP/IP
Connection name : xxx.xx.x.xxx(yyy10)
TCP/IP-addr : 10.30.5.121
TCP-Port : yyy10
Status : ok
---------------
You are using the MQSeries Client API for the queue manager communication.
Checking system identifier FMC.FMCGRP1.FMCSYS1,FMCQM1 .
Ping to server xxx.xx.x.xxx was successful.
Connecting to the queue manager FMCQM1 was successful.
There are no checks with this utility to verify that the MQSeries Workflow Server is running on your server.
|
This tells me that the tab file is OK. I am ablet to ping to the server successfully and connect to the queue manager
Now, I have tried to logon to the FAT client on to "FMCSYS1" and "FMCGRP1' and I am getting "FMC_API_COMMUNICATION_ERROR". I have checked the windows event viewer and there are not MQ errors. I have checked all the logs and I could not find any errors
Can you suggest any solution?
Thanks |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Aug 09, 2004 10:11 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Did you give the connect names to both of your configurations?
I think that is what is missing. |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Mon Aug 09, 2004 10:58 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Thanks. I have added the connect name for my old configuration also.
| Quote: |
The channel table in the profile is: C:\program files\mqseries workflow\chltabs\new.TAB
The connect name found in the profile : FMC.FMCGRP1.FMCSYS1,FMCQM1,FMC.FMCGRP.FMCSYS,FMCQM
The channel table exists.
The current user has read access to channel table file.
The channel table contains the following information:
Queue manager : FMCQM
Protocol : TCP/IP
Connection name : xx.xx.x.xxx(xx10)
TCP/IP-addr : xx.xx.x.xxx
TCP-Port : xx10
Status : ok
---------------
Queue manager : FMCQM1
Protocol : TCP/IP
Connection name : xx.xx.x.xxx(yyy10)
TCP/IP-addr : xx.xx.x.xxx
TCP-Port : yyy10
Status : ok
---------------
You are using the MQSeries Client API for the queue manager communication.
Checking system identifier FMC.FMCGRP1.FMCSYS1,FMCQM1 .
Ping to server xx.xx.x.xxx was successful.
Connecting to the queue manager FMCQM1 was successful.
There are no checks with this utility to verify that the MQSeries Workflow Server is running on your server.
Checking system identifier FMC.FMCGRP.FMCSYS,FMCQM .
Ping to server xx.xx.x.xxx was successful.
Connecting to the queue manager FMCQM was successful.
There are no checks with this utility to verify that the MQSeries Workflow Server is running on your server.
|
Still it is giving a FMC_API_ERROR_COMMUNICATION. I have tried to connect FMCSYS1, FMCGRP1 but no ..luck |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Thu Aug 12, 2004 5:22 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
|
| Back to top |
|
|
| ucbus1 |
| Posted: Thu Aug 12, 2004 5:49 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
|
| Back to top |
|
|
| ucbus1 |
| Posted: Tue Aug 17, 2004 8:18 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Still waiting...
Can somebody help me on it?? |
|
| Back to top |
|
|
| jmac |
| Posted: Tue Aug 17, 2004 10:02 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
You might want to open a PMR
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| hos |
| Posted: Mon Aug 23, 2004 4:10 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
| Are you saying that your second configuration is linked to a brand new system and system group? Do you have a second data base that is primed with FMCGRP1 and FMCSYS1? |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Mon Aug 23, 2004 5:10 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
hos,
We have a FAT client on windows2000 machine configured to work with workflow application ( FMC/FMCSYS/FMCGRP configuration) on AIX. This is working fine.
Now we have added another workflow application ( FMC1/FMCSYS1/FMCGRP1 configuration). I am trying to set up the Fat client to connect to the new application.
We have created a FAT client configuration and we have copied the MQWFCHL.TAB from AIX node. Everything seems to be fine. (Please see my response to Vennela.) But still when we tried to connect we were getting "Communication Failure: FMC_API_ERROR_COMMUNICATION".
Please let me know |
|
| Back to top |
|
|
|
|
