IZ08425: ENHANCEMENTS FOR DB2FMP

DB2 Version 9.5 Fix Pack 3b for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 1  for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 2a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 2  for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4  for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• Two enhancements are implemented in the fenced mode process
  (db2fmp) for better handling of the fenced threadsafe stored
  procedure calls:
  .
  You can enable and disable the db2agent caching
  db2fmp worker for both threadsafe and not threadsafe fenced
  mode processes.  You might consider this feature if the
  applications are using connection pooling and you want the
  fenced mode processes (FMPs) to be reused instead of
  having different FMPs associated to each of the db2agents
  that are servicing the connections.
  .
  You can also limit the number of threads that can run within a
  fenced mode process. When this limit is reached, a new fenced
  mode process will be started to support new requests, and the
  existing one will be able to service incoming calls once any of
  its threads is are returned to the pool.   You might consider
  using this feature if your threadsafe Java routines use a large
  amount of java heap.
  .
  Because these two DB2 registry variables
  DB2_AGENT_CACHING_FMP and DB2_MAX_THREADS_PER_FMP
  might have an impact on your overall system, contact DB2 Support
  for technical guidance for when to use them and how to enable
  them.
  

Local fix

Problem summary

• User affected: DB2 Fenced SP/UDF users
  Problem description: Enhancements for DB2FMP
  Problem summary: see details in APAR ERROR DESCRIPTION.
  

Problem conclusion

• First fixed in DB2 UDB Version 9.5 FP1 (s080328)
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IZ03666

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 UDB ESE SOL

• Fixed component ID

  5765F4102

Applicable component levels

• R820 PSY

     UP

• R910 PSY

     UP

• R950 PSY

     UP