PH24008: DEFAULT '*' THRESHOLD PROFILE WITH SET SPECIAL_REGISTER DOES NOTWORK AFTER APPLYING APAR PH12041 / PTF UI6 20/04/02 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• db2spm profilesys spm
  MONITOR THREADS profiles defined with a single-asterisk,
  ('*') that sets SPECIAL_REGISTER does not work after
  applying APAR PH12041 / PTF UI67630.
  
  
  This problem is also applicable to wildcarding
  such as AUTHID='USER*'
  
  
  
  Additional keywords and symptoms:
  *********************************
  DB2DDF DB2SPM SQLSPECIALREG
  SPME
  

Local fix

• Define a specific or exact MONITOR THREADS profile for
  setting the SPECIAL_REGISTER.
  
  Example:
   DSN_PROFILE_TABLE AUTHID='USERA'
   instead of AUTHID='*'
  
  or
  
   DSN_PROFILE_TABLE AUTHID='USERA'
  instead of AUTHID='USER*'
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Distributed Data Facility (DDF) users                    *
  * of Db2 profiles to monitor connections and                   *
  * threads for remote TCP/IP access to a                        *
  * Db2 for z/OS server.  Specifically those                     *
  * who have applied PH12041 / UI67630.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * After applying PH12041 / UI67630,                            *
  * remote connections and threads                               *
  * monitored through Db2 profiles defined                       *
  * using a single asterisk wildcard value                       *
  * ('*') will not correctly set special                         *
  * registers or global variables.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  Db2 system profiles for monitoring connections and threads
  defined with an asterisk (*) value as the filtering criteria
  and the associated DSN_PROFILE_ATTRIBUTES row specifies
  SPECIAL_REGISTER (or GLOBAL_VARIABLE) for the KEYWORD
  column, will not correctly apply the special register (or
  global variable) value.
  This incorrect behavior is caused by a Db2 internal logic
  error (after applying PH12041 / UI67630 fix).
  Note: As a temporary workaround, define a profile with the
   specific (or exact) value for the filtering criteria.
  

Problem conclusion

• Db2 system profile monitoring has been changed to correctly
  apply profiles that are defined using a single-byte asterisk
  value ('*') which contains SET special register or global
  variable statement(s) for monitoring remote threads.
  

Temporary fix

Comments

APAR Information

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

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

  UI69272

Modules/Macros

• DSNLCTRC DSNLILNR DSNLIRTR DSNLAGNT DSNT1RSP DSNLEDDA DSNLQDIS
  DSNLQINA DSNLTEXC DSNLJTIN DSNLTACT DSNLTACC
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI69272

     UP20/05/07 P F005 {

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.