This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
A requirement for larger messages to be supported in a future release of WMQ FTE.
The customer was unable to create large messages on z/OS queue using File to Queue . The state message is held on the SYSTEM.FTE.STATE. queue. This limits the maximum output message size that can be written to around 33MB as you observe. There is currently no way around this. Please raise a requirement if you would like larger messages to be supported in a future release. . WebSphere MQ File Transfer Edition does not automatically split messages if they are larger than 100MB as you observe. To split the files based on size you must use the -qs parameter on the fteCreateTransfer command. Due to the way that WebSphere check points transfers the state message for the transfer may need to store up to 3 times the maximum output message size worth of data. The state messages that are written to the SYSTEM.FTE.STATE. queue perstistently and may be up to 3 * maxInputOutputMessageLength + 1048576 bytes in size. There is one state message for each source and destination transfer. The size of the page sets needs to take this into consideration.
Do not place IBM confidential, company confidential, or personal information into any field.