Date:   Mar, 30, 2002

Patch:  5.1.1-ITM-FP03

Component: IBM Tivoli Monitoring, Version 5.1.1

General Description:
    This patch fixes the APARs and defects listed in the
    "Problems Fixed" section of this README file.

    Additional features for TEC Server specifications are added:
    1. Local EventServer
    2. Failover
    3. Multiple TEC servers.
    Look at the "Integration with Tivoli Enterprise Console" manual
    in the "books" directory of this Fixpack for further details.

    This Fixpack supersedes Fixpack 5.1.1-ITM-FP02

    Performance improvements on the Unix engine and on the gateway
    processes are also included.

    Serviceability improvements have been implemented

    1. The trace_dmxeu.log trace files no long contains <F>.

    2. wdmcheckprereq is able to find ODBC version on WinNT4 too.

    3. Changes of the trace settings on the Windows engine works
       at runtime.

    4. The TBSM adapter and the transport layer traces are enabled
       by default.

    5. The msg_datacollector.log file now has the time specified with
       the local timezone.


Database Changes:

 The following modified resource models are installed:

 - Memory             (Unix)

 - File System        (Unix)

 - CPU                (Unix)

 - Network Interface  (Unix)

 - Security           (Unix)

 - Process            (Unix)

 - Memory             (Windows)

 - Server Performance Prediction for Unix_Linux  (Unix)

 - Server Performance Prediction for Windows     (Windows)

 - Job Log (OS400)

  The notice group "ITM Tivoli Monitoring" is created if it does not
  already exist.

 ACLs:
 The ACLs of the  Request Manager methods are changed to include
 the "itm_whc_user" role.

 GUI:
  The "Send TEC Events" option in the "Profile Properties" window has
  been modified. See the "Integration with Tivoli Enterprise 
  Console.pdf" document in the "books" directory of this Fixpack for 
  details.

 Dependency Manager:
 The TMW2KlcfDList and TMW2KepDList dependency managers are changed 
 and recreated. The "dmnt_get_request_data" endpoint method is moved 
 from  TMW2KlcfDList to TMW2KepDList.
 
 
Problems Fixed:
 Included in Fixpack 3:
             
    APAR:    IY32954
    Symptom: DMAE 4.1 and DM Classic (3.7) TDS Components cannot 
             exist together. Files rolup2db.pl  and wdmsql placed 
             down by DM 3.7 will be overwritten by DMAE's version.

    Notes:   In order to avoid this problem, file rolup2db.pl will be
             now placed down in another location by DMAE. The new
             location will be %BINDIR%/TME/Tmw2k/TDS/tasks.
             The binary file wdmsql is still in the %BINDIR%/bin
             directory, but it has been changed to be compliant with
             DM classic version in the following way.
             An optional parameter "-ITM", has been added that
             when specified, indicates the log file that needs to be 
             used.
             For classic edition, the log file is /tmp/spp_guide.log,
             for advanced it is /tmp/dmae_spp_guide.log.

    WARNING: The wdmsql command has the same place for DM classic and
             DM advanced. So the fix done for this APAR will be 
             developed in the same way on DM Classic TDS component.
             For this reason, if you install a DM Classic TDS component
             patch, you need to reapply the "IBM Tivoli Monitoring - 
             Gathering Historical Data Component 5.1.1 - Fixpack 3" 
             component.

    APAR:    IY36978, IY36800
    Symptom: The AMY_m10_s010_buildStarSchema.db2 script has a missing
             WHERE clause which prevents it from running successfully
             when other enablement packs upload data into TEDW tables

    APAR:    IY37710
    Symptom: Web Health Console cannot display RMs status when the 
             Profile containing the RM has Japanese character for 
             profile.

    APAR:    IY37775
    Symptom: When a new profile is created it does not reflect all 
             the Properties settings defined in the tmw2kDefProfile
             (Default profile).
             The same problem is present in the Profile Clone action
             where the Profile Properties are not duplicated.

    APAR:    IY38102
    Symptom: The command wdmeditprf is missing of 2 options.
             The option for enabling/disabling RAW data logging and
             option for enabling/disabling TEDW data logging.

    Notes:   These 2 options has now been added and the syntax of 
             them is as following:
             wdmeditprf -P <profile#region> -add <resource_model>
                    -Log [ -LogEnable | -LogDisable ]
                    [ -RAW yes | no ] [ -TEDW yes | no ]
                    [-p <period> ] [ -Agg yes | no ]
                    [ -ap <aggregation_period> ] [-Min | -NoMin]
                    [-Max | -NoMax] [-Avg | -NoAvg] \n\

             and:

             wdmeditprf -P <profile#region> -edit <resource_model>
                    -Log [ -LogEnable | -LogDisable ]
                    [ -RAW yes | no ] [ -TEDW yes | no ]
                    [-p <period> ] [ -Agg yes | no ]
                    [ -ap <aggregation_period> ] [-Min | -NoMin]
                    [-Max | -NoMax] [-Avg | -NoAvg] \n\

    APAR:    IY38450
    Symptom: The Request Manager performs unnecessary checks on the
             gateways and on the endpoints causing performance 
             problems.

    APAR:    IY38490
    Symptom: The "wdmeng" command hangs when trying to stop or delete
             a resource model from the Unix engine

    APAR:    IY38593
    Symptom: DMXMemory Model reports negative numbers for
             PercAvailStorage and TotalAvailStorage on
             HP-UX endpoints.

    APAR:    IY38686
    Symptom: Files xml are malformed, and are causing TEDW data to be
             not inserted in the database.
  
    APAR:    IY38687
    Symptom: All the commands using the option "-m all" (wdmmn,
             wdmdiscovery, wdmconfig, wdmmngcache, wdmheartbeat,
             wdmcollect, wdmcmd) encounter a problem when the oserv
              of one managed node is down.
             Instead of keep on looping all the other managed nodes,
             these commands stop the execution, so that if only one
             managed node is down, it is no more allowed the use of
             "-m all".
             I.e. wdmmngcache -m all -l

    APAR:    IY38689
    Symptom: The option "-m" need to be added to wdmcmd command, in
             order to allow the starting and stopping operation on
             all the endpoints.
    Notes:   The new command syntax is now the following:
             wdmcmd -restart {-p <profile_manager#region> |
                       -e <endpoint>... | -m {<managed_node> | all} }
             wdmcmd -stop {-p <profile_manager#region> |
                       -e <endpoint>... | -m {<managed_node> | all} }

    APAR:    IY38806
    Symptom: "dmae_ep_dep" dependency set broken after applying
             5.1.1-ITM-FP02.
  
    APAR:    IY38862
    Symptom: Data returned by DMXMemory RM are inconsistent with
             TEDW metadata. 

    APAR:    IY38975
    Symptom: The date field in the message file of the data collector
             is set in the GMT format.

    APAR:    IY39340
    Symptom: The Resource model DMXProcess released in ITM 5.1.1
             Fixpack 2 does not work properly; the sintax for
             specify multiple parameters is not correctly parsed
             in the Java Script. 

    APAR:    IY39349
    Symptom: Trying to migrate a Custom Resource model (RM) created 
             for AS400 using the migration method from DM classic 
             monitor collection produce an error in the trace log.

    APAR:    IY39412
    Symptom: The Resource model DMXProcess released in ITM 5.1.1
             Fixpack 2 causes a file descriptor leak on Linux. 

    APAR:    IY39643
    Symptom: AMW4593W error code on the Web health console if an
             endpoint is removed from the TMR.

    APAR:    IY39725
    Symptom: The wdmsql command invokes both rollback and delete 
             function in the RIM object, when only rollback should be
             used.

    APAR:    IY39752
    Symptom: Function "GetStrParameterCount" called into WorkBench 
             returns  the number of element set to FALSE and TRUE for
             boolean list; it should return only the number of 
             elements set to TRUE as described in the ITM User Guide.

    APAR:    IY39896
    Symptom: The Windows engine experiences a memory leak while 
             running a javascript resource model.

    APAR:    IY40160
    Symptom: When running the AMY_m10_s010_buildStarSchema Step from 
             the AMY Warehouse Pack version 1.1 in the DB2 Data 
             Warehouse Center GUI, the following error occurs:
             SQL_ERROR: 'Insert Dest Data' 2003.01.1


    APAR:    IY40190
    Symptom: The wdmeditprf command does not allow to set TBSM and 
             TEC event at the same time. 
             A double typing of the wdmeditprf command is needed to 
             set this 2 parameter.

    APAR:    IY40191
    Symptom: If a profile contains only resource model/s of a wrong 
             type respect to all the endpoints subscribed, 
             when it is distributed no messages or warning are 
             displayed to aware that the distribution has not been 
             submitted.
             In particular, if the distribution has been attempted 
             via command line with the wdmdistrib command, a massage 
             is prompted:
             "AMW0162I - Operation successfully submitted. 
             Distribution ID is N/A"
             which is not clear at all.
    Notes:   A new warning message will now be prompted when the 
             distribution does not occur for this reason:
             "There are no resource model types matching with the 
             endpoints interpreter". 
             This will be prompted in both cases, when the
             distribution is attempted via CLI and via GUI.

    APAR:    IY40726
    Symptom: DMXProcess generate a java core due to a memory access
             violation when more than 1000 processes are running.

    APAR:    IY40869
    Symptom: Resource Models with numeric parameters do not work if 
             locale for current user is set to Danish and locale for 
             the system is  set to United States. 

    APAR:    IY40870
    Symptom: DMXProcess shipped in 5.1.1-ITM-FP02 fails on Linux when
             it try to retrieve processes' informations having
             a huge quantity of arguments; it causes a
             StackOverflowError in trace_dmxengine.log and the 
             engine's crash.

    APAR:    IY41082
    Symptom: ITM Engine on W2k replace mfc42.dll and msvcrt.dll even
             if they are already present.
    
    Notes:   On Windows 2000 boxes these libraries are not replaced.

    APAR:    IY41083
    Symptom: Duplicate entries in MetricsData table causes failure in
             ETL process AMX_CO5_S01_EXTRACT.
    Notes:   If you have the ITM_DB already created, you must run the
             new scripts $BINDIR/TME/Tmw2k/WarehouseCfg/up_tbl.
                                                      <db_extension>.
             The steps to follow are similar to the one described in 
             IBM Tivoli Monitoring User's Guide Version 5.1.1, page 
             93, step 4b. An example for DB2 will follow. 
             If you don't have the ITM_DB created, you must exactly 
             follow  the steps  described in the paragraph "Creating 
             and Configuring the Database Structure", page 91.
             Example for updating the ITM_DB for DB2, Windows box:
             - Start -> run -> db2cmd
             - db2 connect to itm_db user <user>
             - db2 -td$ -vf ./up_tbl.db2

    APAR:    IY41211
    Symptom: Tmw2k.exe causing Dr Watson during the "register_endpoint" 
             upcall.
             
    APAR:    IY41526
    Symptom: Multiple Tmw2k.exe when stop/start the engine, when 
             the performance counters corresponding to the 
             Process performance object are disabled.

    APAR:    IY41629
    Symptom: DMXSpp reports wrong values in the DB for CPU Idle time
             metric.

    APAR:    IY41633
    Symptom: Commas converted into dots in the TEC event msg string. 

    APAR:    IY41862
    Symptom: The "%" cannot be used in the "Message" form in event
             definition secion of Workbench; using "%" a garbled
             message is shown during an event is sent to TEC.
 
    APAR:    IY41878
    Symptom: Core dump of the Request manager while the datacollector
             is running if there are more than 100 zip files for a 
             single endpoint.             
   
    APAR:    IY41940
    Symptom: TMW_Spp fails to log data for Phisical Disks section.

    APAR:    IY42297
    Symptom: Security defect: Files *.js put on the endpoint have 
             write permission for all users. 
             They must have read only permissions for users and write
             permission only for root user.
             
    Defect:  34358
    Symptom: ETL:With MQ, MQI, and RMs   ETLs running together 
             in the same environment, there is a problem with the
             component relationships that are not being created 
             correctly. Specifically CTQ_MGR has an entry with 
             HMI_HOST as a parent.  This is causing duplicate 
             component entries for all children of CTQ_MGR and as a 
             result duplicate measurements. 

    Defect:  35547
    Symptom: ETL: "AMY_m15_buildOSStarSchemas_Process" has wrong agent 
             site.

    Defect:  36094
    Symptom: Tivoli Enterprise Data Warehouse: resources being created 
             against wrong AVA_HOST.
             
    Defect:  36206
    Symptom: ETL1 is not handling the case where PACS with similar 
             resource names are logging data in the same RIMDB.

    Defect:  35184
    Symptom: Task arguments are out of order when passed to a task
             implementation where some of the arguments have null 
             values.

    Defect:  36057
    Symptom: Core dump of the Windows engine while compacting the 
             local database.

    Defect:  36106
    Symptom: There is not a way to disable the purge process on the 
             ITM_DB while using the datacollector.
    Notes:   The "datacollector.db_purge_enable" parameter has been 
             added to enable or disable the purge of the data in the
             ITM_DB. Use the wdmconfig command to set this parameter,
             the default value is "true".
             
    Defect:  36417
    Symptom: The datacollector stops loading the data of the 
             endpoints if it reaches an endpoint for which the zip 
             files are not present on the gateway.

    Defect: 36421
    Symptom: Performance improvement of the trace utility on the Unix 
             engine.


                          
 Included in Fixpack 2:

    APAR:    IY35247
    Symptom: The memory model resource model may go in error
             for an overflow in the VBA code.

    APAR:    IY34189
    Symptom: Customer resource models created from dumped collection
             fail on Unix if the monitor interpreter is perl.

    APAR:    IY33930
    Symptom: Memory leak of the Unix engine on AIX platform due to
             java thread creation process.

    APAR:    IY34565
    Symptom: There is not a way to make an administrator access only
             a subset of the endpoints with the Web Health Console.
             All the command lines are designed to make the
             administrator access and perform operations on the
             endpoints the administrator has the required roles.
             Without the fix, the administrator needs the "user"
             role on the TMR to use the Web Health Console. With
             the "user" role, the administrator has enough rights to
             connect and see data from all the endpoints.

    Notes:   To use the Web Health Console, the "user" role is no
             longer required. The administrator needs one of the
             following roles: user, senior, super, admin or
             itm_whc_user on the TMR. An administrator may have
             only the itm_whc_user role on the TMR, thus preventing
             him to connect to any endpoint. To set the role on the
             TMR, use the following command:
             wsetadmin -r global,itm_whc_user <administrator>.
             Then create a PolicyRegion and grant the administrator
             the roles you want him to have on his endpoints.
             After that, move the endpoints in the specified Policy
             Region. In this environment, the administrator will
             only see his endpoints on the Web Health Console.

    APAR:    IY34672
    Symptom: The DMXProcess resource model can not distinguish
             processes with arguments.

    Notes:
    1) the properties terminal, basename and arguments has been added
       to the DMXProcess.mof
       - terminal: the name of the controlling terminal of the
         process
       - basename: the basename of the executable of the process
       - arguments: the arguments of the process;

    2) the DMXProcess Resource Model script has been modified in
       order to manage the new added properties: now as parameters it
       accepts variable length filters made by a list of couples
       name-value.
       The well-known properties are:
        basename     : the basename of the executable
        name         : the name of the executable with the relative
                       path
        name         : the name of the executable. It has to be
                       specified in the way it has been launched.
                       This depends on the OS and on the process
                       itself
        terminal     : the controlling terminal name of the process
        arguments    : the arguments of the process
        user         : the username belonging of the process
        group        : the groupname belonging to the process
        effectiveUser: the effective username belonging to the
                       process
        effectiveGroup:the effective groupname belonging to the
                       process
        status       : the status of the process

  Example:basename=lcfd | name=/opt/Tivoli/lcf/bin/solaris2/mrt/lcfd

    3) The mof file, the DMXProcess provider has been modified for
       every UNIX platform.


    APAR:    IY34688
    Symptom: The Environment Variables available to Custom script
             resource models or imported monitors from Classic
             Collections Resource Models is inconsistent between
             platforms versions of ITM engines.
             This can be seen in that some are missing on some OSs
             and exists on others or if they do exist are not set
             correctly.
             There is also no way to get/set Environment variable
             within the Visittree routine for use by Custom script.

    APAR:    IY34824
    Symptom: The burst of TBSM events should not exceed the limit of
             50 events packaged in one single TBSM event.

    APAR:    IY35190
    Symptom: The Rollup job changes the target of new data
             aggregation job if the aggregation failed on one
             endpoint.

    APAR:    IY35760
    Symptom: An incorrect TEC Event is sent from the ActionManager
             indicating a Run failure, when a Run Program is
             specified as one of the builtin actions, whether this
             Run Program runs successfully or not.

    APAR:    IY35831
    Symptom: The Solaris Provider of the DMXProcess Resource Model
             returns the base name of the process.

    Note:    the considerations for APAR IY34672 apply also to this
             APAR

    APAR:    IY36008
    Symptom: The DMXFileSystem resource model reports wrong values
             for /var and /home on AIX systems.

    APAR:    IY36550
    Symptom: The log file on Windows is filled by the following error
             warning:
             "Warning some warehouse metrics were not collected in
             the previous cycles. It won't be considered for
             logging.".

    APAR:    IY36851
    Symptom: Event generated by the ITM Windows engine sent to TEC
             result in a syntax error if it contained a decimal value
             and the ',' character is used as separator.

    APAR:    IY35903
    Symptom: A Resource Model created from a custom script goes in
             error state if the interpreter is perl.

    APAR:    IY35933
    Symptom: Problem: The script dmae_tec_inst.sh
             (in $BINDIR/TMNT_TEC) does not do any error checking
             when issuing wstopesvr and wstartesvr but does echo
             "stopping the T/EC Server" or
             "Starting the T/EC Server".

    APAR:    IY36390
    Symptom: When editing an Indication and choosing an ACTION of a
             TASK, some TaskLibraries do not appear in the GUI list.

    APAR:    IY37242
    Symptom: Uninstalling IBM Tivoli Monitoring 5.1.1 also 
             incorrectly removes the uninstall script for the TDS 
             component.

    APAR:    IY37276
    Symptom: The script dmae_sentryanalyser.sh fails if a Sentry
             Profile name contains a space. Moreover the script will
             not run
             correclty on Solaris due to a syntax error.

    APAR:    IY35174
    Symptom: The DMXNetworkInterface resource model may cause a
             javacore.

    APAR:    IY37752
    Symptom: Migrating  DM37 Monitor W2K Service Status to ITM5.1,
             the corresponding Resource Models goes in error state.

    Notes:   A particular syntax must be used in order to monitor
             services with a name composed of two or more words; see
             the following examples:
             1) Monitor a service begins with word "Server":
                  -add in parameters: Server /B
             2) Monitor a service ends with word "Storage":
                  -add in parameters: Storage /E
             3) Monitor a service called exactly "Tivoli Endpoint":
                  -add in parameters: "Tivoli Endpoint" "/B /E"
             4) Monitor a service begin with words
                "Tivoli Management":
                  -add in parameters: "Tivoli Management" /B
             5) Monitor a service begin called exactly "TrcBoot":
                  -add in parameters: TrcBoot "/B /E"

    APAR:    IY37761
    Symptom: Svc.Trace on VBA does not allow to print the "%"
             character as simple text.

    APAR:    IY37762
    Symptom: Universal.AppInstances in Workbench: /sntlab/ps.o file
             not refreshed when ntprocinfo runs. It causes a bad
             behavior of the Resource Model created from the classic
             monitor AppInstances.

    APAR:    IY37050
    Symptom: If using european language settings other then english,
             historical data does not show as percentages.

    APAR:    IY37865
    Symptom: The notice group "IBM Tivoli Monitoring" is not created
             during the upgrade of the product.

    APAR:    IY37317
    Symptom: When a resource model is disabled and it is distributed
             on an endpoint on which the prerequisites are not met,
             the resource model has the "missed prereq" state.

    APAR:    IY36057
    Symptom: Overflow error in .vba code using TMW_MemoryModel.
             Similar to APAR IY35247.

    APAR:    IY38177
    Symptom: A "general failure" error occurs while distributing a
             profile to profile managers only. This happens if
             distributing to a profile manager with the "one level of
             subscribers" option or while distributing with the "all
             levels of subscribers" option if all the profile
             managers do not have endpoint subscribed.

    APAR:    IY37003
    Symptom: A "general oserv failure" created when distributing a
             TMW2KProfile copy from a HUB TMR which contains a custom
             Resource Model. The error occurs if the custom resource
             model has not been added both TMRs.

    APAR:    IY37221
    Symptom: In ITM 5.1 heartbeat behavior the Endpoint would
             periodically make an upcall. In ITM 5.1.1 this behavior
             was changed and the Endpoint no longer makes the
             periodic upcall. Missing the periodical upcall we have 2
             problems:
             1) when the gateway machine is down the endpoints don't
                migrate
             2) if the cache is deleted, it is not recreated.

    Note:    In ITM 5.1 the period to make upcalls was 18 minutes,
             with this Fixpack the period is configurable through the
             wdmconfig command. For example if you invoke the
             following command:
             wdmconfig -m all -D heartbeat.reg_ep_time=60 and
             then restart the ITM engines, the endpoints will perform
             an upcall each 60 seconds.
             Setting the heartbeat.reg_ep_time parameter to 0 no
             upcalls will be performed.

    APAR:    IY37072
    Symptom: The support for the local EventServer is not enabled.

    Note:    Check the "Integration with Tivoli Enterprise Console"
             manual provided with this Fixpack.

    APAR:    IY37279
    Symptom: The "Parametric Event Log" Resource Model can cause the
             engine to function improperly if the Event Log Rate is
             greater than 10 per second.

    Note:    This APAR was successfully verified with a rate of 20
             per second.

    APAR:    IY37297
    Symptom: A resource model with numeric parameters will not
             work properly on a non-US endpoint.

    APAR:    IY37749
    Symptom: The msg slot from a non-TME TEC event coming from an
             AS400 is empty.

    APAR:    IY37821
    Symptom: Sax basic overflow error while calling many times the
             createmap procedure in a resource model.

    Notes:   In order to avoid the problem described in IY37821 you
             need to build the Custom Resource Model using the
             Workbench shipped in this Fixpack.

    APAR:    IY37861
    Symptom: On a Windows endpoint japanese version with Service Pack
             3 installed, the tmw2k_ep process hangs and multiple
             instances may occur.

    APAR:    IY37995
    Symptom: If using TME TEC events on a Unix endpoint and the TEC
             gateway is down, a duplicated is cached.

    APAR:    IY37422
    Symptom: The installation of patch 3.7-DAD-0002E on ITM 5.1.1
             fails.

    Defect:  34229
    Symptom: ITM tasks cannot have more than 10 arguments.

    Defect:  34410
    Symptom: The trace_dmxeu.log trace files contains an unnecessary
             <F> at the end.

    Defect:  34735
    Symptom: wdmcheckprereq is unable to find ODBC version on WinNT4.

    Defect:  34772
    Symptom: m12javaprovider has to work with jre 1.4.

    Defect:  34917
    Symptom: "RunProgram" and "Shell" APIs don't work if the current
             directory is not properly set.

    Defect:  34927
    Symptom: The resource model category is not properly logged on
             Unix engine.

    Defect:  35131
    Symptom: It is not possible change the trace settings on the
             Windows engine at runtime.

    Defect:  35091
    Symptom: Improvement in the Archive Manager of the TEDW support.

    Notes:   A new staging area is created.

    Defect:  35099
    Symptom: Memory leaks in the middle layer processes (Heartbeat,
             Data Collector, TBSM adapter, Task Engine, Request
             Manager, Rim Handler).

    Defect:  35047
    Symptom: Local Unix DB continuosly grows.

 Included in Fixpack 1:

    APAR:    IY33437
    Symptom: Serviceability defects in ITM 5.1.

    APAR:    IY33624
    Symptom: The "all level of subscribers" profile distribution
             option does not work.

    APAR:    IY33439
    Symptom: Clearing events mechanism may fail in some occasions.

    APAR:    IY33577
    Symptom: TMW_Spp resource model points to Windows NT counter
             which provides incorrect output on Windows 2000
             machines, especially CPU counters.

    APAR:    IY34192
    Symptom: Custom resmodels created from monitors fail.

    APAR:    IY34236
    Symptom: Scheduling of resource models does not work if any
             end at 24:00, models show as scheduled in wdmlseng
             when should be running.

    APAR:    IY34301
    Symptom: Scheduled resource models can not be disabled.

    APAR:    IY34575
    Symptom: Invalid column name error in rim_db_log when trying
             to insert data to a column name "PROFILE" in the
             DM_METRICS table.

    APAR:    IY34674
    Symptom: Dmae_sentryprofile_analyzer.sh getting error when run
             in interconnected Tmrs with resources exchanged.

    APAR:    IY34600
    Symptom: The Svc method ReplaceNumParameter and
             RemoveNumParameter do not work on Unix Engine.

    APAR:    IY35492
    Symptom: DMXSpp fails on AIX endpoints, after upgrading to
             version ITM 5.1.1.

    APAR:    IY28294
    Symptom: Spp task SPR_PurgeDataInDb for MSSQL and Sybase:
             username of the SPP database is hardcoded.

    APAR:    IY37260
    Symptom: On interconnected TMR with  ITM 5.1.1 the region name
             for the EventServer is stored twice in the Respource
             Model Profile.

    Defect:  34116
    Symptom: Changes into DMXUser and DMXGroup providers.

    Defect:  34121
    Symptom: Indications dialog contains a null value in
             drop down list.

    Defect:  34122
    Symptom: ReplaceStrParameter() fails.

    Defect:  34151
    Symptom: OS400 - JobLog RM does not see matching conditions.

    Defect:  34154
    Symptom: PERF: TEDW HistDatalog performance worsens each
             period.

    Defect:  34165
    Symptom: Logging GUI does not save changes.

    Defect:  34759
    Symptom: The ETL1 is failing when in the same hierarchy the
             same attribute name is used for 2 different
             components.

    Defect:  34175
    Symptom: ITM stops writing TEDW XML files if any resource
             models on endpoints is in the retry mode.

    Defect:  34222
    Symptom: Adding "-o delete" to the wdmdistrib.

    Note:    this new option has been added because of a
             limitation with Framework 3.7.1 Fixpack or later:
             the automatic delete push does not work.
             Before deleting the profile from the DSL GUI type:
             'wdmdistrib -p <profile> -o delete'.

    Defect:  34232
    Symptom: Unix lcf env variables are not propagated to custom
             scripts.

    Defect:  34237
    Symptom: UNIX: Cpu provider changes for Linux INTERP.

    Defect:  34241
    Symptom: The value of the date in the date slot is incorrect.

    Defect:  34351
    Symptom: Creation of an OS/400 directory leaves wrong owner.

    Defect:  34476
    Symptom: Importing a bad dumped collection crashes JVM.

    Defect:  34680
    Symptom: TEDW: implement a method that allows to insert
             Metrics data.

