Best practices for Db2 for z/OS stored procedures with ODBA

In a z/OS application runtime environments for Db2 for z/OS stored procedures that use the ODBA subsystem, you can make certain key changes to improve performance, reduce hung threads, cut down on the overhead caused by recycling addressed spaces, and increase stability.

In addition to following existing guidance for designing stored procedures, consider the following recommendations:
  • Use the Open Database Manager (ODBM) component of the IMS Common Service Layer (CSL) to protect IMS from unexpected terminations of Db2 for z/OS stored procedures.
  • Do not design stored procedures that use parameters that can cause problems with ODBA, such as the Db2 for z/OS ASUTIME value.
  • Fast-running stored procedures that do not hold unnecessary database locks or issue more than one APSB call at a time within a DB2 thread improve performance and reduce the frequency of hung threads.
  • Adjust the values of IMS system parameters, such as the MINTHRD= and MAXTHRD=, in the IMS DFSPRP macro.
  • Configure your system to improve serviceability and activate key diagnostic data collection facilities to quickly collect all of the relevant diagnostic information and reduce the amount of time you need to troubleshoot ODBA problems.