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.
We have an IDAA loader job that disables the table prior to the load to IDAA. Upon successful load of # rows, Loader will end with RC = 0 and enable the table for acceleration again. If the same process is run multiple times and results in "no row...
We're using IDAA loader V 2.1 to run backups for very huge AOTs. When IDAA loader takes a backup from an IDAA AOT it uses SQL multirow fetch to transfer the data from IDAA into a z/OS sequential file. This may work fine for small AOTs. But in our ...
Today, HLOMAINT utility is not designed to find out what utilities are stuck or dead. To clean up those loader utilities, we run a SELECT * against HLOTB.HLOUSTAT table, review each utility, and run the HLOMAINT job to terminate the utilities one ...
Use separate HLQs for read-only and updateable product libraries in TCz
TCz should provide an option to allow a customer to specify different HLQs to separate read-only and updateable libraries during product customization. For security and auditing reasons, this separation is required.
IDAA LOADER job with RC=8 due to just one IDAA load fail
Some of our daily DB2 load Jobs are "DUAL MODE" (DB2 + 4 IDAAs) but we are having issues due to RC=8 when just one IDAA receives error . When the load is sucessful for DB2 and 3 IDAAs but abend for just one IDAA we want to receive at least RC=4 be...
missing parm for forceFullReload (or detectChanges="PARTITION") in IDAA loader
According to Stored Procedure Guide V7.1.7 :The forceFullReload attribute is deprecated because detectChanges="PARTITION" withoutpartition list has the same effect as forceFullReload="false", and omitting the detectChangesattribute and a partition...
Rollback changes to both accelerators if failure occurs loading multiple accels in one load statement
We have a situation where it is important to keep the data in synch on both accelerators, so we use one statement to load both accelerators. Real case: The data is loaded from OPERLOG logstream to shadow table every 15 minutes on two IDAA accelera...
Today, when we have a problem with a Load execution, we can use the BMC ISPF application to terminate the utility or use the DB2 TERM UTILITY command.When using Loader, there is no way to terminate a utility unless using the HLOMAINT Job .So, we n...
ADABAS - DB2 date & timestamp fields with a default value
Hello, Case number: TS005063737 ADABASINDATEFMT - ADABAS INITIAL DATE FORMAT - DEFAULT is ADA.
ADABASINDATEFMT - This parameter specifies the content of date and time fields for ADABAS. For Example : Consider if the date content is 0000-00-00 and...
Do not place IBM confidential, company confidential, or personal information into any field.