PI68554: SYSTEM PROFILE MONITORING IMPROVE GRANULARITY OF MESSAGES

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• DCR DN1960
  See PI63531 for DB2 11 for z/OS.
  System Profile Monitoring Improve Granularity of Messages.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Distributed Data Facility (DDF) users.  Specifically     *
  * those with profiles to monitor threads and connections for   *
  * remote TCP/IP access to a DB2 for z/OS server.               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Improved granularity of System Profile Monitor messages.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Improved granularity of System Profile Monitor messages.
  

Problem conclusion

• DB2 for z/OS System Profile Monitor messages have been enhanced
  to provide more details of a thread that has exceeded a profile
  threshold. The additional information includes:
    ?  the logical unit of work identifier (LUWID)
    ?  thread related information
    ?  the IP address of the client application
  Existing System Profile Monitoring DSNT773I message is being
  modified such that it can now reflect multiple condition types
  rather than just IDLE THREAD TIMEOUT.  Example:
    DSNT773I csect-name SERVER DISTRIBUTED AGENT WITH
  LUWID=luwid-token THREAD-INFO=thread-information FOR
  LOCATION=location RECEIVED event-type WARNING DUE TO PROFILE
  ID=profile-id
  
    where event-type is (the type of profile threshold event that
  was exceeded):
    ?  MONITOR CONNECTIONS
    ?  MONITOR THREADS
    ?  IDLE THREAD TIMEOUT
  
  New System Profile Monitoring DSNT774I message is being added
  for Exception type conditions.  Example:
    DSNT774I csect-name SERVER DISTRIBUTED AGENT WITH
  LUWID=luwid-token THREAD-INFO=thread-information FOR
  LOCATION=location RECEIVED event-type EXCEPTION DUE TO PROFILE
  ID=profile-id
  
    where event-type is (the type of profile threshold event that
  was exceeded):
    ?  MONITOR CONNECTIONS
    ?  MONITOR THREADS
    ?  IDLE THREAD TIMEOUT
  
  To activate these messages, DB2 implements two new
  SYSIBM.DSN_PROFILE_ATTRIBUTES table ATTRIBUTE1 column values.
  They are, WARNING_DIAGLEVEL3 and EXCEPTION_DIAGLEVEL3.
  Specifying WARNING_DIAGLEVEL3 will cause System Profile Monitor
  to issue message DSNT773I when a warning condition has been
  detected. Similarly, specifying EXCEPTION_DIAGLEVEL3 will cause
  System Profile Monitor to issue message DSNT774I when an
  exception condition has been detected.
  
    Note: When specifying either WARNING_DIAGLEVEL3 or
  EXCEPTION_DIAGLEVEL3, DB2 System Profile Monitor will issue
  messages DSNT773I or DSNT774I every time a warning or exception
  occurs. As a result, a potential flooding of the system console
  with these messages may occur if an application continues to
  exceed their profile limits.
  
  To address the potential flooding of the system console, DB2
  will provide an alternate solution of capturing the thread
  detailed information via a new IFCID 406 trace record. The
  new trace record, will contain information of the thread that
  exceeds the profile threshold. Each IFCID 406 trace record will
  contain the profile-ID and the specific thread related
  information (THREAD-INFO information) in the record. Therefore,
  users have the option to opt out from utilizing the new
  WARNING_DIAGLEVEL3 or EXCEPTION_DIAGLEVEL3 values.  Instead,
  they can enable and start the ICFID 406 trace facility, and
  research on these records for the specific profile-IDs that are
  exceeding the profile thresholds. Furthermore, users have the
  choice of specifying WARNING_DIAGLEVEL3 or EXCEPTION_DIAGLEVEL3
  *and* have DB2 collect IFCID 406 trace records as well.
  
  Information about this new function will be included in the
  Information Management Software for z/OS Solutions Information
  Center (http://publib.boulder.ibm.com/infocenter/imzic) at a
  later date.
  

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:

  UI43272

Modules/Macros

• DSNLTACC DSNT1RSP DSNLEDDA DSNFCDIR DSNDQWHS DSNLTEXC DSNLIRTR
  DSNDQW05 DSNLAGNT DSNLILNR DSNWVINT DSNLQDIS DSNFTDIR
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI43272

     UP16/12/29 P F612

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.