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

TSO

Showing 75

Enable default for VARSTORAGE to be HIGH

Enable an option to specify a system-wide default for VARSTORAGE to be HIGH.
about 6 years ago in z/OS / TSO 0 Future consideration

Provide option to remove NEW PASSWORD field from TSO LOGON

Sites provisioning RACF passwords from web-based tools like ISIM need the ability to prevent the user from changing passwords via NEW PASSWORD fields. Other products provide this capability, but there is currently no capability in TSO to remove th...
over 6 years ago in z/OS / TSO 1 Future consideration

Enhance REXX MVSVAR to return more system-related data

All Enhancements related to Enterprise PLI GETSYSWORD/GETJCLSYMBOL should be also available in Rexx using MVSVAR function or equivalent. MVSVAR('STEPNAME') Stepname of active TaskMVSVAR('PROCSTEP') Procstepname if any MVSVAR('SMFID') SMF ID of Sys...
almost 7 years ago in z/OS / TSO 6 Future consideration

&TRIM

Can a &TRIM built-in function be added to CLIST? I am aware that you can use this:SET MYVAR = &MYVAR But, this does not work if an ampersand or math operator is contained in the variable. Instead, a do loop is needed. Similar functions may...
almost 7 years ago in z/OS / TSO 0 Future consideration

Enhance LISTDSI to display number of generations for PDSE V2 with member generations

LISTDSI should be enhanced to display the number of member generations for a PDSE V2 file with member generation support.
almost 7 years ago in z/OS / TSO 4 Future consideration

Support for YYYY/MM/DD format in REXX DATE() function

Can a new option be added to the REXX DATE() function that returns a date in YYYY/MM/DD format, as required by LMMSTATS CREATED4 format? Maybe DATE('S/')?
almost 7 years ago in z/OS / TSO 2 Future consideration

Display Line Number When CLISTs Terminate Due to an Error

Display the line number when a runtime CLIST error occurs. An example would be when a substr error occurs.
about 7 years ago in z/OS / TSO 2 Future consideration

&SUBSTR Pseudovariable

Changing the value of a variable in the middle of a string could be improved by allowing the use of &SUBSTR as a pseudovariable like can be done in PL/I. SET &OLDVAR = &STR(THIS RUN IS A LIVE RUN) So instead of using:&NEWVAR = &...
about 7 years ago in z/OS / TSO 1 Future consideration

REXX SAY should use PUTLINE

REXX Say should use PUTLINE when under TSO so that the results can be trapped using outtrap.
over 7 years ago in z/OS / TSO 2 Future consideration

Allow SYSDSN in CLIST/REXX to have NORECALL like LISTDSI

Currently if you use SYSDSN in a REXX/CLIST and the dataset is migrated, it needs to be recalled by the function. However, with LISTDSI there is an option for NORECALL to prevent that from occurring. With the inclusion of NORECALL as an option on ...
over 7 years ago in z/OS / TSO 1 Future consideration