Operating Systems: Solaris, AIX, HP-UX, Linux, Windows


Dependencies: ITM 5.1.1

Patches superseded by this patch: 5.1.1-ITM-FP02.

Files replaced or added by this patch:

     Check the image.report file for details

Fixpack Contents

    - This README file
    - Verification Status Report
    - A CD-ROM image for this patch
    - The "Integration with Tivoli Enterprise Console" manual in the 
      'books' directory
    - A new image of the Workbench in the "WB" directory


 Before You Begin the Installation

 WARNING: The current Fixpack must be installed on the TMR server
          first, then on all the managed nodes.
 

 Before you install the Fixpack, you must stop the engine on the 
 endpoints by using the wdmcmd -stop command and all the ITM
 processes on the managed nodes (wdmmn -stop -m all -d -r -t -h -b)


 IBM Tivoli Monitoring, Version 5.1.1 must already be
 installed on any managed nodes on which this Fixpack is to be 
 installed. 

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

 Installing the Fixpack is a two-stage process:
 1) Extract the  Fixpack.
 2) Apply the Fixpack in ONE of the following two ways:
   2A) With Software Installation Service (SIS)
   2B) From the Tivoli desktop
3) Apply the fixpack on the Tivoli Enterprise Data Warehouse

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

 1) To extract the Fixpack, perform the following steps:
 
   On a UNIX system:

      Extract the contents of the 5.1.1-ITM-FP03.tar file into a
    temporary directory.
                    
      # cd $PATCH
      # tar xvf 5.1.1-ITM-FP03.tar 
    
    where:
      - $PATCH is the temporary directory
     
      
   On a Windows NT system:

      Extract the contents of the 5.1.1-ITM-FP03.tar file into a
    temporary directory. 
      
      > %SystemRoot%\system32\drivers\etc\Tivoli\setup_env
      > X:              
      > cd %PATCH%
      > tar xvf 5.1.1-ITM-FP03.tar 

      where:
      - %PATCH% is the temporary directory
      - X is the drive letter where the %PATCH% directory 
        is located
     
      NOTE:  On Windows NT, the executable tar file is 
             bin/w32-ix86/tools/tar.exe.


 2)  To install this  Fixpack, you must have both the install_product
     and super authorization roles. 

 2A) Before you apply the Fixpack by using Software Installation 
     Service (SIS), note the following:

     SIS can install Tivoli products on any hardware
     platform supported by Tivoli, but there are some
     hardware platforms on which SIS cannot be run. See the 
     TME 10 Software Installation Service User's Guide 
     and TME 10 Software Installation Service Release Notes, 
     for the list of platforms on which SIS can run and more
     information about using SIS.

 2B) To apply the Fixpack from the Tivoli desktop, perform the
     following steps:
    
     a)  Select the Install -> Install Patch option from the
         Desktop menu, to display the Install Patch dialog.
    
     b)  Click the Select Media button to display the 
         File Browser dialog.
    
     c)  In the Path Name field, type the path to the directory that 
       contains the patch.
             
     d)  Click the Set Media & Close button to return to the
         Install Patch dialog.
         The patch install list now contains the names of the Fixpack 
         components to be installed:

       o IBM Tivoli Monitoring, Version 5.1.1.- Fixpack 3
       o IBM Tivoli Monitoring - Tivoli Enterprise Data Warehouse
         Support, Version 5.1.1 - Fixpack 3
       o IBM Tivoli Monitoring - Gathering Historical Data
         Component 5.1.1 - Fixpack 3

     e)  Select the IBM Tivoli Monitoring, Version 5.1.1.- Fixpack 3
         component from the list.

     f)  Select the managed nodes on which to install the Fixpack.
                 
     g)  Click the Install button to install the Fixpack.

     h)  Select the IBM Tivoli Monitoring - Tivoli Enterprise Data
         Warehouse Support, Version 5.1.1 - Fixpack 3 component
         from the list.
                    
     i)  Select the managed nodes on which to install the Fixpack.
   
     j)  Click the Install button to install the Fixpack.

     k)  Select the IBM Tivoli Monitoring - Gathering Historical Data
         Component 5.1.1 - Fixpack 3 component from the list.         
    
     l)  Select the managed nodes on which to install the Fixpack.
                 
     m)  Click the Install button to install the Fixpack.

 3) To install the fixpack on the Tivoli Enterprise Data Warehouse 
    follow these instructions:

    a)   Before applying the fixpack on the Tivoli Enteprise Data 
         Warehouse you must demote to 'development' all the processes
         belonging to the AMX enablement pack.

    b)   Run %TWH_TOPDIR%\install\bin\tedw_wpack_patchadm.sh in a bash 
         to create the twh_app_patcher.cfg configuration file into the 
         %TEMP% directory;

    c)   Edit the %TEMP%\twh_app_patcher.cfg configuration file to 
         complete the "USER SUPPLIED SECTION" section
         The "APP_MEDIA_DIR" must refer to the directory of the patch
         bundle where the twh_install_props.cfg is located. 
         For this Fixpack the APP_MEDIA_DIR must refer to the 
         %PATCH%\tedw_apps_etl\AMX directory

    d)   Run again the tedw_wpack_patchadm.sh script to complete the 
         installation of the fixpack

Known problem:
       - ETL1 generates false metric exceptions if PACS with similar 
         resource names are logging data in the same RIMDB; as a result
         measurement records are not inserted into the central data
         warehouse.
       - Some issues on the installation of AMX, AMY components were 
         identified in 5.1.1-ITM-FP03. 
         These problems have been already addressed by the Interim Fix 
         5.1.1-ITM-0021LA that is replacing the AMX and AMY components
         of this Fix Pack.
         