***********************************************************
***********************************************************
**                                                       **
**  NOTICE:  This Patch has been superseded by patch     **
**  3.6.2-DMN-0030                                       **
**                                                       **
**  Please use it instead unless otherwise directed.     **
**                                                       **
***********************************************************
***********************************************************


Date:  24 September 2001

Patch: 3.6.2-DMN-0024

Component: Distributed Monitoring

General Description:
   This patch fixes a variety of defects in the Distributed Monitoring
   engine as well as other DM executables for both Managed Nodes and 
   TMA endpoints.  This patch requires that the DM 3.6.2 Maintenance 
   Release be installed with patch 3.6.2-DMN-0023,
   prior to installing this patch. 

Problems Fixed:

 APAR IY07031
 Symptom: Problem on mcsl, monitors with restriction not worked
             correctly.

 APAR IY08262
 Symptom: Set monitor schedule default values are not taken from
          default when using "Add with default".

 APAR IY12993
 Symptom: Monitor security_log_audit_success event of NTEventLog 
          collection always returns "FALSE".

 APAR IY09454
 Symptom: Monitor daemon status reports incorrect value on Linux
          when the daemon is swapped out of current memory.

 APAR IY19067
 Symptom: Numeric and string script monitors of Universal 
          collection do not work on Netware endpoint.

 APAR IY15385
 Symptom: Security violation: the custom monitors could
          run also with invalid UID/GID.

 APAR IY21720
 Symptom: The perl script io_stat.pl does not allow for
          line of output that AIX puts out at level 4.3.3. 

 APAR IY21478
 Symptom: The userid setting in a sentry profile does not work
          for responses when it is set to "$root_user". The user
          appears to be always "nobody" or an unknown user.

 APAR IY22952
 Symptom: Dm_ep_engine port's mechanism does not work properly
          on NT. It attemps to use port 45316 instead of 1200,
          increasing then (if this port is in use) of more than
          one as it should do.
  
 APAR IY20587
 Symptom: Universal collection, appStatus and appInstances 
          monitors do not return the correct value when
          run on an NT/W2k Endpoint, with argument "lcfd".

 APAR IY21519
 Symptom: There is a case where the unix_sentry monitor percent
          diskused returns the value for a wrong filesystem:
          It returns the value for the remote file system instead 
          of the local one, when the name of the local is contained 
          in the name of the remote, i.e. "/home" is the local
          and "/mnt/home" is the remote.

 APAR IY07377
 Symptom: Editing a DM profile places a lock to the odb.bdb and 
          consequently the odb.log file grows to be quite large.

 APAR IY18141
 Symptom: The $root_user/widmap mechanism trap the netware 
          machine when a DM profile is distributed

 APAR IY13987
 Symptom: Crypted files under ".sntcfg" directory sometimes
          get corrupted. This happens especially during a machine
          reboot.

 APAR IY16833
 Symptom: Dm_ep_engine dies while running an NT monitor using
          wntmon. This happens sometimes when other application
          using performance monitors are up and running.

 APAR IY22069
 Symptom: Monitor print queue status does not work on solaris
          and hp platforms: It always returns "UP" also when 
          the printQ is disabled.

 APAR IY15296
 Symptom: DM NT_Memory monitoring collection doesn't support 
          "% Committed Bytes in Use" Performance Monitor.
 
 APAR IY15834
 Symptom: 3.6.2-DMN-0001 introduced support for the use 
          of $root_user in SentryProfiles.
          This work so long without using the w32-ix86 
          special keyword: BuiltinNTAdministrator 
          On NT platform, using this special keyword in the 
          widmap for $root_user causes the authentication
          to fail .
             
 APAR IY16366
 Symptom: DM_EP_ENGINE fails to start with encryption errors 
          on WinNT 4.0

 APAR IY18614
 Symptom: When 'NT Service Status'-monitor is used to observe a
          NT-Service, it will show incorrectly either up or down if
          there is a system error from either "findstr" or "net start"
          In these situation it should generate an E.EXEC exit result.

 APAR IY19661
 Symptom: Sentry_gateway.exe memory leak on Windows 4.0 Gateway

 APAR IY05134
 Symptom:  In the Tivoli desktop, when viewing a DM Profile,
           monitor names longer than about 37 characters are being
           truncated in the monitor name column.  The name is 
           truncated with ellipsis (i.e. "..." appended at the end).


 APAR IY11515
 Symptom:  When a monitor' schedule start time is edited and the start 
           time is set for a date in the future, after a daylight saving
           switch over (on/off), then the time is altered of 1 hour.
    

