Kulbir, >>>This sounds like another useful feature of MQSI 2.1. �I however have a couple of issues >>>with this approach: We would not be looking at doing the XML conversions in a single >>>compute node. �The data is moved to the destinationlist early on in a compound node used >>>by several message flows and put back into the correct place after all sorts of data lookups, >>>validation checks, etc have been performed. �I think we're talking about may be 4 nodes >>>later. We're using MQSI 2.0.2 with the latest CSD. �To get to MQSI 2.1 would mean a whole >>>load of extra testing that we would need to perform.
Given that you are dealing with messages up to 100mb, I would try to do all I could in a single Compute node, if at all possible, and really search for ways to limit the amount of the message data I am copying to different trees, given the potential performance issues involved in doing so. Especially with V2.1 and its support for partial parsing (where parsing only has to occur when message elements are referenced), given that your message tree is likely to be quite a bit larger than the unparsed message, the less you move it around, the better. Regards, Christopher Frank Sr. I/T Specialist - IBM Software Group IBM Certified Solutions Expert - Websphere MQ & MQ Integrator -------------------------------------------- Phone: 612-397-5532 (t/l 653-5532) mobile: 612-669-3008 e-mail: [EMAIL PROTECTED] Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
