Message flow porting considerations

If you have configured a message flow that runs on a broker on a distributed system, and you now want to deploy it to a broker that runs on z/OS®, you might have to take additional actions to port the flow successfully.

Consider the following resources and attributes:

WebSphere® MQ queue manager and queue names
WebSphere MQ imposes some restrictions for resource names on z/OS:
  • The queue manager name cannot be greater than four characters.
  • All queue names must be in uppercase. Although using quotation marks preserves the case, certain WebSphere MQ activities on z/OS cannot find the queue names being referenced.

For more information about configuring on z/OS, refer to the Concepts and Planning Guide section of the WebSphere MQ Version 6 information center online or the WebSphere MQ Version 5.3 book from the WebSphere MQ library Web page

File system references
File system references must reflect a UNIX® file path. If you deploy a message flow to z/OS that you have previously run on Windows®, you might have to make changes. If you have previously deployed the message flow to a UNIX system (AIX®, Linux®, Solaris, or HP-UX), you do not have to make any changes.
Related concepts
Message flows overview
Related tasks
Developing message flows
Related reference
Supported databases
Built-in nodes
Related information
WebSphere MQ Version 6 information center online
WebSphere MQ library Web page
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:39:45

ac09058_