ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Mainframe, CICS, TXSeries » IMS Bridge response encoding

Post new topic  Reply to topic
 IMS Bridge response encoding « View previous topic :: View next topic » 
Author Message
atheek
PostPosted: Thu Jul 24, 2008 2:58 pm    Post subject: IMS Bridge response encoding Reply with quote

Partisan

Joined: 01 Jun 2006
Posts: 327
Location: Sydney

Hi All,

we are having a j2ee application that communicates with an IMS transaction via an IMS Briddge. We have this application running in stage environment and also in production.

The code and configuration from the j2ee side is same in both environments. The problem I am facing is that in these 2 environments , I am getting the response from IMS Bridge with different encodings.

Production
=======

MQMD Header :
Encoding : 546 CodedCharSetId : 850
Format : 'MQIMS '

IMS Header within the response message
===========================

<StructID>IIH</StructID>
<Version>1</Version>
<Length>84</Length>
<Encoding>546</Encoding>
<CodedCharSetID>850</CodedCharSetID>
<Format>MQSTR</Format>


Stage
====
MQMD Header

Encoding : 785 CodedCharSetId : 500
Format : 'MQIMS '


IMS Header within the response message
===========================
<StructID>IIH</StructID>
<Version>1</Version>
<Length>84</Length>
<Encoding>785</Encoding>
<CodedCharSetID>0</CodedCharSetID>
<Format>MQSTR</Format>

These are the details of the message in the queue before being picked up by the application

I am using an adaptor for communicating with the queues from the application. For this adaptor , I need to specify the encoding of the response messages in the queue. e.g. If I specify it as cp-500, the adaptor assumes that the message in the queue is of encoding 500 and converts it to UTF-8 applying the conversion rules for cp500 to UTF-8. This is causing a problem in production since the message in the queue is with a different (850) encoding. The only solution I have is to maintain different codes for staging where I need to set encoding to cp500 and in production where I dont have to do this.

My question is who exactly decides the encodings in the MQ Headers and IMS Headers in the response message - is it decided by the IMS application code that generates the response message, or the IMS Bridge or the queue manager at mainframe side itself? I can confirm that there is no channel conversion turned on at the sender channel at mainframe side . Also there are no channel exits configured.

Here there is nobody who is atleast half good in IMS Bridge Appreciate your help.

TIA
-Atheek
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Mainframe, CICS, TXSeries » IMS Bridge response encoding
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.