Merative Ideas Portal

Shape the future of Merative!

We invite you to shape the future of Merative, 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 Merative team to refine your idea

Help Merative prioritize your ideas and requests

The Merative 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 Merative 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 Merative, 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.


Merative External Privacy Statement: https://www.merative.com/privacy

Add a new idea Subscribe
Status Future consideration
Categories Social Program Management Platform
Created by Guest
Created on Mar 27, 2018

RELATED IDEAS

Batch Documentation

The documentation for the batch framework behaviour is vague or incomplete.

There appears to be no documentation of the parameter ChunkMainParameters.processUnProcessedChunks
A description of the use case for this parameter can be found in the APAR http://www-01.ibm.com/support/docview.wss?uid=swg1PO00520 , however having this information in an APAR is not the correct location for this detail and it should be added to the official documentation for usage of the Batch framework.


The documentation for ChunkMainParameters.unProcessedChunkReadWait reads:
“The ChunkMainParameters.unProcessedChunkReadWait parameter controls the
wait time when re-scanning to detected unprocessed chunks once all the
chunks have been handed out to streams. Because this value typically has to be
tuned for productive use, so that the value is sensible relative to the transaction
time for each chunk, it is typically exposed as an EnvVar with a sensible default
value.”

The provided unProcessedChunkReadWait documentation is missing information:
• why this property is needed
• what happens after the wait is finished
• what are the consequences of setting it to an incorrect value.
I.e. It fails to explain meaning and importance of this field.

Customer Name New Zealand MSD
  • Attach files
  • Guest
    Reply
    |     Apr 26, 2018

    Hi Lucas,

    We acknowledge that this enhancement request has been accepted for consideration. It may not be delivered within the release currently under development and we have no short term plans to provide this enhancement. However, the theme is aligned with our current multi-year strategy and will be considered for a future release.

    IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting.

    IBM will update this request in the future.

    Thank you for your interest in the Cúram product.
    Eloise O'Riordan, Cúram SPM Offering Management team

  • Guest
    Reply
    |     Apr 5, 2018

    Hi Lucas,

    Thank you for your enhancement request.
    We require some further analysis to determine whether or not this enhancement can be considered in a future release.
    I will provide another response when our investigation is complete.

    Thank you,
    Eloise O'Riordan, Cúram SPM Offering Management team