IBM Support

PI70250: SYSTEM PROFILE MONITORING WILDCARD SUPPORT

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • DB2DDF DP1931 dp1931
    System Profile Monitoring Wildcard Support
    
    Additional keywords and symptoms:
    ************************************
    SPM DB2SPM
    

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: System Profile Monitoring Wildcard      *
    *                      Support.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    System Profile Monitoring Wildcard Support.
    
    Many customers have expressed the requirement to be able to
    specify a wildcard value for an IP address, DRDA product
    identifier, and AUTHID in the system profile monitoring table to
    represent the exception or warning to be applied against a
    "range" of IP addresses, DRDA product identifiers, and AUTHIDs.
    Currently, one would have to enter multiple profile rows for
    each specific IP address, DRDA product identifier, and AUTHID to
    be monitored.  Also, since the current means to specify a
    default for any IP address also implies a default for any
    LOCATION value, customers have also need to just default any IP
    address.
    

Problem conclusion

Temporary fix

Comments

  • DB2 for z/OS System Profile Monitoring has been enhanced to
    support the wildcard, asterisk '*', specification for a DRDA
    product identifier, and AUTHIDs. With respect to IP addresses,
    IPv4 or IPv6, TCP/IP subnet masking specification will be used
    to support wildcarding of an IP address. Further, the special
    IP adddress 0.0.0.0 (IPv4) or ::0 (IPv6) can be specified as
    the default IP address in the SYSIBM.DSN_PROFILE_TABLE LOCATION
    column value.
    
    Various areas of the DB2 for z/OS publications within the
    Knowledge Center needs updating to describe the new System
    Profile Monitoring Wildcard Support.
    
    DB2-supplied user tables
     o Profile tables
       o SYSIBM.DSN_PROFILE_TABLE
    
         Table1: SYSIBM.DSN_PROFILE_TABLE description
    
         A new paragraph or bulleted list additions must be added
         to the Description column for the following
         SYSIBM.DSN_PROFILE_TABLE columns:
          o AUTHID
            If multiple authorization IDs, which have a common
            prefix of characters, are to be monitored, then the
            column value specified would be the characters which
            are common for the authorization IDs followed by an
            asterisk ('*). For example, if the column value is
            'TEMP*', then any authorization ID which begins with
            TEMP (and including TEMP by itself), would match this
            profile specification.
    
          o LOCATION
            The list of possible items can now include the
            following:
             o An IPv4 subnet address which is the initial IPv4
               address of a subnet followed by the subnet prefix
               as follows: IPv4address/mm where mm is 8, 16, or 24
               and represents the number of initial bits of an IPv4
               address which belongs in the subnet.
             o An IPv6 subnet address which is the initial IPv6
               address of a subnet followed by the subnet prefix as
               follows: IPv6address/mmm where mmm is 16, 32, 48, 64,
               80, 96, or 112 and represents the number of initial
               bits of an IPv6 address which belongs in the subnet.
             o 0.0.0.0 or ::0 which represents any IP address
    
          o PRDID
            If multiple product-specific identifiers, which have a
            common prefix of characters, are to be monitored, then
            the column value specified would be the characters which
            are common for the product-specific identifiers followed
            by an asterisk ('*). For example, if the column value is
            'DSN*', then any DB2 for z/OS remote requester would
            match this profile specification.
    
    Managing DB2 performance > Managing system performance >
    Managing DB2 threads > Monitoring threads and connections by
    using profiles
     o Example profiles that monitor threads and connections
       The following rows should be added to the figure:
    
       Table 1. Sample profiles in DSN_PROFILE_TABLE
       ------------------------------------------------------------
       PID LOCATION                ROLE AUTHID PRDID COLLID PKGNAME
       18  null                    null null   DSN*  null   null
       19  null                    null USER*  null  null   null
       20  9.30.222.0/24           null null   null  null   null
       21  2001:DB8:ABCD:0012::/64 null null   null  null   null
       22  0.0.0.0                 null null   null  null   null
       ------------------------------------------------------------
       Note: The value of DSN* for the PRDID variable in PID 18 is
        a string in which the first three characters match DSN
        followed by the unique id. For example, PRDID='DSN10015' or
        any PRDID where the first three characters match 'DSN'.
       Note: The value of USER* for the AUTHID variable in PID 19 is
        a string in which the first four characters match USER
        followed by the unique user id. For example, AUTHID='USER8'
        or any AUTHID where the first four characters match 'USER'.
        or any AUTHID where the first four characters match 'USER'.
       Note: Setting the LOCATION column of PID 22 to ::0 produces
        the same effect as setting it to 0.0.0.0
    
     o Consider example threads that have the following attributes:
       .
       .
       .
       PRDID='DSN10015':
        The criteria of profile 18 matches the thread. DB2 applies
        PID=18 to evaluate whether to apply a threshold against this
        thread.
       AUTHID='USER8':
        The criteria of profile 19 matches the thread and DB2 will
        apply this profile to evaluate whether to apply a threshold
        against this thread.
       LOCATION='9.30.222.21':
        The criteria of profile 20 matches the thread since the IP
        address is part of the subnet range 9.30.222.1 to
        9.30.222.254. DB2 applies this PID=20 to evaluate whether
        to apply a threshold against this thread.
       LOCATION='2001:DB8:ABCD:0012:0000:0000:0000:0003':
        The criteria of profile 21 matches the thread since the
        device address (the last four groupings of numbers,
        0000:0000:0000:0003) is part of the subnet range
        2001:DB8:ABCD:0012:0000:0000:0000:0000 to
        2001:DB8:ABCD:0012:FFFF:FFFF:FFFF:FFFF. DB2 applies this
        PID=21 to evaluate whether to apply a threshold against
        this thread.
       LOCATION='192.168.0.103':
        The criteria of profile 22 matches the thread since the
        special IPv4 address of 0.0.0.0 will match any remote
        client IPv4 address to this profile. DB2 applies this
        PID=22 to evaluate whether to apply a threshold against
        this thread.
    

APAR Information

  • APAR number

    PI70250

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-05

  • Closed date

    2016-11-21

  • Last modified date

    2017-08-10

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

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

    UI42792

Modules/Macros

  •    DSNLAGNT DSNLILNR DSNLQDIS DSNLTACC DSNLTEXC
    DSNLTIPC DSNT1RSP
    

Publications Referenced
SC19406000        

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RB10 PSY UI42792

       UP16/12/06 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.



Document information

More support for: DB2 for z/OS

Software version: B10

Reference #: PI70250

Modified date: 10 August 2017


Translate this page: