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 Not under consideration
Workspace z/OS Connect
Created by Guest
Created on Apr 15, 2020

Add additional properties to policy rules

Today with z/OS Connect policy files you can only use headers to make a decision on which CICS transaction and connection to use. What we are needing is a way to use the headers and other information such as the API operation, path, method e.g. to determine in our case which CICS transaction to use.

In our example we could have one API that provides many operations such as getCustomerInfo, updateCustomerInfo, createCustomer. Having many operations in a single Customer API we need to be able to specify a different transaction to use based on the operation.

The alternative is to create many API's with less operations with individual rules per operation. This approach seems very limited and you end up doing "un-natural" API design because of the current limitations

Idea priority High
  • Guest
    Reply
    |
    Jun 29, 2020

    Whilst this requirement is valid, based on our current plans and priorities for IBM z/OS Connect Enterprise Edition, it is not likely that this could be implemented in the next 12 months. Correspondingly this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

  • Guest
    Reply
    |
    Jun 8, 2020

    We met with the raiser who clarified the use case as follows:

    There are many callers of the API eg Mobile, Branch, Online etc. On any given operation there are unique transaction codes that correspond to each caller. These codes are used downstream for both tracking and routing through the system. Callers set their ID in a header of the API request. Policy rules can be used to filter on this ID and set a transaction code accordingly. The problem is, at the moment a rule can only be applied across all operations in the API so, for instance, if OperationA requires XOAM, XOAB or XOAO (for Mobile, Branch and Online) and OperationB requires XOBM, XOBB or XOBO then there is no way to have a policy rule that will set the transcodes correctly in both cases and so they have to be moved into separate APIs.

    If other have a similar use case please comment and/or vote on this RFE.

  • Guest
    Reply
    |
    May 20, 2020

    Thank you for raising this requirement. Would you consider achieving this by defining a service (on which you can set the TraqnID and Connection) for each of the invocation styles?
    The following link will guide you through the steps -
    https://www.ibm.com/support/knowledgecenter/SS4SVW_3.0.0/designing/service_compose_interface.html
    If defining as a service doesn't meet your requirements please feedback your reasons.