MQSeries.net :: View topic - Error '4' converting a character string to or from codepage

gmmqnet · Posted: Fri Dec 22, 2006 1:35 pm Post subject:

Environment-
AIX,MB6.0,MQ6.0

Case-
Sending a message to Siebel using adapter response received in response queue.Trying to access the response from the flow using a MQGet node.Gives the following trace node result -
---------------
Root Message:
(
(0x01000000):Properties = (
(0x03000000):MessageSet = NULL
(0x03000000):MessageType = NULL
(0x03000000):MessageFormat = NULL
(0x03000000):Encoding = NULL
(0x03000000):CodedCharSetId = NULL
(0x03000000):Transactional = NULL
(0x03000000):Persistence = NULL
(0x03000000):CreationTime = NULL
(0x03000000):ExpirationTime = NULL
(0x03000000):Priority = NULL
(0x03000000):ReplyIdentifier = X'414d5120535343494445564d512020204575da7e2003e806'
(0x03000000):ReplyProtocol = 'MQ'
(0x03000000):Topic = NULL
(0x03000000):ContentType = NULL
)
(0x01000000):MQMD = (
(0x03000000):Format = ''
(0x03000000):CorrelId = X'414d5120535343494445564d512020204575da7e2003e806'
)
)

Local Environment:

Exception Tree:
(
(0x01000000):RecoverableException = (
(0x03000000):File = '/build/S600_P/src/DataFlowEngine/ImbDataFlowNode.cpp'
(0x03000000):Line = 616
(0x03000000):Function = 'ImbDataFlowNode::createExceptionList'
(0x03000000):Type = 'ComIbmMQGetNode'
(0x03000000):Name = 'CItoODS/CITMOUT_CIRESUBMIT#FCMComposite_1_4'
(0x03000000):Label = 'CItoODS.CITMOUT_CIRESUBMIT.SIEBEL.RESPONSE1'
(0x03000000):Catalog = 'BIPv600'
(0x03000000):Severity = 3
(0x03000000):Number = 2230
(0x03000000):Text = 'Node throwing exception'
(0x01000000):RecoverableException = (
(0x03000000):File = '/build/S600_P/src/DataFlowEngine/ImbMqGetNode.cpp'
(0x03000000):Line = 1567
(0x03000000):Function = 'ImbMqGetNode::failureProcess'
(0x03000000):Type = ''
(0x03000000):Name = ''
(0x03000000):Label = ''
(0x03000000):Catalog = 'BIPv600'
(0x03000000):Severity = 3
(0x03000000):Number = 4633
(0x03000000):Text = 'MQGet node Exception'
(0x01000000):RecoverableException = (
(0x03000000):File = '/build/S600_P/src/CommonServices/ImbConverter.cpp'
(0x03000000):Line = 112
(0x03000000):Function = 'ImbConverterCPP::ImbConverterCPP'
(0x03000000):Type = ''
(0x03000000):Name = ''
(0x03000000):Label = ''
(0x03000000):Catalog = 'BIPv600'
(0x03000000):Severity = 3
(0x03000000):Number = 2130
(0x03000000):Text = 'Error creating converter'
(0x01000000):Insert = (
(0x03000000):Type = 2
(0x03000000):Text = '0'
)
(0x01000000):Insert = (
(0x03000000):Type = 2
(0x03000000):Text = '4'
)
)
)
)
)
------------------------------
Ran a debug trace on the same and gets this error

2006-12-21 14:44:35.928581 3031 UserTrace BIP4635I: The MQ Get node 'CItoODS.CITMOUT_CIRESUBMIT.SIEBEL.RESPONSE1' failed to navigate to the default location ''InputLocalEnvironment.MQ.GET'' for ''Input MQ Parameters Location''.
Location ''InputLocalEnvironment.MQ.GET'' is the default value for ''Input MQ Parameters Location'' and it was not found. It is assumed that this ''Input MQ Parameters Location'' node property is not needed in this case and, therefore, the issue is ignored.
Ignore this message (and the previous user trace message regarding this navigation, if there is one) if this ''Input MQ Parameters Location'' node property is not needed; Otherwise, make sure the location is available or correct the location specification.
2006-12-21 14:44:35.928939 3031 UserTrace BIP2231E: Error detected whilst processing a message 'CItoODS.CITMOUT_CIRESUBMIT.SIEBEL.RESPONSE1'.
The message broker detected an error whilst processing a message in node 'CItoODS.CITMOUT_CIRESUBMIT.SIEBEL.RESPONSE1'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2006-12-21 14:44:35.928951 3031 RecoverableException BIP2130E: Error '4' converting a character string to or from codepage '0'.
A character conversion between codepages has failed. This may be due to an invalid codepage being specified in the header of a message, or may be due to a character being present in a message that does not appear in the required codepage conversion table.
Check that the application that generated the message is using a valid codepage in the message header and that all characters used are valid in that codepage.
2006-12-21 14:44:35.929054 3031 UserTrace BIP2540I: Node 'CItoODS.CITMOUT_CIRESUBMIT.Failure Trace': Finished evaluating expression ''CURRENT_TIMESTAMP'' at ('', '2.29'). The result was ''TIMESTAMP '2006-12-21 14:44:35.928967'''.
2006-12-21 14:44:35.929199 3031 UserTrace BIP2539I: Node 'CItoODS.CITMOUT_CIRESUBMIT.Failure Trace': Evaluating expression ''Environment.Variables.XML.CIReprocessMessage.TableName'' at ('', '3.16'). This resolved to ''Environment.Variables.XML.CIReprocessMessage.TableName''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='TableName' Value='S_ORG_EXT'''.
2006-12-21 14:44:35.929264 3031 UserTrace BIP2539I: Node 'CItoODS.CITMOUT_CIRESUBMIT.Failure Trace': Evaluating expression ''Environment.Variables.XML.CIReprocessMessage.RowId'' at ('', '4.13'). This resolved to ''Environment.Variables.XML.CIReprocessMessage.RowId''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='RowId' Value='TST1-65HKZ'''.
2006-12-21 14:44:35.929344 3031 UserTrace BIP4067I: Message propagated to output terminal for trace node 'CItoODS.CITMOUT_CIRESUBMIT.Failure Trace'.
The trace node 'CItoODS.CITMOUT_CIRESUBMIT.Failure Trace' has received a message and is propagating it to any nodes connected to its output terminal.
No user action required.

--------------------
Ran the same on Windows works fine.Any help would be appreciated.