Hi Mike Sorry I am responding so late. Another option you could use is to add to your ReTrieve statement: TO docname. This will then send your XML output to the &XML& file with no page breaks. Your syntax would be something like: EXECUTE "LIST filename criteria TOXML TO xmldocname".
Thanks Kurt Neumann; IBM Certified Solutions Expert U2 Support and Training @ Workgroup Work Phone: +2711 654 6175 Fax Number: +2711 654 6375 Cell Phone: +2782 825 5011 Website: www.utwo.co.za e-Mail: [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of HENDERSON MIKE, MR Sent: 08 June 2006 12:46 AM To: [email protected] Subject: [U2] FW: [UV] Change in behaviour of "EXECUTE ... CAPTURING" at 10.1.18 {Unclassified} Folks, We have been using "EXECUTE <RetrieVe statement that generates an XML output> CAPTURING STUFF" to generate XML statements in STUFF. We then pass the XML to a BizTalk server to update a number of other systems from our UniVerse system. This is done from a Trigger program when certain files change. This has worked fine on 10.0.15, but since I upgraded the Development server to 10.1.18, the STUFF variable gets a 'page feed' "<ESC>[H<ESC>[J" inserted every 24 lines. Not unreasonably, this upsets the MS XML parser in BizTalk! Note that this is a new feature, it never happened on 10.0.15. Does anyone know why this happens? - maybe I missed a uv.config file change in the upgrade? - maybe this is an exciting 10.1.x 'new feature' [AKA 'bug']? I know that changing the terminal page depth works, but the TERM verb is not allowed in Transaction State, and a Trigger is always in Transaction State. Unless there's a config change I can make, I can see three ways of fixing this quickly: 1) fiddling the TERM verb options in the VOC to allow it in Transaction State Nasty, will probably work, may have unexpected side-effects 2) Filter the STUFF variable to catch and discard these lines Crude, may increase the trigger running time significantly, but will work 3) Upgrade the program to use the brand-new-in-10.1 XMLEXECUTE verb. Documentation is sparse to non-existent, except for what the list has already found for me. Not sure I want to be that 'bleeding edge' for this important production application. And then of course, there's always 4) Upgrade again to 10.1.<pick a number>, the bug has been found and fixed Help! Thanks Mike The information contained in this Internet Email message is intended for the addressee only and may contain privileged information, but not necessarily the official views or opinions of the New Zealand Defence Force. If you are not the intended recipient you must not use, disclose, copy or distribute this message or the information in it. If you have received this message in error, please Email or telephone the sender immediately. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
