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

Pinned ideas

PINNED Respect $HOME/.config/go/env
After adding eval $(/path/to/goz-env) in .profile, each time I log in to OMVS, I get 3 or 4 lines about $COMPILER_PATH. Can you add config to turn this off, please? Second, even if I have $HOME/.config/go/env (per XDG spec), go env says that `go` ...
Share feedback 0

All ideas

Showing 8507

Include CPU consumed by API in interceptors

Customer needs to determine APIs with high CPU to target for tuning. The customer uses OMEGAMON for JVM for API monitoring and they would like CPU per API included in detail reports.
5 months ago in z/OS Connect 1 Future consideration

Support outbound CICS --> REST API (OpenAPI v3) calls using a containerized solution on OpenShift

Currently the exposure of OpenAPI 3 REST APIs inbound to z/OS is supported on openshift x86 containerized architecture. Outbound calls from CICS to the REST API (OpenAPI v3) instead require the runtime to be installed on z/OS. This generates a dup...
about 1 year ago in z/OS Connect 0 Future consideration

Prepare the PMT (Preserver Mirror Tools) to manage the registration/deletion of devices both at the Metro Mirro level and at the MGM level.

If I'm not confused, currently the PMT can only be run to be able to manage (high/low) devices at the Metro Mirror level. In a GDPS MGM3SITE (or MGM4SITE) environment, we can only use the PMT for the MTMM part. It would be interesting to be able t...
12 months ago in GDPS 5 Future consideration

Add Support for Multi-Target Global Mirror Introduced in DS8900F Release 9.4

This would allow us to take two distinct sets of Safeguarded Copies from a single environment, each set making use of different parameters. For instance, we could thus address the requirements of the business (captures every 30 minutes, kept for 1...
about 1 month ago in GDPS 0 Future consideration

Collect data provider info for outbound z/OS Connect server

As per TS017415564, Citi needs to send performance and other critical operational data for zOS connect outbound servers to zLDA. These includes but not limited to request URI/endpoint used, response received from provider and https codes.
about 1 month ago in IBM Z Operational Log and Data Analytics 0 Under review

OMEGAMON CICS Exit KOCOME00 always returns RC=0 for XMNOUT exit. It should return the previous exit program's RC if it's greater than the OMEGAMON exit's RC.

We have our own XMNOUT exit to suppress SMF110 records for CSMI and some exception records. Our exit works fine until we need to do OMEGAMON maintenance which does OMEG REMOVE and OMEG INIT. Normally the sequence of the XMNOUT program is KOCOME00 ...
4 months ago in IBM Z OMEGAMON for CICS / Product functionality 0 Future consideration

Programmatically Update Monitor INTERVAL Start via AUTLCP1

There is no way currently to accurately set the timer on an ad hoc basis. Essentially the timer starts when the Interval value is updated or when a master switch occurs. In our use case, we have set up alerts for Partial Captures via GEO2976I, but...
6 months ago in GDPS 1 Planned for future release

Option to prevent inadvertent use of LINKAGE-SECTION data items prior to establishing addressability

In a COBOL program, the LINKAGE SECTION is used to describe data structures that are made available to this program from another program or method. Addressability to these data structures are established in a variety of ways, such as via reference...
over 1 year ago in COBOL Compilers / z/OS 9 Future consideration

CICS & z/OS Connect Time inconsistent in report

When analyzing through CICS/PA a report of type ZCON we find discrepancies in the times that make it practically useless On one side, CICS appears in Local Time, but the z/OS Connect show the time in UTC. Could this not be unified? Also (obviating...
almost 2 years ago in CICS Performance Analyzer for z/OS / Runtime 6 Not under consideration

CopyOnce: too much frequent

As written in the manual "ZG246758" the restore procedure after an HYPERSWAP (scheduled or unattended) foresees 3 actions:1- START secondary on Master of MM;2- MGM3SITE_RESTORE;3- MGM3SITE_SWAP The 9th step of MGM3SITE_RESTORE_MT_RS* procedure for...
over 2 years ago in GDPS 1 Is a defect

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.