Date:   June 20, 2002

Patch:  3.7.1-TEC-FP02

Component: Tivoli Enterprise Console 3.7.1

General Description:
  This fixpack PTF U482349 supersedes and contains APAR fixes from
  previous e-fixes and patches, as well as numerous other fixes to the
  Tivoli Enterprise Console, Version 3.7.1.

 **********************************************************************
 **********************************************************************

 NOTES:  It is very important to read all the notes in this README.

 * Consult your operating system reference manual(s) for operating
   system specific commands.

 * WARNING: Due to changes in the wtdbclear command, it is recommended
           that users make a backup copy of the wtdbclear binary file
           prior to installing this fixpack.  See the section on
           wtdbclear for details.

 **********************************************************************
 **********************************************************************

Patches superseded by this patch:

  3.7.1-TEC-0001
  3.7.1-TEC-0003E
  3.7.1-TEC-0004
  3.7.1-TEC-0005E
  3.7.1-TEC-0006E
  3.7.1-TEC-0008E
  3.7.1-TEC-0009E
  3.7.1-TEC-0010E
  3.7.1-TEC-0011E
  3.7.1-TEC-0012E
  3.7.1-TEC-0013E
  3.7.1-TEC-0014E
  3.7.1-TEC-0016E
  3.7.1-TEC-0017E

 **********************************************************************
 **********************************************************************

Prerequisites:

 Note:  The following must be installed prior to the installation
        of this fixpack.

    Tivoli Enterprise Console 3.7.1

    For Tier 2 enablement:
      3.7-TMF-0021
      3.6.1-TMF-0026
      3.6.1-TMF-0034
    
    For IBM Tivoli Netview 7.1.2 console enablement:
      IBM Tivoli Netview 7.1.2

 **********************************************************************
 **********************************************************************

Files Replaced or Added by this Fixpack
 (for all supported values of $INTERP):

   bin/wrb
   bin/wtdbclear
   bin/wtdumper
   bin/wtdumprl
   bin/wtdumptr
   bin/wtdbspace
   bin/wsetemsg
   TME/TEC/nvsync.sh
   TME/TEC/tec_config
   TME/TEC/tec_dispatch
   TME/TEC/tec_reception
   TME/TEC/tec_server
   TME/TEC/tec_rule
   TME/TEC/tec_rule_data
   TME/TEC/tec_task
   TME/TEC/tec_tasks.tll
   TME/TEC/tec_compile_rules_gui.sh
   TME/TEC/tec_rule_non_tme.tar
   TME/TEC/.tec_config
   TME/TEC/default_rb/.rbtargets/EventServer/TEC_TEMPLATES/$INTERP\
      /event_specifiers.wic
   TME/TEC/default_rb/TEC_TEMPLATES/$INTERP/event_specifiers.wic
   TME/TEC/default_rb/TEC_RULES/netview.rls
   TME/RULE_BUILDER/builder
   TME/RULE_BUILDER/builder_data
   bin/postemsg
   bin/wpostemsg
   bin/wtdbclear.pl
   TME/TEC/tec_rb.jar
   TME/TEC/nways.jar
   TME/TEC/nvsync.jar
   TME/TEC/tec_ui_svr.jar
   TME/TEC/tec_console.jar
   TME/TEC/tec_svr.jar
   TME/TEC/launch118.jar
   TME/TEC/tec_ui_server
   TME/TEC/tec_gateway.exe
   bin/aix4-r1/TME/TEC/adapters/bin/tecad_logfile
   bin/aix4-r1/TME/TEC/adapters/bin/logfile_gencds
   bin/hpux10/TME/TEC/adapters/bin/tecad_logfile
   bin/hpux10/TME/TEC/adapters/bin/logfile_gencds
   bin/solaris2/TME/TEC/adapters/bin/tecad_logfile
   bin/solaris2/TME/TEC/adapters/bin/logfile_gencds
   bin/linux-ix86/TME/TEC/adapters/bin/tecad_logfile
   bin/linux-ix86/TME/TEC/adapters/bin/logfile_gencds
   bin/linux-s390/TME/TEC/adapters/bin/tecad_logfile
   bin/linux-s390/TME/TEC/adapters/bin/logfile_gencds
   bin/aix4-r1/bin/wpostemsg
   bin/hpux10/bin/wpostemsg
   bin/solaris2/bin/wpostemsg
   bin/w32-ix86/bin/wpostemsg.exe
   bin/os2-ix86/bin/wpostemsg.exe
   bin/linux-ix86/bin/wpostemsg
   bin/linux-s390/bin/wpostemsg
   bin/w32-ix86/TME/TEC/adapters/bin/tecad_nt.exe
   bin/w32-ix86/TME/TEC/adapters/bin/tecadnts.exe
   bin/w32-ix86/TME/TEC/adapters/bin/sctlnt.exe
   bin/w32-ix86/TME/TEC/adapters/bin/nt_gencds.exe
   bin/w32-ix86/TME/TEC/adapters/bin/tecad_win.exe
   bin/w32-ix86/TME/TEC/adapters/bin/tecadwins.exe
   bin/w32-ix86/TME/TEC/adapters/bin/sctlwin.exe
   bin/w32-ix86/TME/TEC/adapters/bin/win_gencds.exe
   bin/w32-ix86/TME/TEC/adapters/bin/tecad_nt.exe
   bin/w32-ix86/TME/TEC/adapters/bin/tecadnts.exe
   bin/w32-ix86/TME/TEC/adapters/bin/tecad_win.exe
   bin/w32-ix86/TME/TEC/adapters/bin/tecadwins.exe
   bin/aix4-r1/TME/TEC/adapters/bin/tecad_logfile
   bin/hpux10/TME/TEC/adapters/bin/tecad_logfile
   bin/solaris2/TME/TEC/adapters/bin/tecad_logfile
   bin/os2-ix86/TME/TEC/adapters/bin/tecados2.exe
   bin/aix4-r1/TME/TEC/adapters/bin/tecad_snmp
   bin/hpux10/TME/TEC/adapters/bin/tecad_snmp
   bin/solaris2/TME/TEC/adapters/bin/tecad_snmp
   bin/w32-ix86/TME/TEC/adapters/bin/tecad_snmp

 Tier 2 enablement:
   bin/linux-ix86/TME/ACP/acpep
   bin/linux-ix86/TME/ACP/acpep_install
   bin/linux-ix86/TME/ACP/wacpadin
   bin/linux-ix86/TME/TEC/adapters/bin/wlocpath
   lib/linux-ix86/libstdc++-libc6.1-2.so.3
   bin/linux-s390/TME/ACP/acpep
   bin/linux-s390/TME/ACP/acpep_install
   bin/linux-s390/TME/ACP/wacpadin
   bin/linux-s390/TME/TEC/adapters/bin/wlocpath
   lib/linux-s390/libstdc++-libc6.1-2.so.3
   bin/mips-irix5/TME/ACP/acpep
   bin/mips-irix5/TME/ACP/acpep_install
   bin/mips-irix5/TME/ACP/wacpadin
   bin/mips-irix5/TME/TEC/adapters/bin/wlocpath
   lib/mips-irix5/libstdc++.so.2.10.0
   bin/osf-axp/TME/ACP/acpep
   bin/osf-axp/TME/ACP/acpep_install
   bin/osf-axp/TME/ACP/wacpadin
   bin/osf-axp/TME/TEC/adapters/bin/wlocpath
   lib/osf-axp/libStr272.so
   lib/osf-axp/libg++.so.2.7.2
   lib/osf-axp/libstdc++.so.2.7.2
   bin/reliant-unix/TME/ACP/acpep
   bin/reliant-unix/TME/ACP/acpep_install
   bin/reliant-unix/TME/ACP/wacpadin
   bin/reliant-unix/TME/TEC/adapters/bin/wlocpath
   lib/reliant-unix/libstdc++.so.2.10.0
   bin/sequent/TME/ACP/acpep
   bin/sequent/TME/ACP/acpep_install
   bin/sequent/TME/ACP/wacpadin
   bin/sequent/TME/TEC/adapters/bin/wlocpath
   lib/sequent/libstdc++.so.2.10.0
   bin/solaris2-ix86/TME/ACP/acpep
   bin/solaris2-ix86/TME/ACP/acpep_install
   bin/solaris2-ix86/TME/ACP/wacpadin
   bin/solaris2-ix86/TME/TEC/adapters/bin/wlocpath
   lib/solaris2-ix86/libstdc++.so.2.10.0
   bin/uw2-ix86/TME/ACP/acpep
   bin/uw2-ix86/TME/ACP/acpep_install
   bin/uw2-ix86/TME/ACP/wacpadin
   bin/uw2-ix86/TME/TEC/adapters/bin/wlocpath
   lib/uw2-ix86/libStr.so.2.7.2
   lib/uw2-ix86/libg++.so.2.7.2
   lib/uw2-ix86/libstdc++.so.2.7.2
   bin/linux-ix86/TME/TEC/adapters/bin/tecad_logfile
   bin/linux-ix86/TME/TEC/adapters/bin/logfile_gencds
   bin/linux-s390/TME/TEC/adapters/bin/tecad_logfile
   bin/linux-s390/TME/TEC/adapters/bin/logfile_gencds
   bin/mips-irix5/TME/TEC/adapters/bin/tecad_logfile
   bin/mips-irix5/TME/TEC/adapters/bin/logfile_gencds
   bin/osf-axp/TME/TEC/adapters/bin/tecad_logfile
   bin/osf-axp/TME/TEC/adapters/bin/logfile_gencds
   bin/reliant-unix/TME/TEC/adapters/bin/tecad_logfile
   bin/reliant-unix/TME/TEC/adapters/bin/logfile_gencds
   bin/sequent/TME/TEC/adapters/bin/tecad_logfile
   bin/sequent/TME/TEC/adapters/bin/logfile_gencds
   bin/solaris2-ix86/TME/TEC/adapters/bin/tecad_logfile
   bin/solaris2-ix86/TME/TEC/adapters/bin/logfile_gencds
   bin/uw2-ix86/TME/TEC/adapters/bin/tecad_logfile
   bin/uw2-ix86/TME/TEC/adapters/bin/logfile_gencds
   bin/linux-ix86/bin/wpostemsg
   bin/linux-s390/bin/wpostemsg
   bin/mips-irix5/bin/wpostemsg
   bin/osf-axp/bin/wpostemsg
   bin/reliant-unix/bin/wpostemsg
   bin/sequent/bin/wpostemsg
   bin/solaris2-ix86/bin/wpostemsg
   bin/uw2-ix86/bin/wpostemsg
   bin/linux-ix86/bin/wstoptecgw
   bin/linux-s390/bin/wstoptecgw
   bin/mips-irix5/bin/wstoptecgw
   bin/osf-axp/bin/wstoptecgw
   bin/reliant-unix/bin/wstoptecgw
   bin/sequent/bin/wstoptecgw
   bin/solaris2-ix86/bin/wstoptecgw
   bin/uw2-ix86/bin/wstoptecgw

 **********************************************************************
 **********************************************************************

