| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Handling low values in MRM |
« View previous topic :: View next topic » |
| Author |
Message
|
| vishal |
 Posted: Sat May 29, 2004 8:48 pm Post subject: Handling low values in MRM |
 |
|
Novice
Joined: 01 Feb 2004
Posts: 13
|
I have a task in, which I transform the MRM to XML. Some of the fields passed from the legacy system would contain low values (HEX zero's)..In this case I would like to eliminate
the XML tag.
My output XML structure would look like as below...
DECLARE IM REFERENCE TO InputRoot.MRM;
CREATE FIELD OutputRoot.XML.myXML;
DECLARE OM REFERENCE TO OutputRoot.XML.myXML;
SET OM.(XML.attr)A = IM."A";
SET OM.(XML.attr)B = IM."B";
SET OM.(XML.attr)C = IM."C";
SET OM.(XML.attr)D = IM."D";
SET OM.(XML.attr)E = IM."E";
I want to eliminate the attribute in the output XML....Can this be handled this while defining MRM CWF physical structure..like if low values are passed in any particular field say A
Does CWF parser can eliminate the MRM fields if it encounters the X'00'
IM."A" would be null..
So, that while assigning this value to outputXML
SET OM.(XML.attr)A =NULL;...and it gets eliminated
(OR)Do I need to exclusively code this in ESQL (compute node) like writing a procedure..
Can any one advice on this..I need this to be resolved ASAP..I need a start on this.. |
|
| Back to top |
|
 |
| kirani |
| Posted: Mon May 31, 2004 5:32 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
I believe you need to code this in ESQL. In your message set you can mention padding for that element, but it's only used when creating/parsing the bitstream.
You need to check null values into each incoming field using ESQL code and set the attribute to NULL when X'00' is found.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| shanson |
| Posted: Tue Jun 01, 2004 5:07 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
There's a couple of things to bear in mind here.
Low values. I take it that the source app is COBOL? You may find that you get parsing errors if low values have been moved to a field that, according to its data type, should not contain low values. The way round this is to use the MRM CWF format's null handling capability, which allows you to specify a null value for a field; if the field has this value you get a NULL value element in the tree. One problem - it is not currently possible to enter hex values as null values - but this is planned to be addressed in the next WBI-MB V5 fixpak.
Once you have your NULL elements, there is no MRM XML format option to discard the element if it is null, so you would have to delete the element from the tree yourself in ESQL. You may want to consider using the XML Schema Instance mechanism for flagging a null field - the xsi:nil attribute -which MRM XML supports today. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
