PM94679: DB2 FOR Z/OS DSN_PROFILE_TABLES ROW FOR SPECIFIC USER IS ALSO COUNTED AGAINST THE ROW FOR ALL USERS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2DDF DB2SPM defect pm94679 dpm94679
  DB2 for z/os dsn_profile_tables row for a specific user may
  also be counted against the row for ALL users which could
  lead to the thread unexpectedly ending with abend 00E30504.
  
  -30081 from DSNLIENO could be returned to application  with a
  DSNT772I from DSNLILNR
  A Monitor profile exception has occurred issued in SYSLOG
  ***************************************************************
  Additional Symptoms and Keywords:
   DSNT772I MSGDSNT772I DSNLILNR 00E30504 RC00E30504
   dsn_profile_tables
   SQLCODE -30081 SQLCODE30081 SQLCODE30081N DSNLIENO
  

Local fix

• For a workaround, the customer can adjust the rows in
  dsn_profile_tables to remove specific rows or increase the
  allowed count.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Distributed Data Facility (DDF) users    *
  *                 who are using, or plan to use, DB2 for z/OS  *
  *                 System Profile Monitoring (SPM) support.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: The following problems are reported:    *
  *                      * A DB2 for z/OS server unexpectedly    *
  *                        rejects new connections with message  *
  *                        DSNT772I, csect DSNLILNR and reason   *
  *                        code 00E30504.                        *
  *                      * A DB2 for z/OS server intermittently  *
  *                        rejects new connections from          *
  *                        different DB2 for z/OS requesters on  *
  *                        the same z/OS LPAR.                   *
  *                      Remote client applications will likely  *
  *                      receive SQLCODE -30081.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The following problems are reported:
  * When an asterisk ('*') character value is specified for any
    profile monitoring filter criteria, DB2 uses the action
    attributes to control the monitoring of all connections or
    threads that do not match a more specific profile.
    For example, consider a SYSIBM.DSN_PROFILE_TABLE row that is
    populated with the LOCATION column set to an asterisk ('*').
    A corresponding SYSIBM.DSN_PROFILE_ATTRIBUTES table row is
    populated with the KEYWORDS column set to "MONITOR
    CONNECTIONS", the ATTRIBUTE1 column set to "EXCEPTION", and
    the ATTRIBUTE2 column set to a value of 10.  When such a
    profile is activated (-START PROFILE command), DB2 would
    collectively limit the maximum number of connections to the
    subsystem to a total of 10 connections, if no other specific
    (value is not an '*') profile was activated.
    However, when a specific value profile was also activated,
    the count of the connections which match its filter value is
    also erroneously applied against the threshold specified in
    the asterisk ('*') monitoring profile.  This error causes the
    DB2 server to unexpectedly reject inbound connections, as
    reflected by message DSNT772I DSNLILNR 00E30504.
  * Another case of client applications receiving unexpected
    connection failures occurs when those applications are
    utilizing different DB2 for z/OS requesters which operate
    on the same z/OS LPAR, and hence have the same source TCP/IP
    address.  When a DB2 for z/OS server receives a new
    connection, it cannot distinguish if a specific requesting
    client has reached its particular connection threshold or
    not.  The server can only determine if the threshold of
    connections has been reached from a particular TCP/IP
    address.  This could lead to connection requests being
    unexpectedly rejected when a monitoring connections profile
    is activated with a filter of a specific value or an asterisk
    ('*') value.
  When the connections are rejected by the DB2 for z/OS server,
  remote applications will likely receive SQLCODE -30081.
  

Problem conclusion

• DB2 server processing is changed as follows:
  * A filtering criteria value of an asterisk ('*') for a
    profile that monitors connections or threads will now be used
    as the separate threshold value for each connection or thread
    whose filtering value does not match a specific value profile.
    For example, if a threshold value of 10 is specified for a
    profile that monitors connections with an asterisk ('*')
    filter criteria, and no other specific value profile is
    activated, then any particular client connecting from any
    remote TCP/IP address would be allowed to establish up to 10
    connections to the DB2 server (as long as the CONDBAT
    subsystem parameter value is not exceeded).  If a specific
    value profile is also activated, the threshold of the
    specific profile will apply only against connections or
    threads whose filter value matches the specific profile.
    No other profiles will be examined or applied.
  * When a remote DB2 for z/OS requester attempts to connect to
    the DB2 for z/OS server, the requester's location name will
    now be used to match against any monitoring threads profile
    which has a specific location name style of value for the
    LOCATION filtering criteria.  For any other client type, the
    name of the requested server location will be used.
    This change cannot be used to limit the number of connections
    from a particular DB2 for z/OS requester location because
    DB2 must accept the connection in order to determine the
    requester's location name.
    Users can however impose a thread limit.  By activating a
    profile that monitors threads with a threshold of concurrent
    threads and a filter value to be matched against a requesting
    DB2 for z/OS location name, users can limit concurrent thread
    activity attributed to the requester DB2 for z/OS location.
  

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:

  UI23567 UI23568

Modules/Macros

• DSNLAGNT DSNLCTRC DSNLILNR DSNLIRTR DSNLQDIS
  DSNLQINA DSNLTACC DSNLTACT DSNLTEXC
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI23567

     UP14/12/18 P F412

• RB10 PSY UI23568

     UP14/12/18 P F412

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.