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 77

PDSE resource contention in a multi-tasking TSO BATCH environment

This is a former DCR MR0923135057 issued on 23th September 2013 and public RFE of private RFE 47867. According IBM this is already in implementation of next z/OS release. Under the existing z/OS architecture accessing a PDSE resource in a multi-ta...
almost 10 years ago in z/OS / TSO 3 Future consideration

Have JCL symbol for PDS submitted from

Have a JCL symbol to be the PDS where a job was submitted from. so I can have JCL like//MYJOB JOB// INCLUDE &mypds(DEFS)
almost 4 years ago in z/OS / TSO 0 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

TESTAUTH for 64 Bit addressing mode

The TESTAUTH functionality should also support programs with 64-bit addressing.
almost 6 years ago in z/OS / TSO 1 Future consideration

Allow definition of user's PREFIX in RACF TSO segment

Currently, a TSO User's prefix defaults to USERID. This is not suitable in all environmentsI would like the ability to specify a PREFIX in the TSO segment (for example, to set this to the user's DEFAULT group).The prefix is stored in the UPT Contr...
12 months ago in z/OS / TSO 3 Not under consideration

Enable default for VARSTORAGE to be HIGH

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

Need to remove 16Mb limitation for REXX variable.

We need to manage data by rds tables in System Automation for z/OS. In particular We need to read and processes by batch jobs, the data stored in the rds tables that are into system automation.But there is a limit around 16Mb. This number, 16Mb, i...
about 10 years ago in z/OS / TSO 1 Future consideration

Global (dynamic) Variables in REXX - and sorry, I couldn't find any category for this... I know that REXX is not XML :)

This would allow a very flexible communication between procedures. A global variable name in REXX would have a syntax like @abc@ (earmuffed) and would always refer to a variable in the main program and not in the current set of variables. It can b...
over 2 years ago in z/OS / TSO 1 Future consideration

Upgrade TSO STATUS command to support JES JOBGROUP

The TSO STATUS command is used to find the status of jobs previously submitted to JES. With z/OS 2.2, JES was enhanced with a new feature call JOBGROUPs. This feature allows jobs to be grouped together. Currently the STATUS command has very rudime...
about 1 year ago in z/OS / TSO 0 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

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.