Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


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.

Status Delivered
Categories Usability
Created by Guest
Created on Aug 21, 2020

NonStop Connect Direct - RFE - SYSOPTS in a snode RUN TASK should be displayed always

If a snode sends a file to us and then makes a “run task” using TACL, then we cannot see what happens in this run task.

Only in case run task has CC > 0 then we see in the sysopts what was the infile that was started by this run task TACL.

But we have often the problem, that run task has CC = 0, but nobody can tell what was started. Even on the snode site

nobody can tell us, because it runs automatically or it is hidden deep inside of a script.

Do you think we would have a chance to get a parameter implemented, with which we could always see the sysopts of an externally started run task ?

What is your industry? Travel & Transportation
How will this idea be used?

If a snode sends a file to us and then makes a “run task” using TACL, then we cannot see what happens in this run task.

Only in case run task has CC > 0 then we see in the sysopts what was the infile that was started by this run task TACL.

But we have often the problem, that run task has CC = 0, but nobody can tell what was started. Even on the snode site

nobody can tell us, because it runs automatically or it is hidden deep inside of a script.

Do you think we would have a chance to get a parameter implemented, with which we could always see the sysopts of an externally started run task ?

  • Admin
    Chris Sanders
    Dec 27, 2021

    Thank you for your patience as we worked on this enhancement. I'm pleased to say that we were able to deliver this in v3.6.02 iFix27. Please visit our Fix Central website to pull down this or newer maintenance to start gaining the benefits of the enhancement.


    Sincerely,

    Chris Sanders

    Connect:Direct Offering Manager

  • Admin
    Chris Sanders
    Aug 28, 2020

    Thank you for opening this enhancement request with IBM. I have reviewed it in detail with my development team and we agree that this would be a worthwhile enhancement. I have accepted this as an uncommitted candidate and we will look to add it to the C:D NonStop roadmap moving forward.

    Sincerely,

    Chris Sanders

    Connect:Direct Offering Manager