| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| LOG FULL EXCEPTION in esql not working as expected |
« View previous topic :: View next topic » |
| Author |
Message
|
| coxsteph |
 Posted: Fri Jul 13, 2012 2:45 am Post subject: LOG FULL EXCEPTION in esql not working as expected |
 |
|
Newbie
Joined: 01 Nov 2005
Posts: 3
|
Hi guys. Trying to use catch terminal error processing to handle transactionality whilst still logging exceptions to the windows event log/user trace.
I'm using the LOG EVENT FULL EXCEPTION code which should log the current exception (if there is one) to the event log.
However this functionality doesnt seem to work, I progress to a compute node connected to the catch terminal, my first line of code is as above and the exception generated in my event log is
BIP2951 (the default if not message is provided)
No inserts (10 ?'s), (the default when no values are provided).
I've looked around the forum the only query about this seemed to show the same behaviour way back at v6 but no resolution was mentioned. It looks like the functionality just isnt there (although is described in the docs). Any ideas, I'm in the process of raising a PMR but thought i'd check if anyone had resolved it here first?
If not any suggestions on how you would log the full exception to the stack trace with the associated error codes in the same way that the log is written if the catch terminal isnt connected?
Thanks in advance |
|
| Back to top |
|
 |
| mgk |
| Posted: Fri Jul 13, 2012 3:02 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hey, long time no see 
The docs for the LOG statement's FULL clause say:
| Quote: |
FULL
The complete nested exception report is logged, just as if the exception had reached the input node. If FULL is not specified, any wrapping exceptions are ignored, and only the original exception is logged. Therefore, you can have either a full report or simply the actual error report without the extra information regarding what was going on at the time. A current exception only exists within handler blocks |
This is because only within a HANDLER block is an exception in scope. Once you are down the catch terminal, the exception has been turned into the ExceptionList and is not longer available as an exception.
Kind Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| coxsteph |
| Posted: Fri Jul 13, 2012 3:04 am Post subject: |
|
|
Newbie
Joined: 01 Nov 2005
Posts: 3
|
| Can we get them to bold that in the docs? Sorry, I re-read about 20 times looking for some kind of catch like that. Thanks! I will make it in soon for a visit |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Jul 14, 2012 4:57 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| coxsteph wrote: |
| Can we get them to bold that in the docs? |
Click the little feedback button at the bottom of the page, and add another feather to the camel's back...  |
|
| Back to top |
|
|
| mkza.swe |
| Posted: Sat Jul 14, 2012 8:27 am Post subject: |
|
|
Novice
Joined: 04 Jun 2012
Posts: 16
|
| coxsteph wrote: |
| Can we get them to bold that in the docs? :) Sorry, I re-read about 20 times looking for some kind of catch like that. Thanks! I will make it in soon for a visit |
Ah, yeah I had the same experience before, trying to log an exception. Easy to misread that. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
