This describes how to create a new message definition from a COBOL data structure using the New Message Definition File wizard in the workbench.
Before you start:
To complete this task, you must have completed the following tasks:
Before you begin this task, you should be aware of the points listed below:
If you previously used the WebSphere MQ Integrator Version 2.1 COBOL importer to create a message model, you may find that the WebSphere Message Broker Version 6.0 importer does not produce exactly the same results. In particular, the Version 2.1 COBOL importer did not support as many COBOL constructs as WebSphere Message Broker Version 6.0, and the naming convention for Version 2.1 compound types is not the same as the naming convention for WebSphere Message Broker Version 6.0 complex types and groups. In a very few cases, the naming convention for Version 2.1 elements is not the same as the naming convention for WebSphere Message Broker Version 6.0 elements. If you created message flow ESQL in Version 2.1 to manipulate your COBOL-derived message model, and you have imported that ESQL into WebSphere Message Broker Version 6.0 using the mqsimigratemsgflows command, and you are now recreating your message model using the WebSphere Message Broker Version 6.0 COBOL importer, you should review your ESQL for correctness.
The steps below cover creating a completely new message definition file and overwriting the contents of an existing file.
To create a message definition file from a COBOL data structure:
When you have completed importing the COBOL file using the wizard:
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ad02930_ |