Set up your environment prior to customization

Prior to beginning the customization process, ensure that your environment meets all requirements, that you have installed all prerequisite software, and that you have considered how you want to customize optional features.

Verify that your environment meets software requirements

  • Ensure that you are using z/OS V1.12 (5694-A01) or later.
  • Ensure that you are using one of the following supported versions of Db2 for z/OS:
    • Db2 V9.1 (5635-Db2)
    • Db2 Value Unit Edition V9.1 (5697-P12)
    • Db2 V10 (5605-Db2)
    • Db2 Value Unit Edition V10.1 (5697-P31)
    • Db2 V11 (5615-Db2)
    • Db2 Value Unit Edition V11.1
  • Additionally, make sure that the following FEC maintenance are applied:
    • FEC APAR PK43912
    • FEC APAR PK76167
    • FEC APAR PM06651 (required for Db2 V10 and later)

Verify that Log Analysis Tool has been installed successfully

See the Program Directory for IBM Log Analysis Tool for z/OS, GI10-8772-03 for installation instructions.

The IBM Tools Base for z/OS (5655-V93), which is available free of charge, provides a standard approach to customizing IBM Db2 for z/OS Tools. See the Program Directory for IBM Tools Base for z/OS, GI10-8819 for installation instructions.

Verify that your environment meets security requirements

The primary user interface to Log Analysis Tool is through its ISPF application, which has multi-factor authentication (MFA) support through TSO logon processing. All authentication is done before Log Analysis Tool is invoked and no additional MFA processing is necessary.

All batch jobs created by Log Analysis Tool and submitted for execution inherit the ID that has already been authenticated by the submitter. The Db2 services that are used by Db2 Log Analysis Tool are invoked using the standard attachment facilities.

Log Analysis Tool requires no extra security measures outside of standard Db2 security. If a user does not have authority to view a table within a Db2 subsystem, Log Analysis Tool will not allow the user to see data changes made to that table. Similarly, undo and redo SQL that generated from the product can be run through products such as SPUFI or QMF, and therefore also adheres to normal Db2 security for the user who runs this SQL.

You must have authorization to run the SELECT statement on the following tables:
  • SYSIBM.SYSAUXRELS
  • SYSIBM.SYSCOLUMNS
  • SYSIBM.SYSCOPY
  • SYSIBM.SYSFIELDS
  • SYSIBM.SYSINDEXES
  • SYSIBM.SYSKEYS
  • SYSIBM.SYSKEYTARGETS
  • SYSIBM.SYSTABLEPART
  • SYSIBM.SYSTABLES
  • SYSIBM.SYSTABLESPACE
  • SYSIBM.SYSXMLRELS
  • SYSIBM.SYSXMLSTRINGS
By default, Log Analysis Tool can run the REPORT utility against filtered objects. This activity is transparent to the user and can be disabled by setting the Misc Flags value on the general report panel to a value of X. If you do not disable this feature for any given run, you must have one of the following authorizations to access the REPORT utility through Log Analysis Tool:
  • RECOVERDB privilege for the database
  • DBADM or DBCTRL authority for the database
  • SYSCTRL or SYSADM authority