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:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Option required for viewing complete formatted Advanced SQL in Object Profiles
There is currently no option available to (re)view the complete formatted Advanced SQL in an Automation Tool Object Profile.
The only option that is available is to view this SQL is using PF10 / PF11 from panel HAA£OPRU as 80 bytes or so at a tim...
Automation Tool incorrectly building RUNSTAT jobs when TS has NPSI being RUNSTAT
Unfortunately the product has been generating jobs incorrectly from the getgo for RUNSTATS. When using load balancing across 20 jobs, the partitions should be spread across the 20 jobs. This works when the NPSI is not having RUNSTATS. When the ...
Reorging a TS with NPSIs, SORT NPSI = AUTO, getting IGD17272I VOLUME SELECTION HAS FAILED FOR INSUFFICIENT SPACE FOR which resulted in DSNU3341I 171 01:39:59.85 DSNURPCT - CANNOT ALLOCATE SORT DATASETS WITHIN 255 LIMIT , REORG should change to SORTNPSI = NO to prevent abend
Reorg TS with NPSIs and SORTNPSI or zparm REORG_PART_SORT_NPSI = AUTO. Reorg decides to run with SORTNPSI YES which sorts all keys for NPSIs. Job is having issues getting DASD resulting in numerous:01.39.58 J0916868 IGD17272I VOLUME SELECTION H...
Reorging of TS with NPSI in the maintenance window causes increase elapsed time and shortage of DASD. Need the capability in HAA eliminate partitions over a certain row amount. We use 100M. Using this the reorgs do not abend. Each week the nex...
For RPN TS, each partition reorged need a separate IC tape drive, need a way to limit the number of tape drives per iteration of REORG for the IC
If 65 partitions of a RPN with NPSIs are being reorg at the same time, 65 IC tape drives would be required. That is excessive and probably all shops can't support that. Even when no NPSIs, this would be a problem. HAA generates LISTPARTS 4096 w...
HAA - PBR containing XML generated REORG that abended because XML running at the same time as an index in the base table containing the XML column in two separate jobs
Base table has index:Name Schema T DB Name TS Name Cols Rows Chks* * * * * * * *------------------ -------- - -------- -------- ------ ----------- ----MASTER_TRANS_MTR ZAP2 T DZAP2QR1 SQR1MTR 17 10 0XQR14MTRColumn Name Seq No O Col Type Length Sca...
HAA did not pick up the need for NPSIs to be reorged when TS was being reorged
SEMHNSA TS partition 278 having 2 NPSIs was triggered for REORG. HAA is run 6 times on Saturday and 4 times on Sunday since this TS is so large, 7 billion rows in some environments. REXX code rebuilds the RGNSA001 so that only 100M rows are reorge...
HAA$UREO - Max Tape Vols/DASD Units should be created on HAA$DSD as separate fields
Seems having Max Tape Vols/DASD Units is dangerous. These should be separated into two different entry fields. VOLCNT is tape volumes, UNCNT is units. Also these should not be on a general panel, HAA$UREO. This should be on HAA$DSD. The fields rea...
Do not place IBM confidential, company confidential, or personal information into any field.