MQSeries.net :: View topic - Flows with MQInput hidden in a subflow non-deployable

Esa · Posted: Fri Dec 03, 2010 1:48 am Post subject:

Hello,

While adding a subflow to a brand new flow my toolkit started rebuilding the workspace. After that all flows that started not with an MQInput node but with a subflow containing an MQInput node had become non-deployable.
The flows are not visible in the bar file editor's prepare tab. Bar files already containing these flows throw them away when I try to rebuild.

I know that my workspace has became corrupt. I have restarted the Toolkit and cleaned the workspace several times but it does not help.

The Toolkit version is 6.1.0.8 and it is not a trial version.

Of course it is possible to make flows deployable by adding a dummy MQInput node, but it does not sound a feasible solution in an environment where most flows start with a subflow.

Does anybody know a way to fix this? I tried manually adding xmlns:ComIbmMQInput.msgnode="ComIbmMQInput.msgnode attribute to the Epackage element in the msgflow file - it did not help. I cannot not find any setting like "don't look for MQInput nodes in subflows" in Preferences, maybe it is hidden somewhere in workspace metadata?

I would hate to have to create a new workspace. I am currently working in an insanely set up version control environment where checking out all tens of projects and manually correcting project references would take hours.