| Author |
Message |
 Topic: [RESOLVED]Hex 15 |
lung
Replies: 4
Views: 2324
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jun 19, 2012 1:03 am Subject: [RESOLVED]Hex 15 |
Hi,
Thanks for the reply.
Anyway apparently the x'25' is only appearing in the trace files, when put into Q, it is still x'15'.
I guess WMB just converts the x'15' (new line) to the native CC ... |
| Topic: [RESOLVED]Hex 15 |
lung
Replies: 4
Views: 2324
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Jun 18, 2012 8:25 pm Subject: [RESOLVED]Hex 15 |
Hi,
I am having an issue with x'15' being converted to x'25'.
The message has an MQMD of CCSID 500 (EBCDIC).
All other characters are CAST properly without issue, only x'15' seems to be conve ... |
| Topic: Default value in HexBinary |
lung
Replies: 12
Views: 6765
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jan 19, 2012 4:18 am Subject: Default value in HexBinary |
Hi,
The incoming message is actually XML in clear text, for example:
<XML>
<FieldA>123</FieldA>
</XML>
It is the receiving program that is expecting hexBinary form. ... |
| Topic: Default value in HexBinary |
lung
Replies: 12
Views: 6765
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jan 18, 2012 4:40 pm Subject: Default value in HexBinary |
Hi,
No, that is not what I meant...
Actually the incoming msgs are XML, it is the outgoing msgs that is going to legacy.
And in these outgoing messages, there are fields in hex format which c ... |
| Topic: Transforming XML to MRM with optional elements |
lung
Replies: 15
Views: 13359
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jan 17, 2012 5:47 pm Subject: Transforming XML to MRM with optional elements |
Hi,
It is actually delimited. I am omitting that info because what I want to do is to achieve this in CWF as mentioned earlier.
So the output will actually be:
ABC<LF><LF>GHI<LF& ... |
| Topic: Default value in HexBinary |
lung
Replies: 12
Views: 6765
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jan 17, 2012 5:29 pm Subject: Default value in HexBinary |
Hi,
a) The amount example is just an example, there are other fields which has similar requirements to be sent in hexBinary format, eg. an ID number sent in from front end as "123A" will ... |
| Topic: Default value in HexBinary |
lung
Replies: 12
Views: 6765
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jan 17, 2012 3:32 am Subject: Default value in HexBinary |
Hi,
The message flow is actually parsing from XML to MRM, where the receiving program is residing on a mainframe.
The program is receiving an amount field in hex format, where for example the fi ... |
| Topic: Transforming XML to MRM with optional elements |
lung
Replies: 15
Views: 13359
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jan 17, 2012 3:19 am Subject: Transforming XML to MRM with optional elements |
Hi,
The reason why I prefer to use CWF is because I want to keep track of the max length of the field, this has often come up as a troubleshooting issue in the past when I used TDS.
As per my gi ... |
| Topic: Transforming XML to MRM with optional elements |
lung
Replies: 15
Views: 13359
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Jan 16, 2012 10:15 pm Subject: Transforming XML to MRM with optional elements |
Yea, I am trying to get the actual copybook from the receiving program, but until then I need to figure this out on my own...
Basically, input data is something like:
<XML>
<A>ABC< ... |
| Topic: Default value in HexBinary |
lung
Replies: 12
Views: 6765
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Jan 16, 2012 10:03 pm Subject: Default value in HexBinary |
Yep, tried that as well.
Anyway I read from here
http://www-01.ibm.com/support/docview.wss?uid=swg1IC43680
That default values are not supported for HexBinary type... But this article is from W ... |
| Topic: Default value in HexBinary |
lung
Replies: 12
Views: 6765
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Jan 16, 2012 7:38 pm Subject: Default value in HexBinary |
Hi,
I am trying to figure out what kind of values are acceptable in the default value box for HexBinary type.
(Properties -> Logical Properties -> Local Element)
I have tried 00, x'00', & ... |
| Topic: Transforming XML to MRM with optional elements |
lung
Replies: 15
Views: 13359
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Jan 16, 2012 7:13 pm Subject: Transforming XML to MRM with optional elements |
Hi,
Any workaround for the problem above?
I found myself trying to achieve the same thing.
Am actually looking at CWF with Min Occurs = 0, and Max Occurs = 1, but the Min Occurs doesn't seem to ... |
| Topic: 'DETACH'ing a field under the Environment.Variables tree |
lung
Replies: 4
Views: 5718
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 29, 2008 9:32 pm Subject: 'DETACH'ing a field under the Environment.Variables tree |
Ah thanks... DELETE FIELD seems to work perfectly for this.
Another question if I may... How do I delete off multiple occurences of an array?
For example Environment.Variables.ABC[1] and Environ ... |
| Topic: 'DETACH'ing a field under the Environment.Variables tree |
lung
Replies: 4
Views: 5718
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 29, 2008 8:26 pm Subject: 'DETACH'ing a field under the Environment.Variables tree |
Hey there,
I have a simple question, how do I detach a field from the Environment.Variables tree, so that it doesn't carry forward to the next node?
Simply put, I need a DETACH command that work ... |
| Topic: BIP0404E - Error while renaming a Msg flow |
lung
Replies: 16
Views: 11133
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 03, 2007 7:53 pm Subject: BIP0404E - Error while renaming a Msg flow |
Yes I do have a v5 broker running, but this project that is still residing on 2.1 needs an urgent change so I don't have the time luxury to migrate yet.
Help! 
EDIT: Nvm, worked it out. Appare ... |
