Date:   December 30, 1999

Patch:  3.6.2-TEC-0004

Component: Tivoli Enterprise Console

General Description:
        This patch includes the 3.6.2-TEC-0002 patch with UTF8 enablement.
        WARNING: This patch should only be applied at sites that need 
                 the UTF8 enablement.

Problems Fixed:
        New Fixes in 3.6.2-TEC-0004

        Internal CMVC defect 89479
        Symptoms: TEC is not UTF8/MBCS enabled.

        APAR IY08064
        Symptoms: "date" column is garbled.

        Fixes from 3.6.2-TEC-0002

        APAR IY08285
        Symptoms: When shutting down the Logfile Adapter, it should
              not refresh syslog if the adapter was not monitoring
              syslog.
        Additional Information: When shutting down an adapter that was
              started with the -s option, you should shut it down in
              the same way.  Example:  init.tecad_logfile -s stop

        APAR IY08253
        Symptoms: TEC commits its database transactions too frequently.
              The unnecessary commits should be removed to avoid 
              slowing down event processing.

        APAR IY08218
        Symptoms: "init.tecad_snmp stop" does not properly shutdown the 
              SNMP adapter and can leave the binary running.

        APAR IY07642
        Symptoms: When flushing events from a non-TME EIF agent, only some
              of the events (approximately 56) are flushed each time. 
              In addition, the last event flushed each time will be
              duplicated.
        Additional Information: non-TME EIF agents include postemsg, 
              non-TME adapters, and custom adapters not using the
              libtec.a library.

        APAR IY06827
        Symptoms: When the TEC Server is restarted the TEC_Start event 
              is not the first event processed by the tec_rule.
        Additional Information: Events marked as QUEUED/WAITING in the 
              Reception Log at startup have arrived before the 
              TEC_Start event and are therefore processed first.
              This fix moves TEC_Start to the head of that list so
              it truly signifies the start of TEC processing.

        APAR IY05550 
        Symptoms: When the tec_gateway process sends a flood of events
              to the TEC Server while in connection_less mode, only
              the first event is received and processed.

        APAR IY04701
        Symptoms: When an event arrives with a slot containing more 
              than 256 bytes, the data is truncated to 256 bytes.
        Additional Information: This most commonly happens with the "info"
              slot in events sent from Distributed Monitoring.
              The maximum has been increased from 256 to 1024 bytes.
              Events still have a total maximum size of 4048 bytes.

        APAR IY01475
        Symptoms: Rule Base compilation failure after using wcprb with 
              the -o option like this:
                    wcprb -cro Default UserRulebase 
        Additional Information: This happens when the wcprb command
              is run by a non-root user.

        APAR IY00489
        Symptoms: A non-TME EIF agent in connection_oriented mode will 
              not cache or re-establish the connection to TEC if
              the connection is lost.  The only way to re-establish
              the connection is to cycle the EIF application.

        APAR IX83918
        Symptoms: "wtdumprl -o DESC" lists events in descending order, but
              events within the same second are listed in ascending 
              order.
   
        Internal CMVC defect 87065
        Symptoms: wtdbclear.pl clears WAITING events from the Reception
              Log even if -f is not specified.
        Additional Information: QUEUED and WAITING events should only be
              cleared when -f is specified.

        Internal CMVC defect 84815
        Symptoms: Events are lost and TEC_DB insertion failure events are
              generated when the TEC Server is restarted with events 
              in the QUEUED state.
        Additional Information: Events were only lost when there were
              QUEUED events that arrived within the same second and
              therefore had the same date_reception.  These were not
              assigned a unique event_handle, causing the DB errors.

        Internal CMVC defect 84757
        Symptoms: The date_reception and cause_date_reception environment
              variables are exported in hexadecimal notation when
              calling exec_program or exec_task from the Rule Base.
        Additional Information: These are now exported in decimal notation.

        Internal CMVC defect 83897
        Symptoms: wtdbspace dies with a segmentation fault when the
              RDBMS is not running.
        Additional Information: wrimsql was fixed to solve this problem.

        Internal CMVC defect 83376
        Symptoms: wtdbclear.pl stops clearing the Event Repository 
              after 1000 events.

        Internal CMVC defect 77596
        Symptoms: wtdbclear.pl does not clear out all events from the
              tec_t_op_ass_log table.
        Additional Information: Internally generated events, such as 
              "Rule Cache full: forced cleaning", are the ones that
              were not being cleared from tec_t_op_ass_log.

        Internal CMVC defect 73227
        Symptoms: The cr_tec_db.sh and rm_tec_db.sh scripts do not work 
              with MS SQL Server 7.0.

