IBM Support

Start Database Monitor (STRDBMON) command filtering improvements

News


Abstract

Start Database Monitor (STRDBMON) command filtering improvements

Content

You are in: IBM i Technology Updates > Db2 for i - Technology UpdatesDb2 for i Security Enhancements > Start Database Monitor (STRDBMON) command filtering improvements

STRDBMON

A filter operator has been added to three STRDBMON parameters.

Job name (JOB)

Specifies the job(s) for which the database monitor is to be started.

  • Element 2: Filter operator
    The filter operator makes it possible to avoid starting a database monitor for specified jobs.
    *EQ
    The database monitor will be started for the specified jobs.
    *NE
    The database monitor will be started for all jobs that are not equal to the Job Name rule. For example, to start a database monitor for all jobs where the job name does not begin with QZDA use the *NE operator.
    STRDBMON OUTFILE(MONLIB/DBMONFILE)  JOB(*ALL/*ALL/QZDA* *NE)

Filter by database file (FTRFILE)

Specifies a filter based on the name of the file and library used within the SQL statement. The files used in the SQL statements will be compared to the files specified. The specified file name can be either the 10-byte short name or the 256-byte long name.

  • Element 2: Filter operator
    Specifies the rule for how each filter should be applied. The filter operator makes it possible to filter on matched values or unmatched values. If multiple filter values are specified, the filters which use *EQ are logically combined with an OR predicate while the filters which use *NE are logically combined with an AND predicate.
    *EQ
    Monitor records will be created when the filter criteria produces a matching result.
    For example, to capture the SQL statements executed using the file LIB41/TABLE01 use the *EQ operator.
    STRDBMON OUTFILE(MONLIB/DBMONFILE) JOB(*ALL/*ALL/ALL) FTRFILE((LIB41/TABLE01 *EQ))
    *NE
    Monitor records will be created when the filter criteria is not equal to the files specified in the SQL statement.
    For example, to capture the SQL statements executed using files like LIB41/TABLE*, but avoid capturing the statements if file LIB41/TABLE01, use the *EQ and *NE operators.
    STRDBMON OUTFILE(MONLIB/DBMONFILE) JOB(*ALL/*ALL/*ALL) FTRFILE((LIB41/TABLE* *EQ) (LIB41/TABLE01 *NE))

Filter by user profile (FTRUSER)

Specifies a filter based on a user or group profile name. The user executing the SQL statements will be compared to the profile filter criteria to determine if a monitor record hould be created.

  • Element 2: Filter operator

    Specifies the rule for how each filter should be applied. The filter operator makes it possible to filter on matched values or unmatched values. If multiple filter values are specified, the filters which use *EQ are logically combined with an OR predicate while the filters which use *NE are logically combined with an AND predicate.

    *EQ
    Monitor records will be created when the filter criteria produces a matching result.
    For example, to capture the SQL statements executed interactively by any user that is a member of the AUDITGROUP group profile, use the *EQ operator.
    STRDBMON OUTFILE(MONLIB/PRIVUSERS) JOB(*ALL/*ALL/QPADEV*) FTRUSER((AUDITGROUP *EQ))
    *NE
    Monitor records will be created when the filter criteria is not equal to the user executing the SQL statement.
    For example, to capture the SQL statements executed by any user that is a member of the AUDITGROUP group profile, but avoid capturing the statement if the user is DEVLPR1, use both the *EQ and *NE operators.
    STRDBMON OUTFILE(MONLIB/PRIVUSERS) JOB(*ALL/*ALL/QPADEV*) FTRUSER((AUDITGROUP *EQ) (DEVLPR1 *NE))

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Component":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

Document Information

Modified date:
21 January 2020

UID

ibm11167232