A fix is available
APAR status
Closed as new function.
Error description
New function support for profile MONITOR ALL CONNECTIONS/THREADS
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All Distributed Data Facility (DDF) users. * * Specifically users of system profiles for * * the monitoring of threads and connections * * for remote TCP/IP access into Db2 for z/OS * * servers. * **************************************************************** * PROBLEM DESCRIPTION: * * This APAR adds the new MONITOR ALL * * CONNECTIONS and MONITOR ALL THREADS * * keyword functions to Db2 System * * Profile Monitoring. * **************************************************************** * RECOMMENDATION: * **************************************************************** Profile monitoring currently allows limiting the number of connections and threads, through the use of existing keywords MONITOR CONNECTIONS/MONITOR THREADS, for unknown applications on an individual IP address basis. However, it is not possible to limit the cumulative number of connections and threads from all unknown locations. An excessive number of unknown locations accessing Db2 can exceed system limits for connections or threads and cause an outage. A Db2 system administrator has no ability to limit the total number of dynamic or unknown applications from accessing Db2 concurrently which can drastically affect Db2 availability.
Problem conclusion
Temporary fix
Comments
New actions, MONITOR ALL CONNECTIONS and MONITOR ALL THREADS, are added to the KEYWORDS column of the DSN_PROFILE_ATTRIBUTES table. These new keywords can be specified for profiles that use the default location filtering criteria (DSN_PROFILE_TABLE - LOCATION column contains '*', '::0', or '0.0.0.0'). These keywords allow profile monitoring to enforce new warning and exception thresholds that apply to the cumulative number of connections or threads from across all locations that fall under the control of the default location profile. For more information about using profiles to monitor remote connections and threads, see the Db2 for z/OS documentation: https://www.ibm.com/support/knowledgecenter/en/SSEPEK_12.0.0/ admin/src/tpc/db2z_createprofiles.html
APAR Information
APAR number
PH30780
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
C10
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-10-21
Closed date
2020-12-15
Last modified date
2021-01-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI73152
Modules/Macros
DSNT1MNA DSNLAGNT DSNLQDIS DSNLSSST DSNLTEXC DSNTSTRT DSNLTACT DSNT1SDV DSNLCTRC DSNLILNR DSNLIRTR DSNT1MST DSNT1RSP DSNLEDDA DSNLQINA DSNLJTIN DSNLTACC DSNTGEPL
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RC10 PSY UI73152
UP20/12/17 P F012
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.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"12.0"}]
Document Information
Modified date:
05 January 2021