| Author |
Message
|
| pnicolay |
 Posted: Sun Dec 05, 2010 10:30 am Post subject: |
 |
|
Apprentice
Joined: 29 Nov 2010
Posts: 26
|
| RogerLacroix wrote: |
| How did you copy the file to Windows? Did you ftp as a "binary" file or ASCII file? It must be copied as a binary file. |
The file has been copied via NetServer (which is an SMB emulation) so the file is copied correctly, and I can clearly see the correct contents via a hex viewer on my PC.
Also the trace clearly shows that he's at least able to read the first entry... but why don't I see a "rrxGetNextChannelDef" or something like that ? This alone makes me believe something is wrong with the client itself.
| RogerLacroix wrote: |
| You should download SupportPac MO72, create a CCDT file and then test it with amqsputc to make sure you have the correct parameters. |
I'll try that next Thursday when I'm back at that project... but when it would work it means that there's a problem on iSeries instead of the client (but it remains a bug). |
|
| Back to top |
|
 |
| pnicolay |
| Posted: Thu Dec 09, 2010 1:25 am Post subject: |
|
|
Apprentice
Joined: 29 Nov 2010
Posts: 26
|
According to IBM, a CCDT file created on a WMQ v6 server will not work with a WMQ v7 client.
I therefore created my client connection channel via Webpshere MQ Explorer on a WMQ 7, however the AMQCLCHL.TAB under /qmgrs/test/@ipcc doesn't get updated (in contrast to when I do the same on iSeries) ?
Is there anything I need/can do to force an update of AMQCLCHL.TAB on Windows ? |
|
| Back to top |
|
|
| pnicolay |
| Posted: Thu Dec 09, 2010 1:54 am Post subject: |
|
|
Apprentice
Joined: 29 Nov 2010
Posts: 26
|
Ignore my previous remark... since MQCHLLIB and MQCHLTAB was set for my test application, Websphere MQ updated that AMQCHLTAB.CHL file offcourse, and not the one in qmgrs/test/@ipcc
All works fine now as well... so it is clear that CCDT files are version related and should match. |
|
| Back to top |
|
|
| ramires |
| Posted: Thu Dec 09, 2010 2:51 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
| Is it working now? No more application locking? |
|
| Back to top |
|
|
| pnicolay |
| Posted: Thu Dec 09, 2010 4:10 am Post subject: |
|
|
Apprentice
Joined: 29 Nov 2010
Posts: 26
|
Yes, everything is working fine now... the application is no longer locking up on the new Queuemanager statement.
Apparently a WMQ Client v7 is not capable of using a WMQ Server v6 generated CCDT file. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Dec 09, 2010 8:10 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| pnicolay wrote: |
| Apparently a WMQ Client v7 is not capable of using a WMQ Server v6 generated CCDT file. |
That is not true. WMQ Client v7 can use a CCDT file generated by any previous version of WMQ Server, although the new features in v7 may not be available for CLNTCONN channels defined by the previous versions.
A CCDT generated by WMQ Server v7 cannot be used with any previous version WMQ Client. The connection will fail.
Curious factoid: A CCDT can actually contain CLNTCONNs defined under different versions of MQ. eg. Create several channels on MQ 6.0 and then alter one of them on MQ 7.0.
_________________
Glenn |
|
| Back to top |
|
|
| pnicolay |
| Posted: Fri Dec 10, 2010 1:10 am Post subject: |
|
|
Apprentice
Joined: 29 Nov 2010
Posts: 26
|
This is what IBM Support told me...
| IBM Support wrote: |
| The CCDT file version should be the same as the application. This means if the application use WMQ client V7, you need to create CCDT with WMQ V7 and if application uses WMQ V6 you need to create a CCDT file with WMQ V6. Rebuilding the ccdt with a qmgr running in V7 should resolves your issue. |
... and true or not (but also for me it is the first time I experience that WMQ is not backwards compatible), it solved my issue.
Looking with a hex editor, the piece that holds my client connection channel information looks identical (I'm only using queuemanager, connection name and max. message length which exists in both V6 and V7). |
|
| Back to top |
|
|
| ramires |
| Posted: Fri Dec 10, 2010 2:58 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Dec 12, 2010 3:10 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| ramires wrote: |
something is wrong with IBM support or with IBM documentation:
"A Version 7.0 WebSphere MQ client can use a client channel definition table that has been prepared by a Version 6.0 queue manager but a Version 6.0 client cannot use a client channel definition table that has been prepared by a Version 7.0 queue manager." |
What is wrong with that? The statement is correct.
| Quote: |
| http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.csqzaf.doc/cs12300_.htm |
Re MQCHLLIB variable, I couldn't see anything wrong on that page.
_________________
Glenn |
|
| Back to top |
|
|
| ramires |
| Posted: Sun Dec 12, 2010 4:31 pm Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
| What IBM support says is not correct, it contradicts what IBM documentation says: a v7 client can use a CCDT from a v6. |
|
| Back to top |
|
|
| pnicolay |
| Posted: Mon Dec 13, 2010 12:10 am Post subject: |
|
|
Apprentice
Joined: 29 Nov 2010
Posts: 26
|
| I reopened the PMR to get some clarification on this... more later. |
|
| Back to top |
|
|
|
|
