Posted: Thu May 20, 2010 5:54 am Post subject: ESQL PARSE WEIRED
Master
Joined: 05 Dec 2007 Posts: 296
I have a very weired problem. I am doing PARSING inside esql procedure. If I debug it works, if I don't debug it fails. I am using runtime 7 no fix packs.... Has anyone had this problem? The code works 100% fine
DECLARE mset CHARACTER 'ICIOCK4002001' ;
DECLARE mType CHARACTER 'Transaction';
DECLARE mFormat CHARACTER 'Text1';
Create LASTCHILD OF Environment.TEST DOMAIN ('MRM') PARSE(Environment.Data
OPTIONS parseOptions
SET mset
TYPE mType
FORMAT mFormat
ENCODING InputRoot.Properties.Encoding
CCSID InputRoot.Properties.CodedCharSetId
I'd suggest using a trace rather than debugger when you're parsing with message sets. I think parsing exceptions are discarded by the debugger, so it might look like it works when you run it with debugger.
Debug trace should help you to figure out what's going wrong.
Luke was not talking about the Trace node. He was suggesting that you should take a user trace.
That means running mqsichangetrace, mqsireadlog and mqsiformatlog.
The output is a text file that tells you exactly what the message flow is doing.
But leave the Trace node in the message flow - it will write its output to the user trace if you ask it nicely ( actually I think that's the default behaviour ).
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