Fixpack Contents:

    - This README file
    - An image report for this fixpack
    - A CD_ROM image for this fixpack 
    - The file containing information about IBM NetView 7.1.2
      integration features:  nvintegration.pdf
    - A CD_ROM image addendum for the AS400 portion of this fixpack


 **********************************************************************
 **********************************************************************

Problems Fixed: 

 3.7.1-TEC-FP02 Problem Resolutions:

 Fixed in 3.7.1-TEC-0001

  APAR IY17813
    Symptoms: EVENT FORWARDING FROM 3.6.2 TO 3.7 TEC CAUSES
              EXTRANEOUS EVENTS

  APAR IY17964
    Symptoms: 371TEC01A IN FMT FILE % LENGTH S NOT PARSING CORRECTLY
    
  APAR IY18278
    Symptoms: POSTEMSG GARBLES JAPANESE CHARACTERS AT THE ADAPTER

  APAR IY20002
    Symptoms: TEC_EXECTASK_DBCS=TRUE CAUSES MEMORY LEAK IN TEC_TASK

 ***********************************

 Fixed in 3.7.1-TEC-0003E
 
  APAR IY24397
    Symptoms: TEC 3.7.1+PATCH 1 SOLARIS ADAPTER SMALL MEMORY LEAK

 ***********************************

 Fixed in 3.7.1-TEC-0005E

  APAR IY23919
    Symptoms: TECADNTS.EXE DIES WITH DRWATSON ERRORS WITH SECURITY
              LOG EVENTS

 ***********************************

 Fixed in 3.7.1-TEC-0006E

  APAR IY20879
    Symptoms: GUI RULE BUILDER RUNS OUT OF MEMORY AND SIGSEGV'S

 ***********************************

 Fixed in 3.7.1-TEC-0008E

  APAR IY25101 
    Symptoms: INFORMIX 9.2/FRAMEWORK 3.7. X AND TEC 3.7.1- WT COMMANDS
              ISSUE

 ***********************************

 Fixed in 3.7.1-TEC-0009E
 
  APAR IY25074
    Symptoms: PERF PROB WITH THE CONSOLE WHEN YOU HAVE SEVERAL
              TASK LIBRARIES

 ***********************************

 Fixed in 3.7.1-TEC-0010E
 
  APAR IY22140
    Symptoms: EIF_EP_ENGINE CORE DUMPS WHEN CLEARING CACHED TEC EVENTS

  APAR IY24606
    Symptoms: WITH PATCH 001 - EDIT PREFS FROM EVENT VIEWER EXCEPTION

  APAR IY24976
    Symptoms: EVENTS WITH (HASH) NOT LOADED IN EVENT CACHE

 ***********************************

 Fixed in 3.7.1-TEC-0011E
 
  APAR IY24718
    Symptoms: 3.7.X TEC_CONFIG HAS MEMORY LEAK

  APAR IY18758
    Symptoms: TEC_UI_SERVER[8700]: PANIC: SETITIMER FAILED. TIMERS.C

 ***********************************

 Fixed in 3.7.1-TEC-0012E
 
  APAR IY23939
    Symptoms: CREATE EVENT GROUP FAILS DUE TO INCORRECT DECIMAL SYMBOL

  APAR IY25766
    Symptoms: TEC CONSOLE (TME OR NON-TME) VERY SLOW TO PERFORM
              ANY ACTION

 ***********************************

 Fixed in 3.7.1-TEC-0013E
 
  APAR IY26534
    Symptoms: WTDBSPACE GENERATES ERROR MESSAGE- TEC 3.7.1

 ***********************************

 Fixed in 3.7.1-TEC-0017E
 
  APAR IY29083
    Symptoms: SMALL BLOCK PROBLEM ON NT/WIN ADAPTERS

 ***********************************

 New Fixes in 3.7.1-TEC-FP02

  APAR IY08645
    Symptoms: WTDBCLEAR.PL TAKES MUCH TOO LONG TO COMPLETE

  APAR IY15475
    Symptoms: WHEN TEC IS DOWN, SOFTWARE DISTRIBUTION EVENTS ARE
              NOT BEING CACHED

  APAR IY15799
    Symptoms: INIT.TECAD_LOGFILE STOP ADAPTER COMMAND KILLS
              OTHER LOGFILE

  APAR IY16090
    Symptoms: UNABLE TO ASSIGN FILTER ON "ACL" SLOT TEC 3.7

  APAR IY18504
    Symptoms: NO SCROLL BAR WHEN ADDING A FILTER USING THE
              "ADD SQL" BUTTON

  APAR IY22170
    Symptoms: COPYING A RULEBASE FAILS THROUGH GUI RULE BUILDER

  APAR IY22996
    Symptoms: LIST_OF STRING NOT HANDLED PROPERLY BY TEC_DISPATCH
              OR TEC_RULE

  APAR IY23065
    Symptoms: TEC_DISPATCH CRASHES WITH EXIT CODE 211, 
              SIGSEGV SPORADICALLY

  APAR IY23295
    Symptoms: TEC EVENT INFORMATION BUTTON WON'T LAUNCH NETSCAPE
              ON SOLARIS

  APAR IY23941
    Symptoms: TEC CONSOLE DOES NOT RETAIN COLUMN WIDTH/LOCATION
              CHANGES AFTER

  APAR IY24129
    Symptoms: 371 AS400 ADAPTER FILTERING NOT WORKING.

  APAR IY24391
    Symptoms: UPG_TEC_DB_370_TO_371.SH NEEDS CORRECTION FOR
              $VENDOR VARIABLE

  APAR IY24673
    Symptoms: SEVERITY COLORS DO NOT CHANGE IN 3.7.1-TEC-0001 (NON-TME)

  APAR IY24812 
    Symptoms: EVENT FROM NT AND WINDOWS 2000 GARBLED

  APAR IY25043
    Symptoms: NT TEC ADAPTER DR WATSONS ON SYSTEM ERROR EVENTS

  APAR IY25233
    Symptoms: SENDING TEC SERVER QUEUES EVENTS WHEN GETTING A LIGHT
              EVENT STREAM

  APAR IY25243
    Symptoms: TEC_CONSOLE -E EVENT_GROUP_NAME HAS NO EFFECT

  APAR IY25381
    Symptoms: GARBLED CHAR WHEN USING NO_UTF8_CONVERSION=NO
              WITH WPOSTEMSG

  APAR IY25922
    Symptoms: ACPEP-EP DEPENDENCY SET INCORRECT FOR TEC 3.7.1

  APAR IY26027
    Symptoms: AS400 3.7 ADAPTER WILL NOT FILTER AGAINST WILDCARDS

  APAR IY26103
    Symptoms: VARIABLE SCOPE IN PROLOG PASSES BEYOND RULE IN WHICH
              THE VARIABLE

  APAR IY26281
    Symptoms: INFORMATION BUTTON DOES NOT PICK UP CORRECT PATH

  APAR IY26332
    Symptoms: TEC HANGS

  APAR IY27045
    Symptoms: TEC SNMP ADAPTER DOCUMENTATION NOT COMPLETE

  APAR IY27198
    Symptoms: THE GLOBAL_EXISTS PREDICATE DOES NOT FUNCTION CORRECTLY

  APAR IY27199
    Symptoms: SAVE_GLOBALS PREDICATE DOES NOT SUCCESSFULLY WRITE
              VARIABLES

  APAR IY27500
    Symptoms: SETTING SINGLE PORT BDT TO TRUE CAUSES TEC FAILURES

  APAR IY27591
    Symptoms: WMIGCON INCORRECTLY MIGRATES FILTER STATEMENTS

  APAR IY27780
    Symptoms: WSETEMSG DOES NOT SET NULL WHEN "" OR OR '' IS PLACED
              AFTER THE

  APAR IY28071
    Symptoms: CONSOLE WILL NOT SHOW ANY EVENTS IN THE PRIORITY OR
              SUMMARY VIEW

  APAR IY18135
    Symptoms: INCORRECTLY - ADMIN AUTHORITY REQUIRED TO RUN
              TROUBLETICKET.SH

  APAR IY21084 
    Symptoms: TEC 3.7 OS/2 ADAPTER - DISTRIBUTION ADDS EXTRA CR
              TO TEXT FILE

  APAR IY20202
    Symptoms: CR_TEC_DB.SH SCRIPT FAILS IF SERVER ID IN RIM OBJECT
              IS NOT SET

  APAR IY22704
    Symptoms: JAVA CONSOLE COLOURS DISAPPEAR WHEN COL. REMOVED

  APAR IY24964
    Symptoms: JAVA CONSOLE RUNS OUT OF MEMORY WHEN PERFORMING
              ADMINISTRATIVE

  APAR IY25651
    Symptoms: TEC WINDOWS LOGFILE ADAPTER DIES WITH A DR WATSON

  APAR IY26465
    Symptoms: ATTR_SEQUENCE DOES NOT FUNCTION CORRECTLY. 
              FIRST_RELATED_EVENT

  APAR IY28434
    Symptoms: CREATE OPERATOR FAILS AFTER PATCH1

  APAR IY28443
    Symptoms: CREATE OPERATOR FAILS ON TEC_CONSOLE DUE TO A HYPHEN
              OR SPACE

  APAR IY28972
    Symptoms: TEC UI SERVER DIES WHEN MODIFYING LARGE NUMBER OF EVENTS

  APAR IY29351
    Symptoms: WINDOWS EVENT LOG ADAPTER RECEIVES DR WATSON DURING
              EVENT STORM

  APAR IY22187
    Symptoms: TEC JAVA CONSOLE MEMORY LEAK (PATCH 15E APPLIED)

 **********************************************************************
 **********************************************************************

