Before you start:
To complete this task, you must have completed the following tasks:
Also, before you begin this task, you should note 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 Business Integration Message Broker Version 5.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 Version 5.0, and the naming convention for Version 2.1 compound types is not the same as the naming convention for Version 5.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 Version 5.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 Version 5.0 using the mqsimigratemsgflows command, and you are now recreating your message model using the Version 5.0 COBOL importer, you are strongly recommended to 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:
Related concepts
Ways to create message definitions
Import from other model representations to create message definitions
Related tasks
Working with a message set project
Related reference
Import formats
Importing from COBOL: supported features
Physical properties for message model objects
Message model object properties
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ad02930_ |