| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Environment & LocalEnvironment |
« View previous topic :: View next topic » |
| Author |
Message
|
| ernest-ter.kuile |
 Posted: Thu Sep 19, 2002 6:55 am Post subject: Environment & LocalEnvironment |
 |
|
Apprentice
Joined: 13 May 2002
Posts: 49
Location: KLM Holland
|
Can Anybody tel me the reason why there is both an Environment and a LocalEnvironment ?
both seem to exist for the duration of one message.
Why do they co-exist ? In the documentation they are refered to interchangeably, however whatever you put in the first cannot be read back from the second.
Has the Environment content any special meaning like LocalEnvironment.Destination... has, or is the content of the Environment completly free to use.
are there any other differences ?
For a long time I thought they where synonymous, but I wasn't using Environment at all. Then I got ESQL code from somebody else which was refering to and setting values in the Environment which I couldn't read back later in a trace node, but could read back in a following compute node.
The error was obvious once I managed to escape my misconception that they where in the same thing.
Ernest. |
|
| Back to top |
|
 |
| kirani |
| Posted: Thu Sep 19, 2002 8:55 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Ernest,
Unlike LocalEnvironment tree there is only one copy of Environment tree is created for an instance of the message. This tree is also called as GlobalEnvironment Tree.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| whiting |
| Posted: Tue Sep 24, 2002 5:25 am Post subject: Environments |
|
|
Acolyte
Joined: 26 Mar 2002
Posts: 64
Location: Greenville, SC
|
The Local environment is a new name for the old destination list. If you make changes to the LocalEnvironment and the message fails later in the message flow then the changes will be rolled back along with the changes to the message. The Environment tree is not copied from node to node as Kiran points out, so if you make changes in that structure the changes will be available to any node that touches the message.
//Bill |
|
| Back to top |
|
|
| Miriam Kaestner |
| Posted: Fri Sep 27, 2002 2:05 am Post subject: |
|
|
Centurion
Joined: 26 Jun 2001
Posts: 103
Location: IBM IT Education Services, Germany
|
Environment is an intra-flow scratchpad area that is never used or touched by IBM primitive nodes.
LocalEnvironment has predefined structure and is used by certain IBM nodes, such as Aggregation nodes, RouteToLabel, MQOutput. You can use its Variables folder as user scratchpad area, too - like Environment.
BUT: In a Compute node, you must use InputLocalEnvironment or OutputLocalEnvironment and set Compute mode accordingly. This makes things more complicated and so you would prefer this to Environment only
- if you use CATCH terminal or TryCatch node to catch exception
- and want to set different values in LocalEnvironment.Variables for the Try and the Catch case. |
|
| 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
|
|
|
|
