Skip to Main Content
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

z/OS

Showing 2927

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

DIAG/AUTOIPL inconsistencies

While using another IBM product (TDMF), we discovered that AUTOIPL processing doesn't use the Unit Addresses consistently. The IPL address (derived from MVS(LAST)) works fine because it's gotten from the UCB, however the IODF Unit Address (contain...
over 7 years ago in z/OS / BCP_IOS 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

Add ICSF Flush command

Provide a mechanism to complete any remaining ICSF work in-flight to be executed just prior to lpar shutdown. This would be in lieu of actually stopping ICSF.
almost 3 years ago in z/OS / ICSF 1 Future consideration

Need SMFLIM to check for REGION=0M jobs (IEFUSI replacement)

Customer objective is to eliminate the use of IEFUSI and replace it's rules using SMFLIM. Currently they have coded in IEFUSI that all the JOBS should be changed to REGION=150MB, but those jobs that are coded with REGION=0M. These ones can use the...
over 5 years ago in z/OS / BCP_SMF 0 Future consideration

Allow RLSE using standard ISPF options for dataset allocations

In the process of doing a PoC for zEDC, we were allocating datasets several different ways using different parameters. One of the things that we found out is that using several of the standard ISPF functions such as 3.3, when you allocate a datase...
almost 6 years ago in z/OS / ISPF 1 Future consideration

Add ability to place comment in auditing of RACF commands

Would like capability to add a comment type keyword on any RACF commands and have that text written to SMF record "as is". Using a new keyword common to all RACF commands. Expected typical usage will be a reason text or tracking number.
over 6 years ago in z/OS / RACF 4 Not under consideration

SMP/E support of additional data element MCS types incorporating expanded use of NLS localization.

Data element MCSs describe elements that are neither macros, modules, or source. Any type of data element may be installed in any target or distribution library that meets documented requirements for data set organization, LRECL, and BLKSIZE. IBM ...
over 8 years ago in z/OS / SMP/E 1 Future consideration

Monitor the z/OS Language Environment Heap Usage

The usage/allocation of the LE Heap storage would affect the performance of the IBM CMOD product that is using it. In the reported case, when the LE Heap is not properly tuned, high CPU consumed by the CMOD address space is observed. Although the ...
over 6 years ago in z/OS / LE 0 Future consideration

AUTOIPL CHANGE for LPAR ACTIVATION

WE would like to have AUTOIPL processing incorporate a deactivate on activate of the lpar that is being REIPL. This should be and option in the DIAGXX member, like you now have for reconfigurable storage.This process is now been done by our BMCsof...
almost 6 years ago in z/OS / BCP_IOS 2 Planned for future release