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.
Extend the configuration control statements for Db2-supplied routines for program DSNTRIN with APPLCOMPAT a
Program DSNTRIN give the ability to pass some configuration control statement for DB2-supplied-routines as per the doc:
Configuration control statements for Db2-supplied routines
Configuration control statements supply the basic input for the DSNTRIN program, which installs and configures all routines that Db2 supplies.
Configuration control statements consist of a routine's schema and name (for stored procedures) or specific name (for user-defined functions), followed by customizable parameters. You can manually customize these parameters, but to save your settings and facilitate future migrations, specify changes using the Db2 routines: Advanced configuration options installation panels, which are accessed from the DSNTIPR1 panel.
The following parameters are used in configuration control statements:
The name of the WLM environment for running the routine. The default environment depends on the routine.
The authorization IDs allowed to execute the routine and use any associated tables or created global temporary tables. Separate multiple IDs with commas. Do not use blanks. The default is PUBLIC, which allows everyone to execute the routine.
The authorization ID to own the routine's package. The specified owner must have the privileges required to execute the SQL statements contained in the routine. If this parameter is specified for a routine that does not have a package, the parameter is ignored. If this optional parameter is not specified, the default package owner is the primary ID used to run DSNTRIN.
The general form of a configuration control statement is:
It will be helpful to have also the APPLCOMPAT as parameter to specify the level the customer wish to use.
Remember that this program run in the job DSNTIJRT that make a BIND (not REBIND) so the APPLCOMPAT assumed is the standard value derived from parameter:
of DSNZPARM that may be different from the setting made by the customer.
Do not place IBM confidential, company confidential, or personal information into any field.