Applying the Patch:

  **IMPORTANT:  Before applying this fixpack, stop the event server.

  **WARNING:  The .tec_config file is replaced during the installation
              of Fixpack 2.  Users with a customized file must create
              a backup copy prior to installation, in order to use with
              updated product.

  1.  Extract the fixpack:

        On a UNIX system:
        
        Extract the contents into a temporary directory, using the
        following commands. For the purpose
        of this example, assume that the variable $PATCH points to
        this temporary directory.

        cd $PATCH
        tar xvf 3.7.1-TEC-FP02.tar
        tar xvf 3.7.1-TEC-FP02_as400.tar

        On a Windows system:

        Extract the contents into a temporary directory, using the
        following commands. For the purpose of this example, assume
        that the variable %PATCH% points to this directory, and X is
        drive letter where %PATCH% is found.

        %SystemRoot%\system32\drivers\etc\Tivoli\setup_env
        X: 
        > cd %PATCH%
        > tar xvf 3.7.1-TEC-FP02.tar
        > tar xvf 3.7.1-TEC-FP02_as400.tar

        NOTE:  If extracting the tar image on a Windows system,
               you will find an executable for the tar utility
               in the TME installation on Windows:
                 bin/w32-ix86/tools/tar.exe.

  2.  The following instructions are included for using Software
      Installation Service (SIS).  If SIS is not used, skip to
      number 3.

      NOTE: SIS can install Tivoli Software products on most hardware
            platform supported by Tivoli Software, however there are
            some hardware platforms on which SIS cannot be run.
            Check the Tivoli Enterprise Installation Guide for the
            list of platforms on which SIS can be run.

      NOTE: You must have the install_product and super authorization
            roles to successfully install this fixpack.

    **IMPORTANT: The following SIS patch, available from the Tivoli
                 Support FTP site, is required: 3.7-SIS-0005

        a)  From the Tivoli desktop pull down menu, select
            Desktop --> Install --> Software Installation Service.
        b)  SIS will initialize, and display the Get Installation
            Password dialog.  Enter the installation password.
        c)  Click the Install button on the dialog which contains
            the Tivoli image.
        d)  Click the Select Product button on the Install Spreadsheet
            dialog.
        e)  Click the Import Product button on the Select Product
            dialog.
        f)  Locate the media to 3.7.1-TEC-FP02 using the file browser,
            and select the PATCHES.LST file by double-clicking it.
        g)  Select 3.7.1-TEC-FP02 in the Import Product dialog, and
            click the Import Button.
        h)  When the import is complete, click the OK button on the
            Global Progress dialog.
        i)  Select 3.7.1-TEC-FP02 in the Select Product dialog,
            and click the OK button.
        j)  Click the Select Machine button on the
            Install Spreadsheet dialog.
        k)  Select the machine(s) you would like to install
            3.7.1-TEC-FP02 to, and click the OK button.
        l)  Click the appropriate cell(s) in the Install Spreadsheet
            dialog. (NOTE: This should yield an X in the cell(s)
            for the machines to install 3.7.1-TEC-FP02 on).
        m)  Click the Install button.
        n)  Select the install algorithm you want to use in the
            Installation Algorithm dialog, and click the OK button.
        o)  SIS will perform the installation(s) you designated
            in the Install Spreadsheet dialog.
        p)  Installation is complete. Check the Additional 
            Installation Instructions section below.

  3.  Use the following steps to install the fixpack using the classic
      Tivoli installation mechanism.

      NOTE: The install_product and super authorization roles
            are required to successfully install this fixpack.

        a)  Select Install -> Install Patch from the
            Tivoli desktop" pull-down menu to display the
            Install Patch dialog.
        b)  Click the Select Media button to display the File
            Browser dialog.
        c)  Enter the path to the directory containing the Fixpack,
            $PATCH, in the Path Name field.
        d)  Click the Set Media & Close button to return to the
            Install Patch dialog.
        e)  The patch install list now contains the name
            of the fixpack.
            Select the fixpack by clicking on it. 
        f)  Select the clients to install this fixpack on.  Fixpacks
            typically need to be installed on the Tivoli server
            and on each Tivoli client.
        g)  Click the Install button to install the fixpack.

 **********************************************************************
 **********************************************************************

