Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 z/OS
Categories BCP_XCF/XES
Created by Guest
Created on Jan 18, 2022

IXCMIAPU Should Be Updated to Return The Default Value of Each Structure Attriubte To The CFRM Policy Editor

The CFRM Policy Editor is intended to make it easier and more efficient to manage the CFRM policy. There are many Structure attributes that are assigned default values if the user does not assign a specific value. While those default values are shown in the Setting Up a Sysplex manual, it would be MUCH easier for users if the CFRM Policy Editor could show the default value.

It would not make sense to add all the default values to the Policy Editor - those values would then need to be maintained in two places. A better alternative would be if IXCMIAPU could return the default values in response to the request from the Policy Editor.

Additionally, it would be helpful to the user to know if the values they are presented with were hard-coded by a colleague, or if they were inserted by IXCMIAPU because the user did not specify that attribute. A flag could be added to the response from IXCMIAPU indicating which attributes had been coded by the user, and which were allowed to take the default value.

Idea priority Medium
  • Guest
    Reply
    |
    Apr 1, 2022

    Hi, Thank you for your help. And yes, this can be a complex topic. The following are just my opinions - voters should comment on which attributes would be the most important for them.

    Based on my experiences, the rough priority order (from high to low) would be:

    • INITSIZE and MINSIZE. I think that SIZE MUST be specified. INITSIZE will default to the SIZE value, but you could also hardcode the SIZE value as the INITSIZE, so clarifying that would help. Similarly for MINSIZE.

    • DUPLEX, so you can differentiate between a structure where the keyword was accidentally omitted, versus one where DISABLED was explicitly requested.

    • ALLOWAUTOALT

    • FULLTHRESHOLD

    • REBUILDPERCENT

    • ENCRYPT

    • ALLOWREALLOCATE

    • RECPRTY

    • The various NOTIFYDELAY attributes

    • ENFORCEORDER

    I hope this is a little help. Thank you for considering this.

  • Guest
    Reply
    |
    Feb 8, 2022

    .Are there specific CFRM CF/STRUCTURE keywords involved? This may not make sense (or may be too complex) for keywords in general. Here are some examples:

    - DUPLEX(DISABLED) is a default if DUPLEX is not specified. This is an easy case of a clear default. And the CFRM policy already keeps track of whether DUPLEX(DISABLED) was specified or DUPLEX(DISABLED) was taken as a default.

    - MINSIZE - the default for MINSIZE depends on the value of the ALLOWAUTOALT keyword (which has a default value of NO). This can be done, but thinking about the policy editor, it would mean that a change to ALLOWAUTOALT would need to drive IXCMIAPU in order to get the appropriate default MINSIZE value.

    - SITE - by default there is no SITE association. But other than mentioning nothing about SITE, there is nothing in IXCMIAPU syntax to represent no SITE association - there is no way to "explicitly specify no SITE association". EXCLLIST is similar to this.

    - To complicate things, many of the "defaults" are not taken by IXCMIAPU. Only an indication of "default taken" is stored in the CFRM CDS. The effective default gets applied by the XCF at the appropriate time.


    It would be good to understand if there are keywords of particular importance in order to prioritize and evaluate the feasibility and effectiveness of a solution.