| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| CICS request Node Error in Message broker 8 |
« View previous topic :: View next topic » |
| Author |
Message
|
| wbi_telecom |
 Posted: Tue Oct 09, 2012 5:53 am Post subject: |
 |
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
Sometimes if you use mirror transactions in CICS, you tend to use a default IPCONN dynamically. I think that is what might be happening in this case because of which the security identity is not getting propagated. That is why I suggeste to confirm that an IPCONN is created and is used because I noticed that he is using a mirror transaction in his CICSRequest node. I agree with you on the USERAUTH settings provided the IPCONN is already created.
Cheers |
|
| Back to top |
|
 |
| kishoreraju |
| Posted: Wed Oct 10, 2012 9:07 am Post subject: |
|
|
Disciple
Joined: 30 Sep 2004
Posts: 156
|
After setting up the clientApplid,clientQualifier i am able to connect to CICS using CICS request from my broker flow which is running on Windows7.But now i am having data encoding isssues with the response message data. Could you please advise the right CCISID i need to use to get the data in right format.
Here are properies configured in CICS request node for response message parsing.
In Response Message Parsing here are the properties
Message DodedCahracter set ID: EBCDI(037)
Message encoding :Big Endian,Wi IEE Floating point(273) |
|
| Back to top |
|
|
| wbi_telecom |
| Posted: Wed Oct 10, 2012 9:16 am Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
I think the Encoding should be 785. Are you creating a message deifinition file for your COMMAREA. Your CCSID looks good but you have to make sure to use the same when you create your message definition file. (its on the last page of the importer).
Cheers, |
|
| Back to top |
|
|
| kishoreraju |
| Posted: Fri Oct 12, 2012 6:07 am Post subject: |
|
|
Disciple
Joined: 30 Sep 2004
Posts: 156
|
Data conversion issue with CICS Request Node is resolved by setting the CCSID and Encoding in the request that is being send to CICS.
SET OutputRoot.Properties.CodedCharSetId=500;
SET OutputRoot.Properties.Encoding=785;
Thanks for all your help in resolving this issue. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
