| Author |
Message
|
| anveshita |
 Posted: Tue Mar 08, 2005 7:43 am Post subject: Fat client - help |
 |
|
Master
Joined: 27 Sep 2004
Posts: 254
Location: Jambudweepam
|
Hello,
I have created a Fat Client configuration on Windows box to connect to my workflow server, which is on UNIX-PROD.
I have exported the MQWFCHL.TAB file from UNIX-PROD to the Windows box and pointed my fat client to point to the
MQWFCHL.TAB file.
Two wierd things.
1. When I have started the Fat client it is starting but was pointing to UNIX-DVLP. I checked all the instances and
I am sure it is pointing to UNIX-DVLP and not UNIX-PROD as I am hoping for. I made sure there is no other fat client
configuration on the box. Why is it connecting to DVLP when my chltab file is from PROD. I have opened a copy of the file
and searched for the host address and it is clearly pointing to PROD and not DEV. Can somebody help me why it is pointing
to DEV instead of PROD?
2. I ran the fmczccd utility and the utility was not giving the information as I am hoping for
| Quote: |
The channel table in the profile is: C:\program files\mqseries workflow\chltabs\
MQWFCHL.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 utlity is not giving any information more than this. Idelally it should have given me some information like
Queue manager name, protocol, connection name etc., obviously some thing is wrong
Any help in this regards is appreciated.
Thanks
Last edited by anveshita on Tue Mar 08, 2005 8:43 pm; edited 2 times in total |
|
| Back to top |
|
 |
| anveshita |
| Posted: Tue Mar 08, 2005 12:52 pm Post subject: |
|
|
Master
Joined: 27 Sep 2004
Posts: 254
Location: Jambudweepam
|
Some additional info.
I have noticed that the there is a variable mqserver was set to point to the DEV box. I have corrected that to point to the PROD box and the Fat client configuration started working. But this restricts me to work with only one host. Hence I would like to use channel tab file approach.
I have tried taking out MQSERVER variable and replaced them with MQCHLLIB and MQCHLTAB parameters. Pointed MQCHLLIB to the directory where I my channel tab file from UNIX-PROD and MQCHLTAB to poin to UNIX-PROD.TAB
Now I started getting FMC_COMMNICATION _ERROR when I tried logging on using the fat client
When I tried FMCZCCD it is, ending the same way I have indicated in my above post
Please let me know what do I have to do.
Thanks |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Mar 08, 2005 4:35 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Did you reconfigure your Fat Client to use the new channel table file.
_________________
-Ratan |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Tue Mar 08, 2005 8:36 pm Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
| Are you seeing any errors besides this error? |
|
| Back to top |
|
|
| anveshita |
| Posted: Tue Mar 08, 2005 8:43 pm Post subject: |
|
|
Master
Joined: 27 Sep 2004
Posts: 254
Location: Jambudweepam
|
Ratan,
Do you mean dropping the configuration and recreating it? Yes
I did it.
Please let me know if it is not what you meant.
Besides this, when the communication error occurred it created an FDC saying that some access violation.I will post it if it is needed. But I guess it is rather effect than cause. I am bit peplexed to see FMCZCCD quitting this with out executing fully.
Thanks |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Mar 08, 2005 11:14 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
The only reason I can think of why fmczccd quits is if the system doesn't have any default configuration. Other than that there should be no reason why it would quit unless it's a bug.
Anveshitha:
What is that you are trying to do?
What are the connect names for dev and prod? |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Wed Mar 09, 2005 6:34 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
| What version of workflow is it? |
|
| Back to top |
|
|
| anveshita |
| Posted: Wed Mar 09, 2005 7:12 am Post subject: |
|
|
Master
Joined: 27 Sep 2004
Posts: 254
Location: Jambudweepam
|
Vennela,
Here is what I am trying to do.
1. I am trying to set up a Fat client configuration on windowsfor my production box.
I have exported the MQWFCHLTAB file from my production box (UNIX-PROD) to Windows box.
Used the configuration utility,created a run time client and pointed it to MQWFCHLTAB file.
2. The client started working,but I have noticed that it was pulling work list from UNIX-DEV.
3. I have checked and found that there is a property called "MQSERVER" which was pointing to
UNIX-DEV.I have changed this to point to UNIX-PROD and it started pulling the work list from
UNIX-PROD.
4. At this point I ran fmczdd utility. It quit after execuring the following statements
| Quote: |
The channel table in the profile is: C:\program files\mqseries workflow\chltabs\
MQWFCHL.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. |
5. Now, having this property "MQSERVER" restricts me to useonly one configuration because it points
to UNIX-PROD or UNIX_DEV. My idea is to have one fat client for UNIX-PROD and one for UNIX-DEV.I think the
way this can be achieved is to use the varialbes "MQCHLLIB" and "MQCHLTAB" properties.So I have replaced
the "MQSERVER" properties with "MQCHLLIB" and "MQCHLTAB" properties.
MQCHLLIB C:\Program Files\MQSeries Workflow\chltabs
MQCHLTAB MQWFCHL.TAB ( Tried lower case too)
6. I have re-created the client configuration and tried step4. But it is still quitting.
7. Then I tried use the configuation I have created knowing that it would not work, because of step6.
Got FMC-API-communicaton error and it created a FDC.
Any help is appreciated on figuring out why fmczccd is quitting and whats wrong with the steps I am performing
Thanks
Post script: the connect names I am using in both DEV and PROD are
FMC.FMCGRP.FMCSYS,FMCQM
MQ Workflow Version 3.5 |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Thu Mar 10, 2005 5:16 pm Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
I am not sure why it is not working.
But is there a reason why you can't use MQSERVER property, if you are able to connect to the your production machine?
One way is to have batch file to set the environment variable in your batch script for MQSEREVER and set it to point to PROD and run fmcn6rtc.exe -y <prod> config.
Have another one to point to DVLP.
I know this is awkward, but you may try this in the mean time.
Hopefully somebody would answer this on this forum |
|
| Back to top |
|
|
| anveshita |
| Posted: Fri Mar 11, 2005 9:12 am Post subject: |
|
|
Master
Joined: 27 Sep 2004
Posts: 254
Location: Jambudweepam
|
Thanks for the alternaticve.
I still would like to know why my approach is not working.
Please let me know |
|
| Back to top |
|
|
| anveshita |
| Posted: Tue Mar 15, 2005 7:18 am Post subject: |
|
|
Master
Joined: 27 Sep 2004
Posts: 254
Location: Jambudweepam
|
|
| Back to top |
|
|
| vennela |
| Posted: Tue Mar 15, 2005 8:35 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
You should read the MQ Clients manual on how MQ client works.
Creating a channel table is extensively discussed in the following manual
http://www.mqseries.net/phpBB2/viewtopic.php?t=1732&highlight=channel+table+create
Having said that it is not easy to solve your problem because, you have the same system system group and qmgr name in both the environments.
The only way I can think of is create two channel tables, the first one with DEV qmgr and the second one with PROD QMGR and use some batch file to point to your desired channel table before invoking the workflow client. |
|
| Back to top |
|
|
|
|
