IBM Sterling Ideas

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

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

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 notifications 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.

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 ?

  • Guest
  • Aug 21 2020
  • Delivered
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 commented
    27 Dec, 2021 07:04pm

    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 commented
    28 Aug, 2020 06:24pm

    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

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.