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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to for resolution. For more information about IBM's Ideas program visit

Status Functionality already exists
Created by Guest
Created on Jun 1, 2021

Provide logging to stdout\stderr for MFT redistributable package

For containerised environments with a centralised logging mechanism there is often a requirement to direct log output to stdout\stderr of the pid=1.

The log to file options currently provided by MFT include logic to rotate based on size\age which makes it impossible to 'redirect' the files.

Case TS005617616.

Idea priority Medium
Use Case
Expose runtime arguments to allow the log data (e.g. output.log, pcevent.log, capture.log, stderr.log and stdout.log) to be printed to the containers stdout. No management of files is required for this option.
RFE ID 150771
RFE Product IBM MQ
  • Admin
    Mark Taylor
    Aug 24, 2021

    The comments here describe what is already available, which is at least a partial solution to the requirement. There are no current plans to do anything further in this area

  • Guest
    Jun 21, 2021

    Thank you.

    As of now contents of output0.log and pcevent0.log are displayed on the console. Contents of capture0.log are not displayed on console.

    You may also want to have a look at MFT Container image published in DockerHub at

    Thank you

  • Guest
    Jun 18, 2021

    Thanks, this sounds promising. I'm assuming this will also include the capture0.log (which we enable). How about the stdout\stderr files, will they also output to console? I will test this and update this RFE with my findings.

  • Guest
    Jun 17, 2021


    Further update: Using -F with fteStartAgent command, events that were written pcevent0,log file, are output console. So you have both output0.log and pcevent0.log events displayed on the console.

    Hope this helps.
    Thank you

  • Guest
    Jun 17, 2021



    By default agent runs as daemon. However there is a documented option, -F to run agent in foreground. This option can be specified when starting an agent using fteStartAgent command, for example fteStartAgent -F . Option is case sensitive, so you must use upper case 'F'. When running in foreground agent outputs messages to console. This includes the event messages logged to agent's output0.log file.

    Could you please look at using the 'F' opion and see if that helps? Yes, it does not display contents of other log files like pcevent.log etc. I think you would be mostly interested in events logged to agent's output0.log file.

    Thank you.