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 May 31, 2017

API Properties & components link

About API Properties:
When a user is looking for an APi properties (From z/os connect EE server view) he can see some informations that are fine but non exaustive. It may be more interesting to have an overview about all files that are dependant (json, wsbind ...). For each file we are interessed by lenght, timestamp of deployement, user which made deployement and so on.

Idea priority High
  • Guest
    Reply
    |
    Sep 27, 2017

    This RFE has been evaluated by development, and because z/OS Connect EE APIs and Services are now deployed as self-contained packaged (.aar and .sar files), in well-defined and configurable locations, we deem this request to be no longer applicable.

    Iterative changes must be made in the input to the API or service project, the artefact regenerated using the API Toolkit or Build Toolkit, and re-redeployed. Environmental dependencies such as references to connections are resolved at runtime in the target server.