Architecture(s): Solaris, AIX 4, HP-UX 10, HP-UX 11, Windows NT 3.5 and 4.0

Patches superceded by this patch: 3.6.2-TEC-0002

Dependencies: 3.6.2-TEC-0001

Database Changes and Special Considerations: None

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

    Event Server
    ------------
    bin/$INTERP/TME/TEC/tec_server
    bin/$INTERP/TME/TEC/tec_reception
    bin/$INTERP/TME/TEC/tec_dispatch
    bin/$INTERP/TME/TEC/tec_task
    bin/$INTERP/TME/TEC/tec_rule
    bin/$INTERP/TME/TEC/tec_rule_data
    bin/$INTERP/TME/TEC/tec_server_gui
    bin/$INTERP/TME/TEC/tec_config
    bin/$INTERP/TME/TEC/tec_db_calls
    bin/$INTERP/TME/TEC/tec_compile_rules_gui.sh
    bin/$INTERP/TME/TEC/tec_agent
    bin/$INTERP/TME/TEC/tec_agent_bdt_demo
    bin/$INTERP/TME/TEC/sql/cr_tec_db.sh
    bin/$INTERP/TME/TEC/sql/cr_db.mssql7
    bin/$INTERP/TME/TEC/sql/rm_db.mssql
    
    Event Console
    -------------
    $BINDIR/TME/TEC/tec_client

    Event Server and Event Console
    ------------------------------
    bin/$INTERP/bin/postemsg
    bin/$INTERP/bin/wpostemsg
    bin/$INTERP/bin/wtdumper
    bin/$INTERP/bin/wtdumprl
    bin/$INTERP/bin/wtdumptr
    bin/$INTERP/bin/wtdumpcr
    bin/$INTERP/bin/wcomprules
    bin/$INTERP/bin/wtdbclear.pl
    bin/$INTERP/bin/wrimsql
    bin/$INTERP/TME/TEC/tec_agent_demo
    bin/aix4-r1/bin/wiconv
    bin/hpux10/bin/wiconv
    bin/solaris2/bin/wiconv

    EIF
    ---
    bin/postemsg
    bin/wpostemsg
    libteceif.a

    non-TME Adapters
    ----------------
    NON_TME/AIX4-R1/tecad_logfile
    NON_TME/AIX4-R1/init.tecad_logfile
    NON_TME/AIX4-R1/tecad_snmp
    NON_TME/AIX4-R1/init.tecad_snmp
    NON_TME/HPUX10/tecad_logfile
    NON_TME/HPUX10/init.tecad_logfile
    NON_TME/HPUX10/tecad_hpov
    NON_TME/HPUX10/tecad_snmp
    NON_TME/HPUX10/init.tecad_snmp
    NON_TME/SOLARIS2/tecad_logfile
    NON_TME/SOLARIS2/init.tecad_logfile
    NON_TME/SOLARIS2/tecad_hpov
    NON_TME/SOLARIS2/tecad_snm
    NON_TME/SOLARIS2/tecad_snmp
    NON_TME/SOLARIS2/init.tecad_snmp
    NON_TME/W32-IX86/tecad_nt.exe
    NON_TME/W32-IX86/tecadnts.exe
    NON_TME/W32-IX86/tecad_hpov.exe
    NON_TME/W32-IX86/tecad_snmp.exe
    NON_TME/W32-IX86/tecad_snmps.exe
    EIFSRC.TAR

Patch Contents:

    - This README file
    - An image report for this patch
    - A cdrom image for this patch 


