New ZPARM for SYSTIMESENSITIVE Bind Option

Please reference CASE TS005056787 (Temporal Table access path in Plan_Table does not match dynamic explain). This bind option which is set for using a Temporal Timestamp Register was set with a DEFAULT to YES by IBM for all binds that exclude this Option, which for us is ALL of our static binds.

Recently we experienced many False negatives when using pathchecker and running our own home grown reports that read from our system level PLAN_TABLE that all of our packages explain data ends up. Our reports are showing misleading scans, index usage on Temporal History tables when a query CLEARLY DOES NOT access the temporal history data because it DOES NOT use the AS OF timestamp ....... in the query.

With this option set to YES, The DBRM will show two instances of the SQL statement for the exact same QUERYNO (one for base temporal and one for History temporal access) whether or not the query references the History temporal data.

Anyway, if you read through the referenced CASE, we are requesting for a ZPARM to allow the CLIENT to decide what the default for this Bind option should be, not IBM. The client best knows how this register will be or will NOT be used in their shop.

Bottom line, is the work around was NOT easy to change this bind option in ALL of our static programs referencing Temporal tables. A Mass rebind was NOT feasible as we found out that in order to change this option in a mass rebind, we need to TURN OFF PLANMGMT, which is not an option for us. So the only way we were able to do this is to work with our Changeman team to have them put in a change to force this option to NO for any program compiles/binds as they are changed for upcoming application releases. this is not a fast solution, but the only one we that was feasible for us to use.

IBM has been involved in this discussion in detail and recommended the same, that we open an AHA to get this ZPARM created for SYSTIMESENSITIVE Bind option.