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


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 updates on them if they matter to you. If you can't find what you are looking for,


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


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Functionality already exists
Workspace DataStage
Created by Guest
Created on Jul 15, 2020

Datastage Super Operator should have Run Now + Stop ability parameterised

In our production Datastage 11.5 environment we submit all of our jobs by using the command line from Linux scripts so that should only be submitted via an external scheduled job. This gives a degree of control over accidental updates to the production database.

Currently our support analysts need to be able to read jobs in order to debug them, so they have been given a super operator role. This means that they could also run a job from the Director or Designer that updates the production database which we don not want them to be able to do.

Obviously there will be some sites this wouldn't be a useful feature, and so would suggest it should be controlled by a project config parameter.

Equally it would be useful if developers could run jobs for possible de-bugging of jobs. We only give this access to a few SME's and for a limited time period.

Somehow our previous Datastage 8.5 production environment was set up so that no-one could use the Run Now, Stop or Reset functions - no errors were generated; just nothing happened. This was done by Cap Gemini when they installed it for us (we think)

Needed by Date Aug 14, 2020
  • Guest
    Reply
    |
    Feb 28, 2023

    This is an undocumented setting. Use at own risk.

    In DSParams, in Section InternalSettings, set OperatorLite=1.

    [InternalSettings]
    OperatorLite=1

    You have to edit the file manually, afaik the Administrator Client cannot set this particular variable.

    This downgrades the roles "Operater" and "Super Operator" so they have less rights. As Operator in OperatorLite Mode, you cannot Start, stop or delete jobs in the director.

    Unfortunatelly, you actually still can run jobs in the operations console, which I think is not how it's meant to be. There's a reason, why this one is undocumented and because of this non-balanced behaviour between ops console and direcor it also looks more like a workaround than a proper feature.


    If this setting is found, then the following actions will be disabled in the Director client for users with the DataStage SuperOperator role:

    • Delete

    • Batch creation

    • Editing

    • Saving

    • Deletion

    Also, the following actions in the Director client will be disabled for users with the DataStage Operator role:

    • Running a job:

      • Run now

      • Validate

      • Reset

      • Stop

      • Set parameter defaults

    • Scheduling a job:

      • Add to schedule

      • Reschedule

      • Unschedule

    • Job logs

      • Clear logs

      • Change log auto-purge settings

    • Cleanup job resources

    • Clearing job status file

    • Delete

    • Batch

      • Creation

      • Editing

      • Saving

      • Deletion

    • Resource Estimation and Performance Analysis

    • Message Handler management

    • Data Set Management

    • Running the Designer client

    • Adding custom tools

    • Setting error and warning limits

    • Setting process priority for jobs

    Also, if a project is marked as "OperatorLite" then users with the DataStage operator role for that project will not be able to access the project properties using the DataStage Administrator client.



  • Guest
    Reply
    |
    Jul 27, 2020

    Hi Scott,

    Thanks very much for the response. Unfortunately none of us seem to be able to access the link, and I can't find anything on the Operator Lite role using Google or searching the IBM docs.

    Is there anyway you could email me the info please? Assuming it isn't more publicly available elsewhere. Thanks very much

  • Guest
    Reply
    |
    Jul 20, 2020

    Thank you for your idea. There is some additional functionality be using OperatorLite role that should address this. https://supportcontent.ibm.com/support/pages/node/413203