| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQCICS not converted on AIX, err2110: best alternative? |
« View previous topic :: View next topic » |
| Author |
Message
|
| pdegrandmaison |
 Posted: Thu May 03, 2007 5:21 am Post subject: MQCICS not converted on AIX, err2110: best alternative? |
 |
|
Newbie
Joined: 03 May 2007
Posts: 5
Location: Montreal, QC ,Canada
|
Hello everybody, I read several threads in this forum about the MQCICS format not being translated on distributed OS, only z/OS, I read several alternative not always very clean like coding the MQCICS in ebcdic(500) CCSID which is not really acceptable for us, but I know several people uses the distributed platform to code MQCICS messages destination z/OS.
What is the best alternative we should use to be able to provide an MQSeries message on AIX containing the MQCICS format?
I tried to switch off the data conversion on sender channel from AIX to z/OS but MQ seams to try to convert it anyway as it is rejected in my AIX DLQ.
Thanks, Pierre
_________________
Pierre DeGrandmaison
IT Integration Architect
Global Business Services
IBM Canada Ltd |
|
| Back to top |
|
 |
| EddieA |
| Posted: Thu May 03, 2007 1:03 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Reply messages from the CICS Bridge have to be converted in the Sender channel, as they leave z/OS, as only the z/OS version has the conversion routines. You should then code the receiving application to do a get WITHOUT conversion. Any attempt to do a conversion at this point will fail.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| pdegrandmaison |
| Posted: Fri May 04, 2007 4:41 am Post subject: |
|
|
Newbie
Joined: 03 May 2007
Posts: 5
Location: Montreal, QC ,Canada
|
Thanks Eddie, but as it is explained my question is from AIX to z/OS, not the reply from z/os to AIX.
Thanks anyway.
Pierre
_________________
Pierre DeGrandmaison
IT Integration Architect
Global Business Services
IBM Canada Ltd |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri May 04, 2007 6:46 am Post subject: |
|
|
Guest
|
| What is it that you are creating on AIX for CICS? A CICS transaction (3270 datastream)? or launching a cics application? What have you specified in an MQCIH? |
|
| Back to top |
|
|
| pdegrandmaison |
| Posted: Fri May 04, 2007 6:54 am Post subject: answer found |
|
|
Newbie
Joined: 03 May 2007
Posts: 5
Location: Montreal, QC ,Canada
|
Thanks everybody, I found the solution by myself.
I have both the AIX and z/OS queue managers in MQ cluster. The difference with cluster channels is the receiver cluster channel CAN have a data conversion field to YES, where a simple receiver channel CAN'T. My problem was although if my Cluster Sender channel on AIX had the Data Conversion set to NO, the corresponding receiver cluster channel on z/OS had the Data Conversion to YES. I guess the AIX QM in this specific situation override and consider the Data Conversion being YES then and fails with an error 2110 Format Error on AIX because the MQCICS format conversion not supported on AIX!
Pierre,
_________________
Pierre DeGrandmaison
IT Integration Architect
Global Business Services
IBM Canada Ltd |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri May 04, 2007 7:07 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The cluster sender channel used to pass messages to your AIX will be based on the cluster receiver you defined on AIX.
Likewise, the cluster sender channel used to pass messages to your zOS will be based on the cluster receiver you defined on zOS.
Unless either of those are FRs, in which case the manually defined cluster sender you created will be used.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri May 04, 2007 11:03 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jefflowrey wrote: |
The cluster sender channel used to pass messages to your AIX will be based on the cluster receiver you defined on AIX.
Likewise, the cluster sender channel used to pass messages to your zOS will be based on the cluster receiver you defined on zOS.
Unless either of those are FRs, in which case the manually defined cluster sender you created will be used. |
Even with full repositories, the automatic cluster senders are used. The manual cluster senders are restricted to some specific traffic ( inter repository command traffic ?)
From the manual:
| Quote: |
| The CLUSSDR definitions made on the full repository queue managers are special. All the updates exchanged by the full repositories flow exclusively on these channels. The administrator controls the network of full repositories explicitly. The administrator must make the CLUSSDR definitions on full repository queue managers manually and not leave them to be auto-defined |
| Quote: |
| Auto-defined cluster-sender channels take their attributes from those specified in the corresponding cluster-receiver channel definition on the receiving queue manager. Even if there is a manually-defined cluster-sender channel, its attributes are automatically modified to ensure that they match those on the corresponding cluster-receiver definition |
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