Architecture(s): Solaris, AIX 4.1, HP-UX 10/11, OS/2
                 Windows NT 4.0, AS/400, NetWare 4.1 and 5.0

Patches superseded by this patch: None

Dependencies: 3.6.2-DMN-0023

Database Changes: None

Files Replaced or Added by this Patch 
 (for all supported values of $INTERP):
 $BINDIR/TME/SENTRY/sentry_engine(.exe)
 $BINDIR/TME/SENTRY/dog(.exe)
 $BINDIR/TME/SENTRY/dogEndpoint(.exe)
 $BINDIR/TME/SENTRY/dogGUI(.exe)
 $BINDIR/TME/SENTRY/crtproxy(.exe)
 $BINDIR/TME/SENTRY/proxy(.exe)
 $BINDIR/TME/SENTRY/mkCapCall(.exe)
 $BINDIR/TME/SENTRY/proxyep(.exe)
 $BINDIR/TME/SENTRY/sentry_gateway(.exe)
 $BINDIR/TME/SENTRY/mkdefault.sh
 $BINDIR/bin/dogcli(.exe)
 $BINDIR/bin/mcsl(.exe)
 $BINDIR/bin/waddchan(.exe)
 $BINDIR/bin/waddcrit(.exe)
 $BINDIR/bin/waddcust(.exe)
 $BINDIR/bin/waddlevel(.exe)
 $BINDIR/bin/waddmon(.exe)
 $BINDIR/bin/waddprb(.exe)
 $BINDIR/bin/waddprxenv(.exe)
 $BINDIR/bin/waddra(.exe)
 $BINDIR/bin/waddsnti(.exe)
 $BINDIR/bin/waddtime(.exe)
 $BINDIR/bin/wasync(.exe)
 $BINDIR/bin/wclreng(.exe)
 $BINDIR/bin/wclrsntlog(.exe)
 $BINDIR/bin/wcrtprx(.exe)
 $BINDIR/bin/wcrtsntcoll(.exe)
 $BINDIR/bin/wdelchan(.exe)
 $BINDIR/bin/wdelcrit(.exe)
 $BINDIR/bin/wdelcust(.exe)
 $BINDIR/bin/wdellevel(.exe)
 $BINDIR/bin/wdelmon(.exe)
 $BINDIR/bin/wdelprb(.exe)
 $BINDIR/bin/wdelra(.exe)
 $BINDIR/bin/wdelsnti(.exe)
 $BINDIR/bin/wdeltime(.exe)
 $BINDIR/bin/wdisprb(.exe)
 $BINDIR/bin/wdisra(.exe)
 $BINDIR/bin/wdistime(.exe)
 $BINDIR/bin/wdumpsnt(.exe)
 $BINDIR/bin/wenblprb(.exe)
 $BINDIR/bin/wenblra(.exe)
 $BINDIR/bin/wenbltime(.exe)
 $BINDIR/bin/wengine(.exe)
 $BINDIR/bin/wgdread(.exe)
 $BINDIR/bin/wgetprxenv(.exe)
 $BINDIR/bin/wgetsntid(.exe)
 $BINDIR/bin/wloadsnt(.exe)
 $BINDIR/bin/wlschan(.exe)
 $BINDIR/bin/wlscoll(.exe)
 $BINDIR/bin/wlscrit(.exe)
 $BINDIR/bin/wlscust(.exe)
 $BINDIR/bin/wlseng(.exe)
 $BINDIR/bin/wlslevels(.exe)
 $BINDIR/bin/wlsmon(.exe)
 $BINDIR/bin/wlsprb(.exe)
 $BINDIR/bin/wlsresp(.exe)
 $BINDIR/bin/wlssntcoll(.exe)
 $BINDIR/bin/wlssntlog(.exe)
 $BINDIR/bin/wlstime(.exe)
 $BINDIR/bin/wpauprb(.exe)
 $BINDIR/bin/wpaura(.exe)
 $BINDIR/bin/wpautime(.exe)
 $BINDIR/bin/wrespond(.exe)
 $BINDIR/bin/wresprb(.exe)
 $BINDIR/bin/wresra(.exe)
 $BINDIR/bin/wrestime(.exe)
 $BINDIR/bin/wrstsntlog(.exe)
 $BINDIR/bin/wrunprb(.exe)
 $BINDIR/bin/wsaveeng(.exe)
 $BINDIR/bin/wsetcoll(.exe)
 $BINDIR/bin/wsetcrit(.exe)
 $BINDIR/bin/wsetmon(.exe)
 $BINDIR/bin/wsetprxenv(.exe)
 $BINDIR/bin/wsetsnti(.exe)
 $BINDIR/bin/wsetsntid(.exe)
 $BINDIR/bin/wsic(.exe)
 $BINDIR/bin/wstopeng(.exe)
 $BINDIR/bin/wlogfile(.exe)
 $BINDIR/bin/wrexec(.exe)
 $BINDIR/bin/wnotice(.exe)
 $BINDIR/bin/wpopup(.exe)
 $BINDIR/bin/wicon(.exe)
 $BINDIR/bin/wmail(.exe)
 $BINDIR/bin/wtec(.exe)
 $BINDIR/bin/wdmgwcfg(.exe)
 $BINDIR/bin/wgateway(.exe)
 $BINDIR/bin/waddinsp(.exe)
 $BINDIR/bin/wdelinsp(.exe)
 $BINDIR/bin/wlsinsp(.exe)
 $BINDIR/bin/webicli(.exe)
 $BINDIR/../bin/lcf_bundle/bin/%INTERP%/TME/SENTRY/dogEndpoint
 $BINDIR/../bin/lcf_bundle/bin/%INTERP%/TME/SENTRY/sentry_gateway
 $BINDIR/../bin/lcf_bundle/bin/%INTERP%/TME/SENTRY/sentry_engine
 $BINDIR/../bin/lcf_bundle/sentry/%INTERP%/dm_ep_engine 
 $BINDIR/../bin/lcf_bundle/sentry/%INTERP%/wstopeng
 $BINDIR/../bin/lcf_bundle/sentry/%INTERP%/wlseng
 $BINDIR/../bin/lcf_bundle/sentry/%INTERP%/wrunprb
 $BINDIR/../bin/lcf_bundle/sentry/%INTERP%/wstopeng
 $BINDIR/../bin/lcf_bundle/sentry/%INTERP%/wclreng
 $BINDIR/../bin/lcf_bundle/sentry/%INTERP%/wasync
 $BINDIR/../bin/lcf_bundle/sentry/%INTERP%/wenblprb
 $BINDIR/../bin/lcf_bundle/sentry/%INTERP%/wdisprb
 $DBDIR/..msg_cat/C/ntHelp.cat
 $DBDIR/../msg_cat/C/nt.cat


