Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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

Post 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 product management 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 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Functionality already exists
Created by Guest
Created on Sep 7, 2018

Admin Tool MIG: User control over jobname in jobcard RFE 124524


Provide ability for user to specify a unique jobcard in the generated source and target jobs to relate to the member name generated.
Possibly something akin to the way Automation Tool provides ability for user to configure generated member names and jobcard names.

Use Case
For example, a MIG may generate source jobs<br/>XXXS1, XXXS2<br/>and target jobs<br/>XXXT1, XXXT2, XXXT3<br/>However they all share the same default job card which means they all run with the same jobname unless manually edited<br/>For automation we intend to schedule these jobs through zoSMF and need unique jobnames to match member names that can then be run and tracked in a zoSMF workflow.
  • Guest
    Dec 14, 2018

    Sent the update to the customer 

  • Guest
    Dec 14, 2018

    We have a longer term strategic plan to provide more REST functions in the tools.  In the mid-term, could you use REXX or some scripting to change the generated job names?