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.
use of SET CURRENT APPLICATION COMPATIBILITY for ONLINECHECK in db2sqljcustomize command
The SQLJ Profile Customizer command db2sqljcustomize (described in the DB2 11 for z/OS Application Programming Guide and Reference for Java) with the options -onlinecheck YES and -genDBRM is used to create a DB2 z/OS DBRM for a SQLJ Java program. The SQL in the SQLJ program is static.
The db2sqljcustomize command (in the IBM data server driver for JDBC and SQLJ) execute the onlinecheck step of the command with dynamic SQL in driver supplied package NULLID.SYSLH200. Maybe other NULLID packages are also involved in some cases.
In the actual implementation of the onlinecheck step there is no dynamic SET CURRENT APPLICATION COMPATIBILITY done before checking the SQL of the SQLJ program. Result is, that the value of APPLCOMPAT parameter of the package NULLID.SYSLH200 on DB2 for z/OS is used for onlinecheck of the SQL in the SQLJ program. This is not transparent for SQLJ programmers and the same value is used within the onlinecheck for all SQLJ programs. The onlinecheck step should execute a SET CURRENT APPLICATION COMPATIBILITY statement before onlinechecking. The onlinecheck step would be independent of the bind parameter of the NULLID.SYSLH200 package in the DB2 for z/OS. In addition the SQLJ programmer would get the chance to control the APPLCOMPAT value for her/his specific SQLJ program. There are some imaginable possibilities for the value (actual V11R1 or V10R1) of the SET CURRENT APPLICATION COMPATIBILITY command. A) It could be extracted from the bind parameters, which are specified in the db2sqljcustomize command option â€œ-bindoptionsâ€. B) Or it could be extracted from the recently provided db2sqljcustomize option â€œ-APPLCOMPATâ€ C) Or it could be extracted from a new db2sqljcustomize option. D) or otherâ€¦
Do not place IBM confidential, company confidential, or personal information into any field.