MQSeries.net :: View topic - mrm-xml

pepperpaddy · Posted: Tue Jul 29, 2003 1:04 am Post subject: mrm-xml

hi

I am importing a C structure like the one below
completemsg{
header{
char HField1[4];
char HField2 [6];
}header1;
detail{
char DField1[4];
char DField2 [6];
}detail1;
trailer{
char TField1[4];
char TField2 [6];
}trailer1;
}completemsg1;

I have a type called CompleteMsg which has 3 sections Header, Detail and Trailer with their fields within this. This is within a message set with a CWF. I have set the Detail part and it's members to repeating with min =1 and the max left blank as I will never know how many blank lines there are in the message.
I then went to the compute node
set OutputRoot = InputRoot;
and
DECLARE M INTEGER;
SET M = CARDINALITY("InputBody"."DETAIL1"[]);
DECLARE X INTEGER;
SET X = 1;
WHILE X < M DO
SET "OutputRoot"."MRM"."XMLPPEXACT_DETAIL"[X]."DField1" = "InputBody"."DETAIL1"[X]."DField1";
SET "OutputRoot"."MRM"."XMLPPEXACT_DETAIL"[X]."DField2" = "InputBody"."DETAIL1"[X]."DField2";
END WHILE;

this works if I have only one detail line when I have more than one detail line I get the following message
ParserException BIP5285E: Message Translation Interface Parsing Errors have occurred:
Message Set Name : 'COMPLETEMSG'
Message Set Level : '1'
Message Format : 'CWF'
Message Type Path : 'COMPLETEMSG'
Review further error messages for an indication to the cause of the errors.
2003-07-29 09:03:38.530998 1908 ParserException BIP5171E: Custom Wire Format parsing error
An error occurred while parsing a Custom Wire Format message.
Current message : 'COMPLETEMSG'
Current element : 'COMPLETEMSG'
Path from message root : ''
Offset from start of message : 308
See following errors for more details.
2003-07-29 09:03:38.530998 1908 ParserException BIP5288E: MRM parsing error. Message bit stream larger than expected.
The bit stream of the message being parsed by the MRM parser is larger than expected for a message of this message type.
The message bit stream has been incorrectly constructed, or the logical model is incorrect.
Ensure that the message is correctly packaged.
Ensure that the message properties are correct.
Ensure that the logical model for this message type is complete (the message set and message type should be quoted in previous messages).

The repeating line is not picked up before it is parsed, does anyone have any ideas on this? Have I gone about it the right way? Is there a better way ?

thanks