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.

ADD A NEW IDEA

IBM Tivoli Advanced Allocation Management for z/OS

Showing 6

Enable DISP=MOD usage identification

When DISP=MOD is coded in JCL whether the dataset exists or not determins if DISP=MOD may actual be treated as DISP=NEW. AAM should be able to detect when DISP=MOD is being treated as DISP=NEW and take appropriate action.
8 months ago in IBM Tivoli Advanced Allocation Management for z/OS 0 Planned for future release

Allow selection criteria based on current volume attributes

AAM should be able to leverage the current volser attributes to be used as selection criteria in order to determine if it is the best option for the current situation. This capability can enhance existing DFSMS Storage Group and volume selection r...
about 1 year ago in IBM Tivoli Advanced Allocation Management for z/OS 0 Planned for future release

Enable Extent number as a selection criteria

AAM currently tracks dataset extents in support of its secondary increase function. AAM should allow the current extent number to be used as a selection criteria in order to invoke product functions.
about 1 year ago in IBM Tivoli Advanced Allocation Management for z/OS 0 Planned for future release

Enable FORCE_EOV capability

When controlling dataset allocation under DFSMS it can be beneficial to influence volume selection within eligible storage groups by disallowing the selected volume. If AAM enabled a force EOV functionality it could leverage this capability in con...
about 1 year ago in IBM Tivoli Advanced Allocation Management for z/OS 0 Planned for future release

Enable exclude logic when defining a VGRP to AAM

When defining a VGRP to AAM it is only possible to define volsers and volser masks to include in the definition. AAM syntax should also allow volsers and volser masks to be excluded to simplify syntax.
over 3 years ago in IBM Tivoli Advanced Allocation Management for z/OS 0 Planned for future release

TAAM should not rely on the name of the STC to ignore DB2 data sets

TAAM by design does not process DB2 data sets. However in order to ignore these data sets, TAAM rely on the name of the DB2 STC. If this name is the default one, everything is fine however if the name has been customized by the customer then TAAM ...
about 9 years ago in IBM Tivoli Advanced Allocation Management for z/OS 1 Planned for future release

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.