Patch Contents:

        - This README file
        - A cdrom image for this patch 

Applying the Patch:

   1) 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_DMN-0024.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-DMN-0024.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 images.
        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-DMN-0024 using the file browser,
            and select the PATCHES.LST file by double-clicking it
        g)  Select 3.6.2-DMN-0024 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-DMN-0024 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-DMN-0024 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 you want to install 3.6.2-DMN-0024 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 old
      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. This patch
           changes binaries and needs to be installed on the TME 
           server and on each client.

       g)  Press the "Install" button to install the patch.


Additional Installation Instructions: 


   If you have been monitoring your TMA endpoints with DM, you'll need
   to perform the following steps logged in as root or Administrator:

   1) On your TMR server or any managed node, execute the shell
      script $BINDIR/TME/SENTRY/dm_ep_stop.sh.

          This will determine the list of endpoints that have had
          dm_ep_engine running on them since the DM 3.6GA release.
          The script will then attempt to stop the dm_ep_engine on
          each endpoint in the list.  wstopeng -z <ep_name> is
          started in the background for each endpoint in the list.
  
      Note: Since wstopeng is started in the background to accommodate
      large numbers of endpoints, it is important to ensure that all
      instances of wstopeng have completed before going on to the
      next step.  Also, another purpose of this step is to ensure
      that the patched version of the 'sentry_engine' binary gets
      downloaded to the TME endpoint.

   2)  On your TMR server execute the shell script
       $BINDIR/TME/SENTRY/dm_gate_stop.sh.

         This will stop all sentry_gateway processes. The command
         prompt may return quickly, but the actual termination
         of each sentry_gateway may take awhile since it will
         clear its queues of all requests before quitting. It is 
         recommended that you not continue to the next step until
         you are certain that all sentry_gateway processes have
         been stopped.

   3) Perform a profile distribution, using as many profiles as
      needed, to reach each TMA endpoint. This step will ensure
      that all the updated binaries provided in this patch are
      downloaded for subsequent use on your TMA endpoints.

Known Defects: None.

