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.

ADD A NEW IDEA

Clear

Ideas

    Showing 319 of 9156

    UKO: /ukebase/server.xml improvments

    It would be easier to have the same timestamp in each log (joblog, syslog, messages.log, trace.log). Currently our zOS logs are in local time and the GUI logs are in UTC. Please add a variable to server.xml in /ukobase to set a timezone Another go...
    over 1 year ago in Enterprise Key Management Foundation / UKO for z/OS 0 Under review

    Allow OMITTED parameters in function identifier.

    The COBOL 2002 standard allows for the OMITTED keyword to be specified as a parameter to a function identifier. This should be allowed for Enterprise COBOL. It could be implemented in a manner similar to specifying OMITTED as a parameter in a CALL...
    over 1 year ago in COBOL Compilers / z/OS 4 Future consideration

    COBOL function hbound() for tables

    COBOL has no easy way to check a table index or subscript against the OCCURS [... TO] {n} TIMES value. You can define an OCCURS constant to check against, but this requires application maintenance correctly preserve the correspondence when the tab...
    about 5 years ago in COBOL Compilers 4 Not under consideration

    Dual Control for key management actions (n/Auth)

    A method for dual control is needed in EKMF Web, such that any action (request), for which dual control is required, requires two (or more) users to confirm the request before EKMF Web performs the action. These actions can be (but not limited to)...
    almost 3 years ago in Enterprise Key Management Foundation / UKO for z/OS 2 Planned for future release

    Key lifecycle management for old key versions

    This idea is related to EKM-I-70 After a key is rotated, there should be options to manage the lifecycle of the old keys. One option could be to set the old version of the key to inactive, so it can not be used for new encryption anymore
    12 months ago in Enterprise Key Management Foundation / EKMF Workstation / UKO for z/OS 0 Planned for future release

    User defined constants

    Implement user defined constants using the COBOL Standard "Constant entry".
    over 10 years ago in COBOL Compilers 8 Not under consideration

    JSON PARSE error handling improvements

    JSON PARSE error handling improvements - Expose messages and tokens to application code. It would be helpful if application logic can determine which PARSE messages to display or suppress. Also, message tokens can be useful in error handling in...
    almost 3 years ago in COBOL Compilers / z/OS 2 Not under consideration

    Add the hability to obtain ODO counter with the JSON PARSE statement

    As of now, when the API we call return a dynamical JSON array, we need to declare a COBOL array with a large number of occurences in order to be sure to retrieve all the data with the JSON PARSE statements. But, in most cases, the json array will ...
    about 5 years ago in COBOL Compilers 2 Not under consideration

    COBOL: free "ID" for datadefinitions (REST-Services)

    In REST-service-context „id“ is a common used keyword for indentification purposes. In COBOL it isn't possible to define such a variable, because it is an reserved word. ID is an abbreviation for IDENTIFICATION in IDENTIFICATION DIVISION and for t...
    about 6 years ago in COBOL Compilers 3 Future consideration

    GUI usability improvements for UKO

    We need to provide the UKO authorisation roles to a group of users with little knowledge of key management. They need a tool that is easy and intuitive to use. So the GUI needs to be clearer. I think it would be very useful if users of the UKO GUI...
    over 1 year ago in Enterprise Key Management Foundation / UKO for z/OS 0 Planned for future release

    By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
    Do not place IBM confidential, company confidential, or personal information into any field.