The manufacturer of this Documentation is CA.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.
This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA.
The DB2 for LUW Audit Policy Editor closes.1 CA Database Management Solutions for DB2 for z/os Best Practices Guide VersionĢ This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation ) is for your informational purposes only and is subject to change or withdrawal by CA at any time. (Optional) Click the Notes tab to view and edit user notes.(Optional) Click the UDP tab to work with user-defined properties for the object.(Optional) Click the Where Used tab to view where the object is used within the model.(Optional) Click the Comment tab and enter any comments that you want to associate with the object.Success - Only successful events are audited. None - No events in this category are audited. You can specify a status for each category as follows:īoth - Successful and failed events are audited.įailure - Only failed events are audited. Specify options for audit policy categories on the General tab.Specifies whether or not to generate DDL for this object during Forward Engineering. Normal - Errors generated by the audit are ignored and only SQLCODEs for the errors are returned.Īudit - All errors are returned. Specifies the error type: Normal or Audit. Use the Enter filter text text box to filter a large list of names to locate the one you want to work with. Note: Click New on the toolbar to create an audit policy. Select an audit policy and work with the following options:.The DB2 for LUW Audit Policy Editor opens. Right-click an Audit Policy in the Model Explorer and select Properties.Note: This topic applies to DB2 for LUW versions 9.5 and 9.7 only. You can create an audit policy to determine what categories you want to be audited you can apply the policy to other database objects monitor the use of those objects. Creating Models › Target Servers for Physical Models › Database Property Editors › DB2 LUW Property Editors › Support for Security Features in DB2 LUW › Define a DB2 LUW Audit Policy