Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 Future consideration
Workspace PowerHA for AIX
Created by Guest
Created on Dec 30, 2020

trustchk error message issued druiing bosboot after changing powerHA syncd value

On AIX 7.2.4.2 and powerHA 7.2.3.3 we receive a trustchk error message when performing bosboot after changing the synd value from the default value of 60 to 10.

Idea priority Medium
  • Guest
    Reply
    |
    Jan 28, 2021

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - PowerHA
    Component - PowerHA for AIX
    Operating system - IBM AIX
    Source - Client

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM AIX
    Component - Product functionality
    Operating system - IBM AIX
    Source - Client

  • Guest
    Reply
    |
    Jan 19, 2021

    Thanks for the clarification as to what exactly is being requested in the RFE. IBM will continue to review this request and update the RFE as evaluation progresses

  • Guest
    Reply
    |
    Jan 15, 2021

    If it were the case that rc.boot was edited I would never have submitted an RFE. The syncd value was changed by issuing the HA command /usr/es/sbin/cluster/utilities/clchsyncd - an IBM supplied command used to modify a parameter of an IBM product. This is why I feel IBM should address the issue.

  • Guest
    Reply
    |
    Jan 14, 2021

    AIX is not considering changing the warning message generated when performing bosboot after changing the synd value by editing rc.boot. AIX does provide the means to override the syncd interval for j2 filesystems, and that is the j2_syncByVFS tunable via the ioo command:

    Here is the output from the help command:
    > ioo -h j2_syncByVFS
    Help for tunable j2_syncByVFS:
    Purpose:
    Specifies the number of seconds to wait between calls to sync a JFS2 file system. This value supercedes the value specified on the syncd command line.
    Values:
    Default: 0
    Range: 0 - 86400
    Type: Dynamic
    Unit: seconds
    Tuning:
    The value specified for this control is the number of seconds between iterations of the sync processing. That is, the sync daemon will wait 'j2_syncByVFS' seconds between initiating calls to syncvfs for JFS2 file systems. This overrides the time specified on the syncd command line.

    question: If IBM were to enhance the ioo command such that the syncd value applies system wide regardless of the filesytem type, would that be sufficient to address the concerns in this RFE?