| Author |
Message
|
| kwelch |
 Posted: Tue Jun 24, 2003 8:20 am Post subject: error on msgset when deploying at execgrp |
 |
|
Master
Joined: 16 May 2001
Posts: 255
|
Hi,
Can anyone tell me why I would get an error on a messagest that is not used by either of my messageflows when I deploy at the Execution Group Level? I thought that when you deployed at the Execution Group you didn't deploy messagesets? This was a TEST msgset and did have legitimate errors but I don't understand why it would keep something else from deploying that has nothing to do with it. My resolution was to remove it from the Broker and delete it but I don't understand why this was necessary to do. We all make errors when we are developing and it shouldn't stop another developer from doing their work.
We are WMQI2.1 CSD2.
Karen |
|
| Back to top |
|
 |
| Craig B |
| Posted: Tue Jun 24, 2003 9:00 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003
Posts: 316
Location: UK
|
Although you logically assign a messageSet to the broker in the Control Centre, a copy of this is sent to each of the Execution Groups within that broker. This is because each execution group is a separate (DataFlowEngine) process in the system and therefore needs to keep a runtime copy that it can access. Therefore when you issue an execution group level deploy then this will pick up changes to message Flows and messageSets for that particular execution group.
_________________
Regards
Craig |
|
| Back to top |
|
|
| kwelch |
| Posted: Tue Jun 24, 2003 9:02 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Hi Craig,
But that is my point this messageset had nothing to do with any of the flows in the execution group I was deploying.
Karen |
|
| Back to top |
|
|
| Craig B |
| Posted: Tue Jun 24, 2003 9:12 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003
Posts: 316
Location: UK
|
Although your messageSet has nothing to do with the message flows in that execution group, a run-time dictionary still needs to be built for your messageSet and sent to that execution group. Unfortunately there is no way of deriving that your message flows do not use this messageSet. You may have specified in your MQInput node that you do not use these messageSets (by specifying a different parser) but these are just the defaults. An MQRFH2 header could specify this MRM messageSet at run-time, or a CREATE statements PARSE clause could use it, or an ASBITSTREAM function could use, and these could potentially be retrieved from an external source that is not known at runtime. Therefore the only option is to give it to the execution group should it ever need it. And to give it to the execution group it needs to build and deploy a valid runtime dictionary which means the messageSet needs to be valid and complete.
_________________
Regards
Craig |
|
| Back to top |
|
|
| kwelch |
| Posted: Tue Jun 24, 2003 10:16 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Craig,
Ok! I get it now! Thanks for the explanation.
Karen |
|
| Back to top |
|
|
|
|
