HELP WITH HANDLING THE RELEASE INCOMPATIBLE CHANGE FOR VARCHAR( DECIMAL), CAST (DECIMAL AS CHAR), CAST(DECIMAL AS VARCHAR)
Michael_D. 1100004WAH Visits (8993)
In Version 10, the formatting of decimal data has changed for the VARCHAR function and the CAST specification with decimal input and VARCHAR or CHAR output. There are two changes:
- Remove leading zero
flodubois 270000K6H5 Visits (1933)
Below is a set of optimiser-related DB2 system parameters (ZPARMS) and their V10 default values. If the setting of any of these system parameters in your environment does NOT match the V10 default, then please re-evaluate the setting before migrating to DB2 10 for z/OS. If you need special assistance from IBM, please open a problem record (PMR).
MACRO ZPARM DEFAULT V10
DSN6SPRM OPTIOWGT ENABLE
DSN6SPRM OPTIXIO ON
DSN6SPRM OPTXQB ON
DSN6SPRM STATCLUS ENHANCED
agburke 060001QPDN Visits (975)
Workload Sysplex Balancing takes things into account such as available CPU capacity, DB2 virtual storage, and enclave service class attainment as well as queuing. This is an excellent start, but you may reach a point where all of the DBATs are in use and WLM still reports that subsystem as a good candidate for new connections.
DBAs want to control the connection queue depth and the wait time for a queued connection to get a DBAT, and when these are exceeded the connection should be terminated. This would apply to data sharing groups using Sysplex Workload Balancing. To address this two new zPARMs MAXCONQN (depth) and MAXCONQW (wait time) are supported. In the case where these limits are reached after MAXDBAT has been hit, DB2 will cancel those new incoming connection requests. This allows the JCC driver to seamlessly route those connections to other DB2s in the data sharing group where they have a better chance of being serviced. This should not return an error to the connecting application if the reroute is successful on the first attempt.