Posted: Thu Nov 22, 2007 3:07 am Post subject: Resource Manager Dictionary not found for message set
Newbie
Joined: 09 Mar 2007 Posts: 4
i am having a problem while migrating message set from 2.1 to WBI 6.0.
The message set id has been changed(not same as specified in the message flow).It is deploying successfully but while putting message in the input queue it is throwing error like [quote]"The runtime dictionary resource for message set 'E0QO3CC08C001' has been requested by the broker in the function 'rmLoadDictionary' but the resource cannot be found as it is not registered. This means that the message set has not been deployed or has not been deployed properly.
The broker was requested to load a dictionary that has not been registered with it."[/quote]This is a run time error mainly.
I have changed the reference in flow and saved and redeployed but same error exist though the file is not read only.
Please help me how could i make it run successfully so that i can get message in the Output queue.
Everytime when migrating it is giving a new message set id and same error exist.I am using Windows XP and CSD 9 with all updates installed in toolkit for WBI6.0
Please reply
This one is easy. The MRM parser requires the following info:
- Message set name or identifier
- Message type
- Message format ( i.e. the name of the physical format )
It locates the deployed dictionary using ( message set identifier, physical format name ). If either of those are wrong, you get 'Resource Manager Dictionary not found'.
Check that your changes to the message flow are correct ( those 13-character identifiers are easy to mis-type ).
Check that the physical format name is correct ( from v5.0 they tend to have a '1' appended to them in new message sets ).
Tip : You don't need to use the message set identifier in v6.0. Use the message set name instead. It's simpler and more maintainable.
Joined: 18 Jul 2002 Posts: 381 Location: Gurgaon, India
Please confirm first that the flow & message set is running without errors in 2.1.
I have done a migration from 2.1 to 6 and did not have to change any message set id's in the flow.
Please search for all references of the old message set id in the .esql & .msgflow files.
Next, if this does not solve the problem, try a re-migration and make sure there are no errors.
Please make sure that the bar file has the correct message set and message flows before deploying. _________________ Shalabh
IBM Cert. WMB V6.0
IBM Cert. MQ V5.3 App. Prog.
IBM Cert. DB2 9 DB Associate
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