| Author |
Message |
 Topic: Migrate NEON Message Flows for Message Broker 7 |
mglaiste
Replies: 3
Views: 4584
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Wed Apr 25, 2012 1:34 am Subject: Migrate NEON Message Flows for Message Broker 7 |
| Mesage Broker 7 will not suport NEON Rules and Formatter. We have a lot of flows using NEON formatter for complex repepeating data structures. Does anyone know if there are any tools to help in the mi ... |
| Topic: German Characters Problem |
mglaiste
Replies: 25
Views: 17996
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Apr 13, 2012 1:27 am Subject: German Characters Problem |
| AND ftp was set to BINARY with a custom end of line character (0D0A) suitable for the Windows environment. |
| Topic: German Characters Problem |
mglaiste
Replies: 25
Views: 17996
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Apr 13, 2012 1:15 am Subject: German Characters Problem |
I have traced the issue:-
The mesage flow was building a text file using the FileOutPut node. The file was then ftp'd to a Windows server. The hex values for ö was correct BUT the file, after FTP ... |
| Topic: German Characters Problem |
mglaiste
Replies: 25
Views: 17996
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 10, 2012 4:19 am Subject: German Characters Problem |
Hi Kimbert
Thanks for the info. I had seen that the XML domain had been deprecated in version 6.1 but hadn't seen any contra indicators for XMLNS. I will chnage to XMLNSC when I can, I don't want t ... |
| Topic: German Characters Problem |
mglaiste
Replies: 25
Views: 17996
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 10, 2012 3:08 am Subject: German Characters Problem |
| Thanks, I assume this will not make any difference to the german chars issue. |
| Topic: German Characters Problem |
mglaiste
Replies: 25
Views: 17996
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 10, 2012 2:57 am Subject: German Characters Problem |
I use XMLNS (I don't want to validate the XML just be able to reference the payload:-
SET outdata = InputRoot.XMLNS.Envelope.Body.Data.Row[I]; |
| Topic: German Characters Problem |
mglaiste
Replies: 25
Views: 17996
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 10, 2012 2:35 am Subject: German Characters Problem |
I have changed the FTP to binary. The purpose of the message flow is to extract tge data payload from the XML and create a text file for use with another application.
Rfhutil displays the xml heade ... |
| Topic: German Characters Problem |
mglaiste
Replies: 25
Views: 17996
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Apr 05, 2012 5:42 am Subject: German Characters Problem |
| The message flow is writing ö as hex c3 b6 which is not ASCII |
| Topic: German Characters Problem |
mglaiste
Replies: 25
Views: 17996
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Apr 05, 2012 5:02 am Subject: German Characters Problem |
| The data is FTP'd to a windows server. I downloaded the data and ö is ?? when viewed in Notepad++. WBI is sending as ASCII |
| Topic: German Characters Problem |
mglaiste
Replies: 25
Views: 17996
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Apr 05, 2012 4:13 am Subject: German Characters Problem |
SET OutputRoot.Properties.CodedCharSetId = 1208;
SET OutputRoot.MQMD.CodedCharSetId = 1208;
DECLARE outdata CHAR ' ';
SET outdata = InputRoot.XMLNS.Envelope.Body.Data.Row[1];
SET Outpu ... |
| Topic: German Characters Problem |
mglaiste
Replies: 25
Views: 17996
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Apr 05, 2012 3:05 am Subject: German Characters Problem |
The message flow receives XML encoded as UTF-8. Mesage tester is showing codepage 1208.
I am extracing the data from the XML and writing out as BLOB
outdata = CAST(indata AS BLOB CCSID 1208)
Th ... |
| Topic: BIP2543I |
mglaiste
Replies: 1
Views: 3085
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Aug 15, 2007 5:52 am Subject: BIP2543I |
I have xml incoming and am trying to assign a variable to a value in a tag.
SET Trans_Type = Root.MRM.Envelope."Body".Header.TransmissionReference;
I get the following error:-
''SET T ... |
| Topic: NEON Export Error |
mglaiste
Replies: 1
Views: 1851
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 23, 2007 2:19 am Subject: NEON Export Error |
Hi
I'm using the NNFIE application to extract NEON formats from the data base. The application abends with:-
‘Fatal Win32 Program Error 0Xc0000005
This application has requested the Runtime to ... |
| Topic: BIP5180E |
mglaiste
Replies: 4
Views: 4580
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Feb 19, 2004 3:31 am Subject: Unknown Type |
Got it:-
There appears to be a bug in WMQI v2.1.
The input MRM messsage set was produced using ver 2.01. When message types were generated they were prefixed by m_XXXX.
e.g. m_MCS_DESPATCH_IN_M ... |
| Topic: BIP5180E |
mglaiste
Replies: 4
Views: 4580
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Feb 19, 2004 2:06 am Subject: BIP 5180E |
| I am trying to produce XML output from MRM input. |
