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.
Enable cron within the containers and/or allow web console to schedule custom user jobs or scripts
Users and DBAs frequently use cron to schedule jobs to run off hours. For a federated data warehouse, where there are many teams, tables, and schemas, users and DBAs are expected to monitor their own tables, loads, runstats, and other maintenance and monitoring jobs. As each team runs independently, they need the ability to schedule and run their own jobs according to their team's business needs. As well, many historical customers have previously written scripts and jobs that should easily transfer to any appliance.
One attempted workaround was to introduce another server to run cron jobs. This idea proved to be very difficult as a remote server requires a password to connect to the database. Due to security, the passwords cannot be stored unencrypted. As a result, the only viable option appears to be to change AUTHENTICATION to CLIENT. However, this too is not a recommended best practice for any security mechanism.
Another possible workaround is to use db2 scheduling. Again this is not pratical to rewrite the many cron jobs that already exist. This is an overwhelming and expensive amount of rework for something that has been working for years as is without security or maintenance overhead.
Last, for some activities like RUNSTATS or other maintenance routines, AUTO MAINT routines were investigated. But this option does not prevent scheduling problems when "EXTERNAL TABLES" or CREATE TABLE AS SELECT" are attempting to run and lock system catalogs. As well, AUTO MAINT throttles the maintenance making it hard to estimate how long the commands will run with different workloads on many different tables.
Do not place IBM confidential, company confidential, or personal information into any field.