Additional Installation Instructions:

  Restart the event server after successful installation
  of the fixpack.

 **********************************************************************
 **********************************************************************

Database Changes and Special Considerations:

    None

 **********************************************************************
 **********************************************************************

Notes:

 ***********************************

 DBCS and UTF-8:

  Note: This applies only to adapters receiving non-English events.

  Tivoli Enterprise Console TME and Non-TME adapters:
  
  To prevent DBCS characters from becoming corrupted, stop the adapter
  and add the following option to the adapter configuration file:

    NO_UTF8_CONVERSION=YES

  Make sure there is a carriage return at the end of the line, or DBCS
  characters may become corrupted.  This option prevents DBCS
  characters in the event stream from being converted to UTF-8 encoding
  twice (in the adapter and in the EIF).  The command line interface
  (CLI), can use the same configuration file as the adapters.  The
  NO_UTF8_CONVERSION option is internally set to NO for CLIs.

 ***********************************

 ACF Install:

  The TME endpoint must be stopped on the target node (TMR gateway)
  when installing the ACF.

 ***********************************

 Tier 2:

  The Tier 2 enablement patch included in FP02 allows distribution of
  Tier 2 adapters from a Tier 1 ACF.

  Note:  See the Known Defects section for precautions.

 ***********************************

 SIS Installation:

  ** IMPORTANT: The following SIS patch, available from the Tivoli
                Support FTP site, is required if using Tivoli SIS to
                install this fixpack:  3.7-SIS-0005

  There have been problems reported with installations using SIS.
  Some of the binaries, including the adapters, do not distribute
  properly, without the above patch installed.

 ***********************************

 wmigcon:

  This command attempts to translate each filter as accurately as
  possible, but an exact match cannot be made for every filter.
  The old filters are specified as Perl regular expressions, and the
  new filters are specified with the SQL LIKE operator.
  Regular expressions and SQL do not map to each other in a precise
  way, so the user should inspect each filter after wmigcon has
  translated it, to make sure that the resulting SQL filter
  is accurate.  Consult the Tivoli Enterprise Console 3.7.1 Reference
  Manual.

 ***********************************

 tec_gateway.conf parameters:

  If the event server fails due to a high rate of incoming events,
  or event storms, the gateway may be used to control the rate at which
  the event server receives events from TME sources.  The following
  optional parameters may be used in the tec_gateway.conf file:
  
  EventSendThreshold = max_events_per_second
  BufferFlushRate = events_per_minute
  MaxGWCacheSizeMegs = size_in_megabytes
  
  EventSendThreshold - The maximum number of events per second in which
  the gateway sends events directly to the event server.  When the rate
  of incoming events exceeds the EventSendThreshold, then the gateway
  begins to cache the events.  From the point, EventSendThreshold is
  used in conjunction with BufferFlushRate, to scale back the rate at
  which events are sent to the event server, utilizing the cache.
    
  BufferFlushRate - The number of events per minute in which the
  gateway sends events to the event server from the cache, once
  connection to the event server has been restored.
  
  MaxGWCacheSizeMegs - Specifies the size of the gateway cache file.
  This parameter is not listed by default in the configuration file,
  and defaults to 1 megabyte.
  
  Note:  The cache file size cannot exceed 1 gigabyte.
  
  For example, if the event server can handle 25 events per second,
  and there are 5 gateways in the environment, set each gateway with
  the following:
  
  BufferFlushRate = 300
  EventSendThreshold = 5
  
  This implies each of the five gateways sending events at a rate of
  300 events per minutes (5 events per second).  Thus the server
  receives 25 events per second.

 **********************************************************************

 The following sections describe the improved functionality
 incorporated in this fixpack.

 **********************************************************************

 Custom Button in the Event Viewer:

  There is a new custom button option provided in the event console.
  When configured and activated, this button appears on the Event
  Viewer, and launches a user-defined script or executable file.
  Specify the following environment variables to create the button,
  which will be located on the middle bar of the Event Viewer, next to
  the Acknowledge button.  When an event is selected, and the button
  pressed, the action specified in TEC_CUSTOM_ACTION executes.

  Environment variables:
    TEC_CUSTOM_LABEL = name of the label (limited to 20 characters)
    TEC_CUSTOM_ACTION = the fully-qualified script to run

  Although the environment variables are set per operator, the custom
  button is not currently designed to be configured for each operator.
  In the IBM Tivoli Enterprise Console product, version 3.8 and above,
  custom buttons will be defined on a per-console basis through the
  console properties.

  Some limitations when setting the TEC_CUSTOM_LABEL and 
  TEC_CUSTOM_ACTION environment variables:

  1. The label is limited to, and truncated at, 20 characters.
  
  2. To run a shell script in UNIX or Linux, you must specify the shell
     program before the script:

     #/usr/local/tec_console> export TEC_CUSTOM_ACTION = \
     "/usr/bin/sh /usr/local/custom_action.sh"

     (Note: The "\" indicates a new line, inserted for readability)

  3. If the custom script launches a graphical application,
     for example a Java GUI, then you must export the DISPLAY
     environment variable in your script:

     #!/bin/sh
     export DISPLAY=<hostname>:0.0
     /usr/jdk/bin/java MyCustomButton $(SLOTS)

  When an event is selected in the Event Viewer and the custom button
  is pressed, the attributes of the event are passed to the custom
  button script as environment variables.  The SLOTS environment
  variable contains a string array with all attributes exported by the
  event console.  It will be similar to the following:

    SLOTS=num_actions hostname server_path adapter_host source\
          cause_event severity status ...

  Each one of these attributes is also an environment variable, and can
  be used in a custom button script.
  For example, in UNIX:

    #!/bin/sh
    /usr/jdk/bin/java UpdateSeverity $(severity) $(hostname)

  In Windows (a .bat file):

    @echo off
    d:
    d:\jdk\bin\java MyCustomButton "%SLOTS%" "%severity%" "%class%"
    @echo on
    REM define environment variable
    set TEC_CUSTOM_ACTION=d:\test\mycustombutton.cmd

 ***********************************

 wtdbclear:

  To improve the run time performance of the wtdbclear commands, table
  indexing and code changes were made, and stored procedures were added
  to the event database.

  SQL scripts for each database vendor type are provided to:

  - Rearrange the tec_t_evt_rec_log index columns to put the date_entry
    column first.

  - Rearrange the tec_t_evt_rep index columns to put the date_reception
    column first.

  - Add a stored procedure to the event database that can be called by
    the wtdbclear command (binary version).

  Stored Procedures Details:
  
  A new stored procedure was coded for each of the five databases that
  the Tivoli Enterprise Console product supports.  Stored procedures
  greatly reduce the time needed to run database functions, because
  they run on the database server, instead of the client.  
  This eliminates the need to transfer records back and forth across
  the network.

  **IMPORTANT: Stored Procedure Notes:

  1. The DB2 stored procedure has been coded with the same
     functionality as the other stored procedures. Due to DB2's
     requirement for a C compiler and DB2 SDK, this procedure has been
     functionally tested on AIX 4.3.3 only.  It has been included here
     in case the user has the required SDK and C compiler installed and
     configured with DB2, and desires the performance benefits.

  2. DB2 SQL stored procedures are only supported with
     DB2 v. 7.1 and later.

  3. RIM requires Tivoli Management Framework e-fix 371-TMF-0042E to
     run the stored procedure for Sybase successfully. This is
     available from the Tivoli Software Support FTP site. 


  Files included for the wtdbclear changes:

  - install_wtdbclear_stproc.sh

  **WARNING:  The event server must not be running while executing this
               script due to the index changes that occur.

    This file runs SQL scripts to install or remove the stored
    procedures and alter indexes. The script will attempt to
    shut down the event server if it is running,
    and will exit if shutdown is unsuccessful.

  - <db_type>_stproc.cr.sql and <db_type>_stproc_rm.sql
  
    Each database type, with the exception of DB2, has these two SQL
    scripts.  The <db_type>_stproc.cr.sql scripts alter indexes and add
    the stored procedure definition to the event database.  The
    <db_type>_stproc_rm.sql scripts drop the stored procedure from the
    event database.

  - db2_stproc_cr.db2, db2_stprocindex_cr.db2, and db2_stproc_rm.db2
  
    DB2 requires three scripts to accomplish the same functionality as
    the two scripts previously described for the other RDBMSs.
    The stored procedure for DB2 is located in the script named
    db2_stproc_cr.db2.  The db2_stprocindex_cr.db2 script contains the
    code to alter indexes and the db2_stproc_rm.db2 script drops the
    stored procedure.
    
    Note:  The DB2 Stored Procedure Builder requires stored procedure
           code to be the only SQL code in a particular file. The file
           must also end with the extension .db2.
           The db2_stproc_cr.db2 meets the criteria for DB2 Stored
           Procedure Builder syntax checking.


  How to run the install_wtdbclear_stproc.sh script:
  
    All the SQL scripts and the install_wtdbclear_stproc.sh shell
    script install into the $BINDIR/TME/TEC/sql directory when the
    fixpack is applied to the event server. For DB2 and Informix,
    these scripts should be run on the database server host, which may
    require copying the install_wtdbclear_stproc.sh shell script, along
    with the appropriate SQL scripts for the database, to the database
    server host. The install_wtdbclear_stproc.sh  shell script should
    be run as the Tivoli Enterprise Console RIM user for DB2 and
    Informix.  For Sybase, MS-SQL, and Oracle, the script prompts for
    the RIM user password as needed.

    There are three possible input parameters for the
    install_wtdbclear_stproc.sh script, described below.
    They are new, remove, and db2proc.

    new - Runs the SQL scripts to alter indexes and add the
          stored procedure to the event database. This is the default.

    DB2Proc - Installs the DB2 stored procedure into the
              event database.
              (Requires the DB2 SDK and C compiler)

    Remove - Removes the stored procedure from the event database.

  **WARNING:  DB2 and Informix Users must log in to your machine as the
              RIM user. On UNIX, use the 'su' command to switch to the
              RIM user ID and run the event database install scripts.
              On Windows, you must not be logged on as Administrator or
              your local domain ID. Log on as the DB2 user assigned as
              the Tivoli Enterprise Console RIM user.

    The following are examples to run the install_wtdbclear_stproc.sh
    script.

    1. No input parameters (the most common method):

       install_wtdbclear_stproc.sh

       -OR-

       install_wtdbclear_stproc.sh new

       The indexes will be altered and the stored procedure will be
       added to the event database. The <db_type>_stproc_cr.sql script
       is run for every database vendor type except DB2. 

       Note: DB2 will only alter the indexes by executing
             db2_stprocindex_cr.db2.

    2. Input parameter remove:

       install_wtdbclear_stproc.sh remove

       The stored procedure is removed from the event database. 
       The script <db_type>_stproc_rm.sql applies to every database
       vendor type. 

    3. Input parameters new and db2proc
       (most common options for DB2 7.1 and higher)

       install_wtdbclear_stproc.sh  new db2proc

       This will install the DB2 stored procedure and then alter
       indexes by running db2_stproc_cr.db2 and db2_stprocindex_cr.db2
       scripts.

       Note: Only use the db2proc option if the required DB2 SDK
             and C compiler is installed on the DB2 server and it
             is configured to compile the SQL procedure into C code.
             Refer to the DB2 documentation and IBM Redbooks for the
             compiler and configuration requirements.


  wtdbclear command changes (binary version):

    NOTE: Backup the current wtdbclear binary file,
          prior to installing the update.


    The new wtdbclear command automatically calls the stored procedures
    for each database type, unless the new option '-p FALSE' is used.
    This option may be used to bypass the calling of the stored
    procedure for any database type.  When the '-p FALSE' option is
    used, the older wtdbclear code is executed, however, benefits from
    altered indexes are still provided.

  **IMPORTANT: Use the '-p FALSE' option for the following:
                1. Running Tivoli Management Framework 3.7b and Sybase.
                2. Running any supported DB2 version prior to 7.1.
                3. Running DB2 version 7.1 without the DB2
                   SDK and C compiler.

    NOTE: DB2 users who are unable to take advantage of the new DB2
          stored procedure can continue to use their backup wtdbclear
          command, to avoid using the new '-p FALSE' option.

  wtdbclear.pl command changes (Perl version):

    The wtdbclear.pl command has been modified to make database calls
    using the new indexes. This avoids complete table scans and uses
    the indexes to find the events that match the -t time input option
    criteria.  The code then determines which retrieved events to
    delete if any other input criteria
    is specified. 

  How to gain other event database performance improvements:

    1. Specify the -t option with an argument of 0 to quickly clear the
       table.  With the wtdbclear.pl command, truncation is performed
       for MS SQL, Sybase, and Oracle, and deletion is performed for
       Informix and DB2.  The wtdbclear command will call the stored
       procedure and execute a DELETE FROM statement for all database
       types. 

       These commands run quickly because truncation clears a table
       without the overhead of logging changes, and deletion logs the
       changes but moves through the rows quickly.

       NOTE:  When clearing a large number of events, use the
              '-a' option.  See the wtdbclear or wtdbclear.pl command
              in the IBM Tivoli Enterprise Console Reference Manual.

    2. When the total number of rows to delete is less than the
       '-a' argument value, a DELETE FROM <table> WHERE DATE is less
       than option -t argument is executed using the table's index.
       This improves the speed because the index pinpoints which rows
       have a lower date value and then clears them quickly.

       Note: Be careful not to specify a commit threshold too large.
             This can cause the transaction logs to run out of space.

    3. When the number of rows to delete is greater than the
       '-a' argument, the rows are read to determine which should be
       deleted, and then they are deleted one by one. The stored
       procedure is the quickest way to delete rows in this manner.

    4. Where possible, both the wtdbclear and wtdbclear.pl commands do
       uncommitted reads to improve lock contention issues that can
       arise due to the event server running at the same time as the
       wtdbclear command.

    5. Statistics are updated internally for Informix, MS SQL, and
       Sybase to update their data distribution statistics for the
       event database.  These statistics are used for the internal
       database manager whose function is to calculate the fastest
       method to access data. If the statistics are not current, the
       internal database manager may choose a method that is not the
       fastest.

  Installation Notes:

  1. IMPORTANT! Make backup copies of the $BINDIR/bin/wtdbclear and
     wtdbclear.pl files prior to installing the fixpack.

  2. Install the fixpack according to the installation instructions.

 ***********************************

 IBM Tivoli NetView Integration:

  NetView integration consists of a rule set and predefined event
  groups that take advantage of the enhanced integration of IBM Tivoli
  NetView 7.1.2 with the Tivoli Enterprise Console product. See the
  nvintegration.pdf file provided with this Fixpack for details about
  the enhanced NetView integration.

  During installation of the fixpack, the NetView rule set is added to
  the Default rule base. This rule set is not active by default.
  To activate the rule set, perform the following steps (examples
  follow UNIX conventions, so modify them for different platforms).
  See the Tivoli Enterprise Console Rule Builders Guide for more
  information about rules and rule sets.

  1.  Go to the Default rule base directory:
      cd $BINDIR/TME/TEC/default_rb/TEC_RULES

  2.  Make sure the file netview.rls is in this directory.
      Edit the file rule_sets and append the following line:
      rule_set(netview, 'netview.rls', active).

  4.  Edit the file rule_sets_EventServer
      and append the following line:
      rule_set: netview

  5.  Go to the Default rule base classes directory:
      cd ../TEC_CLASSES

  6.  Make sure the file netview.baroc is in this directory.

  7.  Edit the file .load_classes and append the following line:
      netview.baroc
      (Be sure to add a carriage return at the end of the line)

  8.  If you have not done so already, source the Tivoli environment:
      . /etc/Tivoli/setup_env.sh
      (%WINDIR%\system32\drivers\etc\Tivoli\setup_env.cmd in Windows)

  9.  Recompile the Default rule base:
      wrb -comprules Default

  10. Reload the Default rule base:
      wrb -loadrb -use Default

  11. Stop and restart the event server:
      wstopesvr
      wstartesvr

  The following command creates the two predefined event groups for
  NetView events:

  wcrtnvgroups

  Note: This command requires the appropriate Tivoli user ID, password,
        and permissions to create an event group and assign event group
        filter for an event console.

  
  To disable the NetView 7.1.2 Integration functionality,
  perform the following:
          
  UNIX:
  cp $BINDIR/bin/tec_console_nonits $BINDIR/bin/tec_console
        
  Windows:
  copy %BINDIR%\bin\tec_console_nonits.cmd %BINDIR%\bin\tec_console.cmd
        
 ***********************************

 IBM Tivoli NetView 7.1.2 Enablement:

  
  **IMPORTANT: Do not install the IBM Tivoli NetView 7.1.2 enablement
               options, until IBM Tivoli NetView 7.1.2 is installed.


  Note: At the time of this fixpack release, IBM Tivoli NetView 7.1.2
        is not currently available.  It is expected to release soon
        after the release of 3.7.1-TEC-FP02.  Check the IBM or Tivoli
        Software Web site, or contact your account representative about
        availability of 7.1.2.

  For information about the IBM Tivoli NetView enablement features,
  view the nvintegration.pdf file, which is provided with this fixpack.

  This fixpack must be installed to use the new event flows from IBM
  Tivoli NetView 7.1.2 with Tivoli Enterprise Console 3.7.1.

  Tivoli Enterprise Console 3.7.1 Fixpack 2 introduces the optional
  integration with IBM Tivoli NetView 7.1.2.  This integration includes
  two primary provisions:

     1. The ability to launch from an event in the Tivoli Enterprise
        Console Event Viewer to a Tivoli NetView Web console.
        The following views are available to launch to in the
        Web console:
        - Submap Explorer
        - Object Properties
        - Diagnostics

     2. The ability to use predefined network-management rules with
        event flows unique to IBM Tivoli NetView 7.1.2.

  These provisions are described in the following sections.

  Event Console/NetView Web Client Integration:

  Prior to Fixpack 2 and IBM Tivoli NetView 7.1.2, users of Tivoli
  Enterprise Console 3.7.1 and the NetView product could launch the
  native NetView console from the Event Viewer. With this fixpack,
  administrators can opt to configure their event consoles to launch
  either the native NetView console or the new NetView Web console
  introduced in IBM Tivoli NetView 7.1.2.

  The native NetView console is the default option and supports
  NetView 6.x to 7.1.1.  By selecting the newer NetView option, for IBM
  Tivoli NetView versions 7.1.2 or later, different launch capabilities
  will be enabled.

  To enable this option select the following from the
  patch install menu:

  "3.7.1 Tivoli Enterprise Console NetView 7.1.2 Enablement" 

  Note: The NetView Web Console must be installed on the same system as
  the event console.

  For UNIX and Linux non-TME event console installations, the new
  NetView integration is enabled by running the use_new_netview.sh
  script located in the event console directory. For example, if the
  event console is installed in the /usr/local/tec_console directory,
  the following command would enable launching the new NetView
  Web console:

  ./use_new_netview.sh

  To use the new NetView launch capability, configure the operating
  system to export an environment variable that specifies the NetView
  Web console path.

  In a UNIX and Linux environment, export the environment variable
  NVWC_HOME to the fully-qualified directory where the NetView Web
  console is installed.  If the NetView Web console is installed in
  the /usr/local/nvwc directory, the following first command would
  define the environment variable, and the second command would start
  the event console:

  export NVWC_HOME=/usr/local/nvwc
  tec_console

  To install a non-TME event console on Windows systems, the event
  console installation wizard for Tivoli Enterprise Console 3.7.1
  Fixpack 2 has a new panel called NetView Launch Support.

  Note:  The environment variable is set automatically by the event
         console installation wizard.


 **********************************************************************
 **********************************************************************

 Test Summary:

 Defect #   Test Description
 --------   ----------------  

 IY15475    Verified that events from Software Distribution(v4.1) are
           cached when the Event Server is not started.

 IY15799    Distributed two adapters, a normal log file adapter and then
           a second application log file adapter. Then created a third
           adapter and distributed with the stop command. The 2nd and
           3rd adapters are in their own directories and have the
           INSTALL_TECADHOME environment variable commented out on from
           the init.tecad_logfile. All three adapters worked correctly.

 IY18278    Verified that wpostemsg with DBCS on AIX in ja_JP locale
           functions correctly.

 IY18758    From the Viewer menu Edit/Preferences and change Max No
           Events from 1000 to 999, click OK. At this point you will
           notice a Java exception. When the fix is applied the
           exception does not happen.

 IY21084    Verified that tec log file adapter for OS/2 distributed
           without errors to an OS/2 system and functioned correctly.

 IY23941    Verified that width/location of columns in the tec console
           can be changed and saved correctly on all supported
           platforms.

 IY24812    Verified that wpostemsg with DBCS on windows in ja_JP locale
           functions correctly.

 IY27500    This fix requires TME Framework 3.7.1 patches 003 and 008
           installed. After patches installed, restart oserv and wrb
           commands work correctly with single_port_bdt set to TRUE.

           NOTE:  To use single_port_bdt=TRUE, install the following
                  TME Framework 3.7.1 patches, available from the
                  Tivoli Support FTP site:
                  3.7.1-TMF-0003 and 3.7.1-TMF-0008

 IY27591    See the wmigcon note in previous section.

 IY17813    Used the Task Send Event to TEC Server to send an event from
           the 3.6.2 TEC Server to the 3.7.1 TEC Server and sent events
           that had all of the slot values set to "~" or "@". They did
           not kill the tec_rule process.

 IY17964    Tested parsing of FORMAT Logfile_Base with both UNIX
           and windows.

 IY23919    Used the tecad_nt adapter to receive over 20,000
           wineventlogs.  Tested wtdumprl,stop/start the TEC server;
           no errors occurred.

 IY20879    Created 10 rules sets of 30 rules each on both Windows &
           AIX; It did not fail with the memory error.

 IY25101    Tested TEC Server operating with INFORMIX 9.2/TME 3.7.1.
           Also testedWT commands in this environment.

 IY25074    Loaded 10 more task libraries and tried to bring up the
           console. The console came up fine within 30-40 sec of
           logging in. This was verified on both Windows and UNIX
           platforms.

 IY22140    Used rule set from customer that caused problem.  Verified
           events were cached and dumped successfully. Events cleared
           without problems on Windows and UNIX.

 IY24606    From the Viewer menu selected Edit-> Preferences and then 
           selected Working Queue, and changed one of the columns sort
           to ascending; then clicked OK. No errors with the
           tec_ui_server occurred on Windows or UNIX.

 IY24976    Used rule set from customer that caused problem. Verified
           that events were cached and dumped successfully. 

 IY24718    The tec_config process was successfully terminated after the
           Console was stopped.

 IY23939    Changed decimal symbol '.' to ',' and created an event
           group with new symbol. Restarted console and event group
           with decimal still existed correctly.

 IY25766    Used default rulebase and generated 5000 events. It took
           significantly less time for the console to start with 5000
           open events in data base. Tested on Windows and UNIX.

 IY26534    Tested wtdbspace script on both windows and UNIX with
           various data bases, including INFORMIX 9.2.

 IY29083    Generated high volume of events for the tecad_nt and
           tecad_win adapters. No errors encountered.

 IY08645    Tested instructions for wtdbclear included in this README
           file, on Windows and UNIX, and on all supported databases.

 IY15475    Halted Event Server and caused Software Distribution events
           to be generated.  Started Event Server and TEC console.
           Cached events from SD were displayed on console
           Event Viewer.

 IY16090    Verified that the ACL slot can be successfully used in any
           filter. Also used SQL queries to check if a value is in an
           ACL list.

 IY18504    Tested the "ADD SQL" function and verified scroll bar
           function.

 IY22170    Copied a rule set and found to be identical as source.
           Tested on both Windows and UNIX.

 IY22996    Ran a 6 step scenario that demonstrates problem of LIST_OF
           not correctly processing quoted strings containing embedded
           comma and space chars. With the fixpack installed, the
           scenario completed without errors. 

 IY23065    Generated tens of thousands of events, and tec_dispatch
           error code 211 was not encountered. This fix pack contains
           the fixes to multiple tec_dispatch crashes. Additional log
           capture logic was added to provide additional root cause
           analysis if a similar problem occurs. 

 IY23295    Wakeup_Up_Netscape successfully tested on Windows and
           UNIX platforms.

 IY24129    Verified that FilterMode=IN and FilterMode=OUT function as
           designed using the scenario outlined in defect description.

 IY24391    Script upg_tec_db_370_to_371.sh run successfully on MS_SQL
           and other databases.

 IY24673    All severity colors verified on windows and UNIX and all
           supported databases.

 IY25043    This problem was caused by an error in pre-filter logic.
           The tecad_nt adapter using pre-filters was tested
           extensively.

 IY25233    Setup an Event Server forwarding events to another; server
           receiving events was shut down. Noticed that forwarding
           server properly continued to process events and cached
           forwarded events.

           NOTE:  Add the following line to the necessary configuration
                  file.  (Adapter configuration file, for example):
                  eipc_verify_portmapper=YES


 IY25243    Verified tec_console -e event_group_name works correctly.

 IY25381    Verified wpostemsg works correctly when using
           NO_UTF8_CONVERSION=NO.

 IY25922    Tested All ACP profile distribution to all supported
           endpoints.

 IY26027    Successfully tested AS400 Filtering with the wild card "*"
           character.

 IY26103    A sample rule that illustrates the problem was tested and
           verified that a variable's scope is working correctly.

 IY26281    Viewer Information button was verified to be working
           correctly on Windows and UNIX.

 IY26332    Tested several events storms to verify tec_gateway did not
           hang or go into a run loop.

 IY27045    Additional information for SNMP adapter is now available.
           This information will be included in TEC 3.8 Adapters Guide.

           NOTE:  Consult the tecad_snmp.baroc file for information
                  regarding generic traps as well as NetWare, Cisco,
                  and Cabletron traps.


 IY27198    Created a rule that contains the set_global_var predicate.
           Used global_exists predicate in same rule to close an event
           if it exits.

 IY27199    Used save_globals to write variables to a file.  Checked the
           file to see if the variables had been written.

 IY27591    Verified that WMIGCON translates each filter as accurately
           as possible, but an exact match cannot be made for every
           filter. The old filters are specified as Perl regular
           expressions, and the new filters are specified with the SQL
           LIKE operator.  Regular expressions and SQL do not map to
           each other in a precise way, so the user should inspect each
           filter after WMIGCON has translated it, to make sure that
           the resulting SQL filter is accurate.

 IY27780    Executed wsetemsg with several different values for the msg
           slot (i.e. "abc", " ", ""). Ensured that the slot value was
           set appropriately according to the added documentation
           comments.

 IY28071    Forced data base shutdown and forced oserv shutdown/reexec 
           while running automated tasks. Verified that the console
           would come up and show events in both priority and summary
           views.

 IY18135    Setup a non-admin user and tried to execute the trouble
           ticket script. Ensured that the system correctly informs
           the user that admin authority is required.

 IY20202    Tried to manually create an Oracle RIM object without the
           server ID set.  Ensured that the system correctly halts the
           script and informs the user that the server ID is required.

 IY22704    Verified that the user will not be allowed to remove
           the severity column from the Event Viewer display.

 IY24964    Executed a script to continually send events to the Event
           Server and set up several automated tasks. Allowed system
           to operate over several days and ensured that tec_console
           process did not continue to leak memory.

 IY25651    Sent very large messages (1K, 2K, and 4K) by modifying the
           tecad_win.fmt file. Verified that the Windows log file
           adapter functioned correctly.

 IY26465    Created a rule containing an attribute sequence. Sent events
           fitting the attribute sequence rule and ensured that they
           were correctly correlated according to the rule.

 IY28434    Created a task with "_!_"  in the name and one with a space
           (" ") in the name. Verified that after restarting the
           console you are still able to create operators.

 IY28443    Created a task with a hyphen ("-") in the name and one with
           a space (" ") in the name. Verified that after restarting
           the console you are still able to create operators.

 IY29351    Created an event storm (600+). Verified that the Windows
           log file adapter continued to function normally.

 **********************************************************************
 **********************************************************************

 Regression Test Notes:

  Fixpack 2 was subjected to the following regression testing:

    1. The Tivoli Enterprise Console automated test suites repeatedly
       exercised the CLI functionality.

    2. Ad-hoc functional and system tests exercised the TME Desktop,
       the TEC Console, and the NetView Consoles.

    3. In addition to testing each APAR as written in all Tier 1
       environments (and Tier 2 environments where specified), manual
       regression testing was performed for each APAR.

    4. Specific tests with HP-UX 10.20 with JRE 1.18 were performed to
       ensure continued functionality.

  Installation testing included an upgrade from Tivoli Enterprise
  Console 3.6.2 to 3.7.1, followed by an installation of Fixpack 2.
  Regression testing was then performed.
  Fixpack 2 was installed on all supported platforms.
  
  The regression testing focused on the following:

    1. Verified that prior maintenance release fixes included in the
       fixpack still functioned as expected.

    2. Verified that no new problems were introduced as a result of
       Fixpack 2.

  Test Platforms:

    AIX 4.3.2, 4.3.3
    Solaris 2.6, 2.7
    HP-UX 10.20, 11.0
    Windows NT 4.0 Service Packs 5 and 6
    Windows 2000
    Red Hat Linux 7.0, 7.1
    SuSE Linux 6.4, 7.0
    Turbo Linux 6.0, 6.1
    OS/2 Warp 4.5
    Windows XP
    SuSE Linux S/390



 **********************************************************************
 **********************************************************************

Known Defects and Limitations:

 ***********************************

ACF:

 There is an issue with the Tier 2 .fmt files (adapter format files)
 when distributing through ACF.  The following error message will
 display because the .fmt file location has changed to be in a
 language specific directory:

  ""acpmsg:0015
  File /data/instdir/tmrbfg94/bin/generic_unnix/TME/ACF_REP/\
       tecad_logfile_linux-ix86.fmt not a regular file"

  To workaround this issue, perform the following steps:
    1. Select Edit -> Profile.
    2. Select the record to edit in the profile and select
       Edit -> Entry.
    3. In the window "Edit Adapter #, Profile <profilename>
       click the Distribution button.
    4. In Files To Be Distributed, select the file 
       tecad_logfile.fmt=host:/path/to/tecad_logfile_linux-ix86.fmt.
    5. Click the up arrow to edit the entry.
    6. Change the path /path/to/tecad_logfile_linux-ix86.fmt to
       /path/to/tecad_logfile_linux-ix86_C.fmt.
    7. Click the check mark to record the changes.
    8. Change the file tecad_logfile.fmt to C/tecad_logfile.fmt.
    9. Click the check mark to record the changes.
    10. Click the Save & Close button.
    11. Distribution should now perform successfully.

 This workaround applies to all available language code sets
 (including C as in the example).



 ***********************************

CLI Commands:

 wrb:

 The actions listed below will cause the following error when compiling
 the rulebase:

      *** SYNTAX 196 *** Term expected

 1. Using 'all_instances' or 'first_instance' predicates in the action
    of a timer rule.
 2. Specifying 'of_class_<variable>' or the anonymous variable '_'.
 3. Using a custom slot value in the 'where' clause.

 Changing the '_', or '_<variable>' to the event class that the custom
 slot is defined in, or placing this within
 [ 'Class_name', 'Class_Name2' ] will allow the compiler to run
 successfully. The wcomprules command can also be run to compile the
 rulebase.

 *****

 wtdbclear:

 wtdbclear -e -p -t 0 returns an error.

 ***********************************

DBCS (UTF8):

 DBCS characters embedded in events become garbled after passing
 through tec_gateway.
 (Fixed in 3.7.1-TEC-0024E)

 ***********************************

EIF:

 When a new line is appended to an ASCII log file, the entire contents
 of the file are sent.
 (Fixed in 3.7.1-TEC-0019E)

 ***********************************

Event Console:

  On a Windows system, the tec_task.exe process can enter an infinite
 loop while processing NetView (ITS_) events.  End the process with the
 Windows Task Manager if this occurs.  If the problem re-occurs, it
 might be necessary to reboot the system to continue processing NetView
 events.

 *****

 Defining an automated task can prevent the console from loading more
 than 1400 events.  To view all events, delete the automated task, and
 reload the events.

 *****

 On Windows NT systems, the Information button on the Event Viewer
 points to an invalid URL.  It works correctly on Windows 2000
 and UNIX.

 *****

 Configuring a task for a selected event on AIX and Solaris returns an
 error code of 0 when the Event Server is not running.

 *****

 The event filter in the print_cache rule does not work.

 *****

 "Null Pointer Exception" occurs in the console when the event server
 stops running.

 *****

 Selected events become deselected after a refresh interval.
 (Fixed in 3.7.1-TEC-0020E)

 *****

 After restarting the Event Viewer, the Preferences window under the
 Edit menu does not work.
 (Fixed in 3.7.1-TEC-0020E)

 ***********************************

NetView Integration:

 NetView Rule Set:

 The current NetView rule set does not support virtual
 private networks.

 *****

 IBM Tivoli NetView Synchronization:

 1. Events acknowledged in the event console might not propagate to the 
 NetView console until the next polling cycle occurs.
 Because immediate synchronization is dependent on SNMP traps that are
 sent to the NetView server, this behavior can occur more frequently
 when the NetView server and the event server are on different subnets
 and are separated by a fire wall.

 2. For troubleshooting purposes, leave the internal IBM Tivoli
 Enterprise Console TEC_Start event open. This allows you to use the
 Task Output dialog to confirm whether the SNMP traps were sent to the
 IBM Tivoli NetView product. Also, be aware that a large number of
 tasks can be reported in this window.

 3. Closing/Acknowledging a large number of events can slow, and
 possibly stop the event server.  To avoid this, do not close more than
 100 events from the Event Viewer at once.

 *****

 nvintegration.pdf: 

 Sections 4.2 and 4.2.2 in the nvintegration.pdf document incorrectly
 state that closed events are synchronized with the IBM Tivoli NetView 
 product. This release only supports the synchronization of
 acknowledged events.

 ***********************************

Rules:

 The syntax checking of the rules compiler has been enhanced.  Existing
 syntax errors in custom rules that have previously been undetected,
 may now be reported as errors.

 *****

 Uppercase slot names do not instantiate during rules operation.
 (Fixed in 3.7.1-TEC-0026E)

 *****

 Rules containing an attribute filter with the attribute name enclosed
 in quotes, will not compile.
 (Fixed in 3.7.1-TEC-0026E)

 *****

 exec_program does not pass arguments properly.
 (Fixed in 3.7.1-TEC-0022E)

 *****

 Slot values specified as LIST_OF_STRING are not pulled from the
 object database properly.
 (Fixed in 3.7.1-TEC-0026E)

 ***********************************

Other:

 The cr_tec_db.sh script fails on Windows NT when RIM is not present.

 *****

 SIS 3.7 fails to install versions 3.7.1 and 3.7.1-FP02 of
 the UI Server.

 **********************************************************************
 **********************************************************************

 