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

Communications Server

Showing 524

SOCKS Configuration - Limitation

We have a problem with the SOCKS configuration in Mainframe that dont allow the use of DNS on the FTP server destination and only allow the use of IP Address. My concern here is that the network department setup rules on the SOCKS Server (the one ...
over 6 years ago in z/OS / Communications Server 2 Not under consideration

Make location of pids for communications server daemons configurable

Serveral of the CS daemon pids (e.g. /etc/syslog.pid, /tmp/pagent.pid) arewritten to directories /etc or /tmp and the location can't be changed. We think /etc is a configuration directory and no daemon should write to it. To /tmp everybody has wri...
almost 2 years ago in z/OS / Communications Server 1 Future consideration

Pagent support for TMPDIR variable

We need to be able to specify where to have pagent.pid and TCPIP.Pagent.tmp files stored. Currently they are stored in /tmp and there is no mechanism to change that. We have cron scripts which delete files in /tmp after xx days (of not being refer...
over 6 years ago in z/OS / Communications Server 0 Future consideration

zERT - Allow filtering for cipher suites

Please add a filter criteria for CipherSuites, like 009D or C027. So it is a quick view over used certificates, and we could reduce our AT-TLS rules for longer unused ciphers. Alternative would be a filtering with multiple parts, like AES_CBC_128 ...
12 months ago in z/OS / Communications Server 0 Future consideration

Full FTP Support for PDSE

FTP should support the transfer of PDS to a PDSE load library. There is no potential loss of data to be incurred from this in the way a PDSE to a PDS would be impacted. Currently this is not supported.
almost 8 years ago in z/OS / Communications Server 3 Not under consideration

EE over IPv6 needs to use the larger MTU of Jumbo OSAs or HiperSockets

When EE goes over IPv4 then it uses the available MTU provided by the OSAs or HiperSockets. Did you know that EE over IPv6 does not? It constrains itself to an MTU of 1100 bytes, even though OSPF is telling us the the available MTU is 8192 for Jum...
about 5 years ago in z/OS / Communications Server 1 Not under consideration

VARY SYNTAXCHECK for OMPROUTE configuration file

OMPROUTE had failed with the following configuration statements:; Interface IP_Address=a.b.c.d Name=interface1 Subnet_Mask=255.255.255.0 Destination_Addr=0.0.0.0 RIP_Interface IP_Address=a.b.c.* Name=dummy Subnet_Mask=255.255.255.224 EZZ7830I SYNT...
about 5 years ago in z/OS / Communications Server 3 Not under consideration

Support creating PDSE V2 data sets in FTP Server SITE and Client LOCSITE command

Much to my chagrin, I found that I could not create a PDSE V2 data set using the available parameters in the SITE command, rather only a PDSE V1. I had to use the rather roundabout way of using DFDSS unload, FTP the unload file, then DFDSS reload.
about 2 years ago in z/OS / Communications Server 0 Future consideration

Make it easier to enabe FTP clients for AT-TLS, in environments that have a variety of FTP servers

For environments where z/OS FTP client users have to connect to a variety of different FTP servers - especially those that are managed by organizations outside of my enterprise - the need to change AT-TLS policy in order to protect the FTP connect...
over 12 years ago in z/OS / Communications Server 2 Future consideration

Loss of packet after VIPAROUTE implementation

Customer implemented VIPAROUTE and, when any target gets recicled, RTOP destination cache sets the smallest MTU among viable routes to the destination, causing the GRE headers exceeds the MTU size causing loss of packets between the distributor an...
about 5 years ago in z/OS / Communications Server 1 Not under 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.