MQSeries.net :: View topic - Variable number of record occurrences in a compound message

sri_sridhar · Posted: Thu Feb 26, 2004 1:56 pm Post subject:

In one big message record we have the following types: FUND_INFORMATION, POLICY_INFORMATION, AGENT_INFORMATION.
The first two contain fields and they repeat a fixed number of times but the AGENT_INFORMATION type (which contains 8 fields) repeats 1 - 99 times. This information may not necessarily repeat 99 times, sometimes it could repeat 5, 10, 15, 30, etc.... times.

I have it coded like this below but all the messages fail.
Any suggestions?

DECLARE looper INTEGER;
SET looper = 1;

WHILE (looper <= CARDINALITY("InputBody"."A170_DETAIL_RECORD_IN"."AGENT_INFORMATION"."INDPDCRRECORD"[ ] )) DO

SET "OutputRoot"."MRM"."A170_DETAIL_RECORD_OUT"."AGENT_INFORMATION"[looper]."INDPDCRRECORD" = 'PDCR';

SET "OutputRoot"."MRM"."A170_DETAIL_RECORD_OUT"."AGENT_INFORMATION"[looper]."PCTCOMMSPLIT" =
"InputBody"."A170_DETAIL_RECORD_IN"."AGENT_INFORMATION"[looper]."PCTCOMMSPLIT";
--
--
--
--
--
--

SET looper = looper + 1;
END WHILE;

The reading of a text element of a message failed because the
message was too short to contain the expected length of text.
Check that the processed message is of the expected format an
d type. If the problem persists please record all the details provided with this error message and c
ontact your IBM support center.
2004-02-25 16:33:56.184804 15 UserTrace BIP2631I: Backed out message being propagated to f
ailure terminal; node 'PL_170_OD_WMQI_1.SPL.DLNK.170.NEWWAY'.
Node 'PL_170_OD_WMQI_1.SPL.DLNK.170.NEWWAY' has received a me
ssage which has previously been backed out because of a processing error in the message flow. The M
QMD 'backoutCount' of the message exceeds (or equals) the 'backoutThreshold' defined for the MQSerie
s input queue. The message broker is propagating the message to the failure terminal of the node.
Examine the other messages and the message flow to determine
why the message is being backed out. Correct this situation if possible. Perform any local error r
ecovery processing required.
2004-02-25 16:33:56.185484 15 UserTrace BIP2638I: The MQ output node 'PL_170_OD_WMQI_1.DL.
MQSI.FAILURE' attempted to write a message to the specified queue 'DL.MQSI.FAILURE' connected to que
ue manager ''. The MQCC was 0 and the MQRC was 0.
2004-02-25 16:33:56.185564 15 UserTrace BIP2622I: Message successfully output by MQ output
node 'PL_170_OD_WMQI_1.DL.MQSI.FAILURE' to queue 'DL.MQSI.FAILURE' on queue manager ''.
2004-02-25 16:33:56.185980 15 UserTrace BIP2632I: Message received and propagated to 'out'
terminal of MQ input node node 'PL_170_OD_WMQI_1.SPL.DLNK.170.NEWWAY'.
2004-02-25 16:33:56.186112 15 UserTrace BIP6060I: Parser type 'Properties' created on beha
lf of node 'PL_170_OD_WMQI_1.SPL.DLNK.170.NEWWAY' to handle portion of incoming message of length 0
bytes beginning at offset '0'.
2004-02-25 16:33:56.186412 15 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of
node 'PL_170_OD_WMQI_1.SPL.DLNK.170.NEWWAY' to handle portion of incoming message of length '364' by
tes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2004-02-25 16:33:56.186564 15 UserTrace BIP6061I: Parser type 'BLOB' created on behalf of
node 'PL_170_OD_WMQI_1.SPL.DLNK.170.NEWWAY' to handle portion of incoming message of length '4979' b
ytes beginning at offset '364'. Parser type selected based on value 'NONE' from previous parser.