Applying the Patch:

    1)  Extract the patch:

        On a Unix system:
        
        Extract the contents into a scratch directory. For the purpose
        of this release note, assume that the symbol $PATCH points to
        this directory.

        # cd $PATCH
        # tar xvf 3.6.2-TEC-0004.tar

        On a Windows NT system:

        Extract the contents into a scratch directory. For the purpose
        of this release note, assume that the symbol %PATCH% points to
        this directory.

        > %SystemRoot%\system32\drivers\etc\Tivoli\setup_env
        > X:              
          ^-- 'X' is drive letter where %PATCH% is found
        > cd %PATCH%
        > tar xvf 3.6.2-TEC-0004.tar

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

    2)  If this patch is to be installed on a release level of 3.6 or
        greater, follow these instructions for using Software
        Installation Service (SIS).  If not, skip to step 3 below.

        NOTE: SIS can install Tivoli products on any hardware
              platform supported by Tivoli, but there are some
              hardware platforms on which SIS cannot be run. Please
              check your SIS User's Manual 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 patch.

        a)  From the Tivoli Desktop, pull down 
            Desktop --> Install --> Software Installation Service.
        b)  SIS will initialize, and bring up the Get Installation
            Password Dialog.  Enter your 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.6.2-TEC-0004 using the file browser, 
            and select the PATCHES.LST file by double-clicking it.
        g)  Select 3.6.2-TEC-0004 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.6.2-TEC-0004 in the Select Product Dialog, if it
            is not already selected, and click the OK Button.
        j)  Now click the Select Machine Button on the Install
            Spreadsheet Dialog.
        k)  Select the machine(s) you would like to install
            3.6.2-TEC-0004 to, and click the OK Button.
            You should install this on all machines with ACF installed.
        l)  Click the appropriate cell(s) in the Install Spreadsheet
            Dialog. (NOTE: This should yield an "X" in the cell(s)
            for the machines you want to install 3.6.2-TEC-0004 to).
        m)  Click the Install Button.
        n)  Select the install algorithm you want to use on the
            Installation Algorithm Dialog, and click OK.
        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 patch using the original
        Tivoli install mechanism.
        NOTE: You must have the install_product and super authorization
        roles to successfully install this patch.

        a)  Select the "Install -> Install Patch..." option from the
           "Desktop" menu to display the "Install Patch" dialog.
        b)  Press the "Select Media..." button to display the "File
            Browser" dialog.
        c)  Enter the path to the directory containing the patch,
            $PATCH, in the "Path Name:" field.
        d)  Press the "Set Media & Close" button to return to the
            "Install Patch" dialog.
        e)  The patch install list now contains the name of the patch.
            Select the patch by clicking on it. 
        f)  Select the clients to install this patch on.  You should 
            install this on all machines with ACF installed.
        g)  Press the "Install" button to install the patch.

Additional Installation Instructions:
  1. Restart the TEC Server after the patch is installed.

  2. To take advantage of the fixes to non-TME EIF, you will need to 
     recompile your custom EIF adapters using either the code in 
     EIFSRC.TAR or libteceif.a provided with the EIF product.

  3. To update your non-TME adapters, you will need to copy the new
     non-TME binaries provided in the patch's NON_TME directory to the 
     $TECADHOME/bin directory where each adapter is currently installed.


Known Defects: 
    APAR IY08063
    Symptoms: The event message which length is longer than 256 bytes
          is truncated.

    APAR IY09834
    Symptoms: After application of fix 3.6.2-TEC-0002 events will only be
          received by the tec server if the 'log reception of events' option
          is set.
          If this option is not set, you need to set it and recompile the
          rulebase with the option set, then restart the server.


Limitations and Workarounds:
  1. The NT Event Log Adapter needs a localized version of tecad_nt.fmt.
     Before you begin to localize, make a backup copy of the installed
     tecad_nt.fmt file. Do not translate class names nor keywords such
     as FORMAT, FOLLOWS, etc. Simply replace the English string patterns
     with their corresponding patterns, in the desired language, using 
     the local encoding.
     For example, on a Japanese NT system, use Shift-JIS encoding. The
     patterns defined in tecad_nt.fmt must match exactly what is
     recorded in the NT Event Log. The NT Event Viewer tool can be used
     to determine what those patterns are.
     Tivoli technical support can provide help in localizing tecad_nt.fmt.

  2. gencds does not support multibyte characters in tecad_nt.fmt. If
     you need to define new classes, please observe the following notes:
    a. Work on a copy of the English version of tecad_nt.fmt; never
       modify the original.
    b. Non-ASCII characters are not supported in class names. Use
       temporary ASCII strings for the patterns. These patterns will be
       replaced later.
    c. Run gencds on the customized .fmt to generate the .cds file.
    d. Save a copy of the .fmt file for future modifications.
    e. Replace the temporary ASCII string patterns with the desired 
       multibyte string patterns, in the local encoding of the machine 
       running the adapter.

  3. The Rules Engine does not work with slots containing multibyte
     characters. Do not define rules that operate on slots that may
     contain multibyte characters.

  4. The Rule Builder GUI tool does not support multibyte characters
     input.

  5. The RIM object does not yet convert UTF-8 to the local encoding of
     the RDBMS. Therefore, TEC events are stored in the RDBMS in UTF-8.
     Third party applications that need to read TEC events from the RDBMS
     must be aware of this fact and provide conversion from UTF-8 to the
     desired encoding.
