Posted: Mon Mar 13, 2017 11:55 pm Post subject: probably a Bug in IIB
Novice
Joined: 27 May 2016 Posts: 13
I tried assigning values to the InputRoot in ESQL as below:
SET InputRoot.XMLNSC.msg.a = 2;
But an error was shown, which was expected.
But when I declared a reference variable for this path and assigned a value to it as below:
DECLARE ref_var REFERENCE TO InputRoot.XMLNSC.msg.a;
SET ref_var = 2;
It not only doesn't throw an error but also changes the value in InputRoot.XMLNSC.msg.a (which I was able to see while debugging).
To double confirm I also assigned this inputroot value to the outputroot and it worked.
So , is this a bug in IIB???? or there is an explanation for this?
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
This is not a Bug as you call it.
This is a feature that goes back years. To be honest, I've never had the need to want to mess up my input message tree like this. Most of us treat the Input* side of things as READONLY.
There are some posts here from some years ago where one of the developers explains the 'feature'.
I'd just learn this are carry on and treat the Input* side of things as READONLY and carry on. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
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