Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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.

Status Delivered
Created by Guest
Created on Jul 27, 2021

IDz File Manager SQL console SELECT Check for excessive data transfer from host

There is no check on the size of a result set, or blocking of results from executing a SELECT statement. I can execute a SELECT that returns > 25,000 rows. Other parts of IDZ (e.g. JES spool display and even displaying member lists) issue warnings if a large amount of data would be transferred from the host.
The behaviour should be configurable. Some clients might not want to prevent large select statements, whereas others would want the opportunity to interrupt a long-running query. I think that the client should be able to configure the maximum bytes to be returned on a query (maybe 0, the default, would mean no limit), and also to configure the behaviour when the byte limit is reached - e.g. Terminate or Prompt to Continue.

Idea priority Medium