IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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

Container Extensions (zCX)

Showing 33 of 3354

make it possible to adapt/customize the motd (Message of the day)

Customers require sometimes that the use of zCX adheres to customer policies & rules. They want to communicate this via motd.
over 1 year ago in z/OS / Container Extensions (zCX) 0 Future consideration

zCX - Externalize failure information to the joblog

Hello, zCX generates FFDC files when a problem is experienced and in the above case zCX restarted. There is no indication of the nature of the problem in the joblog, just that FFDC dumps were captured and zCX was restarted. We have to open a case ...
about 4 years ago in z/OS / Container Extensions (zCX) 0 Future consideration

ZCX / ZOS Communication Server should support multi-IP configurations

For Security-Reasons our firewall blocks traffic to "unusual" ports. So we would like to provide a zCX instance more then one IP like docker on x86 supports. So we can bind connections between host(zcx) and container based on IP-port combinations....
over 1 year ago in z/OS / Container Extensions (zCX) 0 Future consideration

zCX restart capability

Provide the ability to restart zCX. E-mails have been sent to the zCX team.
almost 3 years ago in z/OS / Container Extensions (zCX) 0 Future consideration

Specify ROOTVOLSER on upgrade workflow

Currently the ZCX upgrade workflow will allocate a new 4GB ROOT VSAM file (e.g. ROOT2) based on the current SMS attributes of ROOT (as per the documentation). This is a poor assumption on most systems as the workflow will fail if space is not avai...
over 2 years ago in z/OS / Container Extensions (zCX) 0 Future consideration

Command to display zCX memory SWAP, DATA and ROOT space usage

There is no command to display how much memory the zCX started task is using, or how much space is being used of the ROOT dataset; determining usage of SWAP and DATA is also difficult.This is separate from the within-docker commands to display ind...
over 3 years ago in z/OS / Container Extensions (zCX) 0 Future consideration

zCX Support combined LFAREA usage (2G/1M) if not enough LFAREA is available within one type

Currently, zCX supports the use of LFAREA. This reduces the overhead for TLB and increases performance for zCX. If zCX is configured to use LFAREA and there is not enough LFAREA available within one range (2GB, 1MB) then zCX falls back to 4K what ...
over 3 years ago in z/OS / Container Extensions (zCX) 0 Future consideration

Support Kubernetes for zCX

Add support for Kubernetes for zCX
over 1 year ago in z/OS / Container Extensions (zCX) 1 Not under consideration

Unable to connect to z/OS Container Extension(zCX) from the WAN

The zCX default bridge subnet 172.17.0.0/16 causes conflicts (sometimes and always in our case) to the WAN workstations IP addresses. We request an enhancement or user customisation to avoid subnet conflicts when identified.
over 2 years ago in z/OS / Container Extensions (zCX) 0 Future consideration

Restore Docker Daemon logging levels by suppressing confidential user config.json information

Currently the Docker Daemon dumps the contents of a user's config.json file into the zCX joblog (SYSPRINT) if there is a syntax error in the Dockerfile (e.g. missing "\" continuation on RUN command or perhaps other situations). The user's config.j...
over 1 year ago in z/OS / Container Extensions (zCX) 0 Future consideration

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.