Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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
Categories Other
Created by Guest
Created on May 10, 2022

In a resource overrides .yaml file, allow multiple attribute values within a single selector clause to be OR'd.

Currently the logic would seem to support 1 attribute value on a given selector clause. If I have a resource attribute which can have many possible values and I want to trap some set of those values and apply the same override to each one, I have to specify a selector clause for each value. Being able to specify a list of values on a single selector clause would make the YAML much less cumbersome.

Looking at my original statement above I realise it is not particularly clear. I have looked at the 'selector mapping' topic, and I realise that multiple attributes may be specified for a given resource. In my case I am wanting to test for multiple possible values for a single attribute, and if any of the values is matched (in other words, ORing of the list), apply an override. I raised case TS009181319 and was informed that to do so I would need to code as per 'current approach' in 'additional details', whereas 'desired approach' seems simpler and more compact.

Idea priority Medium
  • Guest
    Reply
    |
    Jun 24, 2022
    This is a candidate for consideration for a future release.
  • Guest
    Reply
    |
    Jun 10, 2022

    I think I have already responded to the comment dated 12 May 2022, but I cannot find a date for my last update, so cannot be sure.

    In my instance I would like to test for multiple values of a single attribute, and the attribute type (ciphers) does not easily lend itself to wildcarding. There are a number of ciphers values which I would like to convert to a single value, thus being able to list them (as per my attached file) and have them OR'd such that any hit within the list would trigger the override, would make the logic more compact and easier to follow.

  • Guest
    Reply
    |
    May 12, 2022
    You can can specify more than one attribute. In addition we support wildcarding, and NOT condition-operators.

    Please see the section titled "Selector mapping (optional)" in https://www.ibm.com/docs/en/cics-ts/5.6?topic=file-resource-overrides-format

    Does this address the issue ?