Db2 for z/OS and its ecosystem

Db2 for z/OS and its ecosystem

Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems.

 View Only

More control for local applications with profile tables in Db2 13 function level 508

By Paul McWilliams posted 2 days ago

  

Db2 13 for z/OS continues to enhance flexibility for application developers. With function level 508, you can now control many settings for local applications by using Db2 profile tables—without changing your application code.

Db2 profile tables are used to monitor and control various aspects of a Db2 subsystem in specific application contexts, including the capability to specify special registers and global variable values for specific applications. Before Db2 13, profiles for setting special registers and global variables could only be applied to distributed applications.

However, the original Db2 13 release introduced support for controlling local applications with Db2 profile tables, but it was limited to just two new settings: the SYSIBMADM.DEADLOCK_RESOLUTION_PRIORITY global variable and the CURRENT LOCK TIMEOUT SPECIAL REGISTER. 

The ATTRIBUTE2 column values specify whether Db2 profiles table rows apply to local or remote applications for rows 'GLOBAL_VARIABLE' or 'SPECIAL_REGISTER' in the KEYWORDS column:

ATTRIBUTE2 = NULL - the profile applies only to remote applications.

ATTRIBUTE2 = '1' - the profile applies only to local applications.

ATTRIBUTE2 = '2' - the profile applies to both local and remote applications.

Starting in function level 508, profiles with KEYWORDS='GLOBAL_VARIABLE' can apply to local applications for following built-in global variables, which is the full set of built-in global variables that could already be controlled by the Db2 profile tables for remote applications. For descriptions of these global variables, see Built-in global variables.  

  • SYSIBMADM.MAX_LOCKS_PER_TABLESPACE
  • SYSIBMADM.MAX_LOCKS_PER_USER
  • SYSIBMADM.GET_ARCHIVE
  • SYSIBMADM.MOVE_TO_ARCHIVE
  • SYSIBM.TEMPORAL_LOGICAL_TRANSACTION_TIME
  • SYSIBM.TEMPORAL_LOGICAL_TRANSACTION

Also starting in function level 508, profile rows with KEYWORDS='SPECIAL_REGISTER' can specify SET statements for the following special registers and apply them to local applications. These are most of the special registers that can be controlled by the Db2 profile tables for local applications. For descriptions of these special registers, see Special registers.

  • CURRENT ACCELERATOR
  • CURRENT APPLICATION COMPATIBILITY
  • CURRENT DEBUG MODE
  • CURRENT DECFLOAT ROUNDING MODE
  • CURRENT DEGREE
  • CURRENT EXPLAIN MODE
  • CURRENT GET_ACCEL_ARCHIVE
  • CURRENT LOCALE LC_CTYPE
  • CURRENT MAINTAINED TABLE TYPES FOR OPTIMIZATION
  • CURRENT OPTIMIZATION HINT
  • CURRENT PRECISION
  • CURRENT QUERY ACCELERATION
  • CURRENT QUERY ACCELERATION WAITFORDATA
  • CURRENT REFRESH AGE
  • CURRENT ROUTINE VERSION
  • CURRENT RULES
  • CURRENT SQLID
  • CURRENT TEMPORAL BUSINESS_TIME
  • CURRENT TEMPORAL SYSTEM_TIME
  • ENCRYPTION PASSWORD
  • PATH
  • SCHEMA
  • SESSION TIME ZONE

By extending profile table capabilities to local applications, Db2 13 function level 508 provides developers and DBAs more flexibility to enforce settings without modifying application code. This enhancement not only streamlines configuration but also promotPes consistency across environments, making it easier to optimize performance and maintain control over complex workloads.

For more information about using these features, see the following topics in the Db2 product documentation:

#Db2forz/OS #Db2Z

0 comments
5 views

Permalink