Date:   April 7, 2005

Patch:  3.7.1-LCF-0024

Component: Tivoli Framework 3.7.1

General Description:

    3.7.1-LCF-0024 is a patch for endpoints. Although this is a 3.7.1
    endpoint patch, it can be installed on 3.7, 3.7.1, 4.1, or 4.1.1
    systems to  allow for subsequent endpoint upgrades / support.
    3.7.1-LCF-0024 supersedes all previous 3.7 and 3.7.1 endpoint
    patches, efixes, and fixpacks (a complete list is provided below).
    If installed on a 3.7 system, then it is recommended that
    3.7-TMF-0016 be installed first. It's also recommended, but not
    required, that 3.7.1-TMF-0146 and 3.7.1-TMF-0126 be installed in
    conjunction with 3.7.1-LCF-0024 in 3.7.1 environments for additional
    fixes.

Problems Fixed:

  New fixes in 3.7.1-LCF-0024:

    Internal CMVC defect 174803
    Symptoms: When an endpoint fails to bind its preferred port, the
    exact cause of the error is not logged, which makes diagnosis of the
    problem difficult.

    APAR IY61722
    Symptoms: According to the 'Enterprise Installation Guide', the
    lcfd<x>.rc file should be installed in the /etc/init.d directory on
    Solaris endpoints. Instead, that file is installed in the
    /sbin/init.d directory if it exists.

  Fixes from 3.7.1-LCF-0021:

    Internal CMVC defect 175597
    Symptoms: The fix for 174400 in 3.7.1-LCF-0020 caused a problem when
    tasks were run on endpoints that had not yet been upgraded to
    3.7.1-LCF-0020. Tasks run on these older endpoints would timeout and
    get a relocation error similar to "symbol cpl_tmpnam: referenced
    symbol not found".

    Additional Information: If 3.7.1-LCF-0020 has already been installed
    on a gateway, the installation of this patch on that same gateway
    will correct the problem reported in defect 175597. That is, older
    endpoints and endpoints where 3.7.1-LCF-0020 was previously
    installed do not have to be upgraded to 3.7.1-LCF-0021 in order to
    have the fix for 175597.

  Fixes from 3.7.1-LCF-0020:

    Internal CMVC defect 174400
    Symptoms: Setting the LCF_TEMPDIR environment variable does not set
    the value of LCF_TEMPDIR actually used by the lcfd and the methods
    that lcfd spawns.

    Additional Information: The fix for 174400 changes this behavior so
    that setting the LCF_TEMPDIR environment variable will now directly
    set the value of LCF_TEMPDIR used by lcfd. (Caveat: On Windows, if
    LCF_TEMPDIR is used to change the temporary directory used by the
    endpoint, the machine must be rebooted before the endpoint can use
    the change since the Service Control Manager won't pick up the
    change until Windows is restarted.)

    In addition:

    * Specifying "-D temp_dir=<dir>" on the lcfd command line will set
      the LCF_TEMPDIR. (Note: During endpoint installations using
      winstlcf, the lcfd command line option "-D temp_dir=<some dir>"
      can be specified with the -L option on winstlcf. For endpoint
      installations using setup.exe, the "-D temp_dir=<some dir>" can be
      specified in the Options field of the Advanced Configuration
      screen.)

    * Specifying "temp_dir=<dir>" in the last.cfg file on the endpoint
      will set the LCF_TEMPDIR. 

    If either of the above two methods are used to change the temporary
    directory, the endpoint must be restarted for this change to take
    effect. If the temporary directory is set in multiple places, then
    when the lcfd starts up, it will choose the value using the
    following priority:

    1. "lcfd -D temp_dir=<dir>" (always used if set)
    2. last.cfg (used if the above method is not used)
    3. LCF_TEMPDIR environment variable (used if neither of the above
       two methods are used)

    APAR IY55102
    Symptoms: The lcf.dat file is not created on the endpoint if the
    login information from the gateway is received after the "cti_accept
    (timeout=65)" has elapsed.

    APAR IY56312
    Symptoms: When patch 3.7.1-LCF-0017 is installed on Windows 2000 and
    the endpoint's web page (http://xxx.xxx.xxx.xxx:9495) is opened,
    then selecting "show trace log" (http://xxx.xxx.xxx.xxx:9495/tlog)
    can cause the endpoint to terminate abnormally.

    APAR IY56646
    Symptoms: When an upgrade is done on an endpoint, a shutdown and a
    restart of the lcfd service is done. Sometimes, the shutdown service
    call takes a long time and before it completes, a start for lcfd is
    issued. This restart fails because it sees that lcfd is running and
    doesn't retry starting the service.

    APAR IY58297
    Symptoms: During a log rollback operation on a Netware server, the
    server can terminate abnormally.

    APAR IY59018, Internal CMVC defect 173138
    Symptoms: During lcfd service shutdown for some Windows XP and
    Server 2003 machines, an application error dialog (usually an access
    violation or privileged instruction) may be generated.

    APAR IY63688
    Symptoms: When a 3.7.1 Windows endpoint is upgraded to patch
    4.1.1-LCF-0008 and that upgraded endpoint is then used as a proxy
    for the installation of new endpoints, the winstlcf command fails to
    install the new endpoint because of a missing TivoliAP.dll on the
    proxy machine.

    Additional Information: A fix related to this fix for IY63688 is
    provided in patch 4.1.1-LCF-0010 via internal defect 175254.

  Fixes from 3.7.1-LCF-0019LA:

    APAR IY54241
    Symptoms: When the dm_ep_engine is started by the "wlseng -z EP"
    command or launched by lcfd, endpoint port 9495 remains in
    CLOSE_WAIT state. The port status is not recovered until the
    dm_ep_engine is stopped.

  Fixes from 3.7.1-LCF-0018:

    APAR IY45863
    Symptoms: If the Tivoli Authentication Package (TAP) is configured
    so that the domain user is locked out when the user fails to logon
    correctly three times, for example, the message that is displayed is
    not one about an "Account Lockout", but rather is "Unknown user name
    or bad password".

    APAR IY46529
    Symptoms: If the start_delay parameter in the last.cfg file is set
    to a value larger than 15 seconds, then it will be reset to 15
    seconds when the endpoint is upgraded.

    APAR IY49044
    Symptoms: When creating multiple AEF actions of the same type for
    user or group profiles, the actions are generated and queued as
    expected.  However, when the distribution that initiates the actions
    is performed, the last action of any type executes multiple times,
    and the other actions of the same type do not execute at all.

    APAR IY51443, Duplicate of APAR IY53319
    Symptoms: After multiple (20+) execute program actions have been run
    on an endpoint, further attempts to run an execute program action
    can cause spd_eng.exe exceptions until the lcfd is restarted.

    APAR IY53132
    Symptoms: Upcalls from an endpoint to a gateway can fail if DES is
    enabled on the gateway and allow_proxy_upcalls is set to true on the
    endpoint.

    APAR IY54373
    Symptoms: When trying to pass the redirection character '>' as an
    argument to a task, the task fails with a syntax error.

    APAR IY54395
    Symptoms: If a space is appended to the end of a numeric value, such
    as the lcfd_port value, in the last.cfg file, then the value will be
    ignored and reset to the default value (i.e., 9495 for lcfd_port)
    when the endpoint is restarted.

    APAR IY54808
    Symptoms: 3.7.1-LCF-0016 does not always set the gateway
    "bundles_map" correctly.

    Additional Information: This was originally closed in 3.7.1-LCF-0017
    when the problem could not be reproduced in that patch, but after
    further analysis, a script fix was made for 3.7.1-LCF-0018.

  Fixes from 3.7.1-LCF-0017:

    Internal CMVC defect 168929
    Symptoms: When allow_proxy_upcall is TRUE, the endpoint processes
    upcalls through the upcall proxy mechanism. To manage the upcall
    pool, old connections that have not been processed are removed. If
    these connections are removed and a request for data arrives, an
    error message should be returned instead of attempting to send data
    that no longer exists.

    Internal CMVC defect 169428
    Symptoms: For endpoints on non-MULTIPROTO platforms, such as AIX,
    Solaris, etc., the following steps can cause a problem: If an
    endpoint logs into its assigned gateway, the gateway shuts down, the
    endpoint then migrates to an alternate gateway, and a downcall is
    performed, then the endpoint may attempt to log in to the original
    gateway.

    Internal CMVC defect 169682
    Symptoms: The Windows bash.exe command does not correctly handle
    newline characters within a data stream.

    APAR IY46121
    Symptoms: When the Unix winstlcf command is used to install Windows
    endpoints with a proxy, it makes an idlcall with the admin password
    argument in clear text. This argument should be encrypted.

    Additional Information: The fix for this APAR requires this patch as
    well as the fix made to winstlcf in 3.7.1-TMF-0127.

    APAR IY51380
    Symptoms: When allow_proxy_upcall=true is enabled, each upcall
    generated by an application is queued at the endpoint to wait for
    data coming / going to the gateway / endpoint. In some cases, such
    as when the gateway is down or the gateway / endpoint is very busy,
    this can lead to 100% CPU utilization on the endpoint.

    Additional Information: When the allow_upcall_proxy=true is set, the
    endpoint operates in upcall proxy mode. The fix for this APAR adds
    two additional parameters, upcall_pool_size and upcall_pool_timeout,
    to the endpoint configuration to allow for the control of upcall
    proxy behavior.

    The upcall_pool_size configuration parameter specifies a maximum
    for the number of connections in the proxy upcall pool. When the
    number of connections in the proxy upcall pool reaches and exceeds
    this value, the older connections in queue are gracefully aborted to
    make room for newer proxy upcall connections. The default value for
    the upcall_pool_size is 100. This value is reset to the default
    value if the upcall_pool_size is set to 0 or less than zero. The
    upcall_pool_size should not be set to be greater than the maximum
    number of file descriptors specified by the 'ulimit -a' (on UNIX
    platforms). The upcall_pool_size should be a low value rather than a
    large value.

    The upcall_pool_timeout configuration parameter specifies the
    maximum number of seconds that a proxy upcall connection can reside
    in the pool until it is gracefully aborted to make room for newer
    proxy upcall connections. The default value for upcall_pool_timeout
    is 60. This value is reset to the default value if the
    upcall_pool_timeout is set less than or equal to the value of the
    recvDataTimeout.

    Note: It is not necessary to restart your endpoint in order for
    changes made to upcall_pool_size and upcall_pool_timeout to take
    effect.  However, in some situations it may be beneficial to restart
    the endpoint if these parameters are changed.  Specifically:

    * If you accidently set a parameter to an invalid value, such as
    setting upcall_pool_size to zero, the endpoint will attempt to use
    this invalid value, which can cause problems.  Restarting the
    endpoint will automatically validate all parameters and reset any
    invalid values to the appropriate default values.

    * Decreasing the upcall_pool_size can cause upcalls to be lost in
    some situations.  For example, if the upcall_pool_size was set to
    1000 and the pool size actually being used was 200, then setting
    upcall_pool_size to 100 would cause upcalls in the pool to be
    discarded to achieve the 100 setting.  In a situation such as this,
    it might be beneficial to restart the endpoint to resynchronize with
    this lower value.  It should be noted that if the upcall_pool_size
    were set to 200 (or a larger value) in this example, then no upcalls
    would be lost and no restart of the endpoint would be necessary.

    APAR IY54808
    Symptoms: 3.7.1-LCF-0016 does not set the gateway "bundles_map"
    properly. (This problem could not be reproduced in 3.7.1-LCF-0017.)

  Fixes from 3.7.1-LCF-0016:

    Internal CMVC defect 165003
    Symptoms: When Netware endpoints are installed, the cache library is
    not included in the path.  Thus, when a method from an application,
    such as Software Distribution, is loaded from the gateway to the
    cache, it can not be  run.  The solution is to change the LCF.NCF
    startup file to include the cache library in the path.

    Additional Information: The fix for this defect corrects the
    reported problem for new endpoint installations, not for endpoints
    that were upgraded to this patch level. A fix for upgraded endpoints
    is planned for a future patch.

    APAR IY46968
    Symptoms: A task that executes /usr/sbin/shutdown on AIX cannot be
    run as a non-root user, even when the user is part of the shutdown
    group.

    APAR IY46986
    Symptoms: The installation of lcfd.exe with the setup command
    generates a logfile that gives a detailed account of the
    installation process and any errors that occur.  However, this
    logfile is stored in the support directory and is erased as soon as
    the install completes or fails.  The fix for this APAR saves the
    logfile in the system temp directory where it will not be deleted.
    Thus, information on why an installation failed will not be deleted.

    APAR IY48151
    Symptoms: When a dependency in the endpoint cache gets corrupted
    (for some reason), the dependency is not downloaded to the endpoint
    again because the endpoint only checks for the existence of the
    file, but it doesn't check its size.

    APAR IY48158
    Symptoms: When an endpoint logs into a gateway that has more than
    one NIC, the endpoint can successfully login to the gateway through
    one interface, but if it then receives a communication from one of
    the other interfaces, it will cause it to retry the login process to
    this new interface.

    APAR IY48425
    Symptoms: The TEC-Winadapter causes CLOSE_WAIT states on Windows
    2000 endpoint ports when the endpoint network adapter is disabled. 

    APAR IY48440
    Symptoms: The Tivoli Authentication Package (TAP) fails and returns
    an error indicating that the specified domain either does not exist
    or cannot be contacted when authenticating a domain user with a
    domain name NETWORK.

    Additional Information: The fix in this patch is only applicable to
    endpoints.  Patch 3.7.1-TMF-0124 contains this fix for TMRs /
    managed nodes / gateways.

    APAR IY49345
    Symptoms: If the run_dir variable (i.e., in the last.cfg file and
    the Windows registry) contains an extra "\" at the end, then this
    can cause problems for Remote Control when accessing an endpoint.

    APAR IY51010
    Symptoms: Endpoint version 37113 has problems logging into the
    gateway if the select_ gateway policy returns '<gw_oid> |
    <gw_hostname>'.  The lcfd log file contains a message similar to
    "lcfd gw login failure: GW index = 0 : unable to resolve gateway
    hostname -> <gw_name>".

  Fixes from 3.7.1-LCF-0015LA:

    APAR IY49030
    Symptoms: Netware endpoints can lose their connection to the gateway
    after some period of normal operation once Distributed Monitoring
    Fixpack 5 is installed.  The LCFD.NLM appears to be hung.

  Fixes from 3.7.1-LCF-0014LA:

    APAR IY46127
    Symptoms: Running upcalls on endpoints with allow_proxy_upcalls=true
    can prevent the temporary files created in $LCF_DATDIR/updata from
    being cleaned up if the upcall fails.  These files are normally
    cleaned up when the endpoint is restarted, but they can accumulate
    between restarts.

    APAR IY47906
    Symptoms: When the WEB_SERVER_SITE_NAMES variable of the app_context
    attribute is over a certain size, the tmw2k_ep process of ITM can
    terminate abnormally.

    APAR IY49269
    Symptoms: A task execution on a Windows NT 4.0 system can sometimes
    causes a Dr. Watson error (i.e., an access violation) in the module
    repository_lookup. Subsequent executions of the same task often work
    correctly, however.

  Fixes from 3.7.1-LCF-0013 (includes fixes from the earlier test fix
    3.7.1-TMF-0108T): 

    Internal CMVC defect 157142
    Symptoms: In some circumstances, the upgrade mechanism on w32-ix86
    fails to restart the lcfd service.  The admin_rpt process should
    wait until the lcfd process starts up before continuing.

    APAR IY34897
    Symptoms: When pre-3.7B NetWare endpoints are upgraded to post-3.7B
    endpoints, the LCFD.NLM cannot be restarted because the LCF.NCF
    specifies old library names instead of the new library names.

    Additional Information: This fix is in the 3.6.5 lcf_bundle included
    in this patch and is also listed in the 3.6.5-TMF-0020 section
    below. 

    APAR IY39408
    Symptoms: On Windows NT / 2000 endpoints with account logon / logoff
    auditing policy enabled, the system security event log indicates
    logon / logoff entries for the Administrator and tmersrvd accounts.
    The token caching mechanism needs to be changed so that no tokens
    are generated, which will eliminate these logon / logoff entries.

    APAR IY40159
    Symptoms: When running in an environment with a Microsoft ISA Server
    where all the endpoints have Microsoft Firewall client installed as
    LSP (Layered Service Provider), enabling the client causes the
    endpoint to be unable to communicate with the gateway.  When
    disabled, endpoint communication is restored.

    APAR IY42743
    Symptoms: Each time a connection is made to an endpoint, the LCFD
    handles the incoming connection and then checks for an additional
    connection. If there is no additional connection activity, the
    additional connection handles are not closed properly, which causes
    a memory leak.

    APAR IY42815
    Symptoms: On Sun and HP endpoints, the command "wep <ep> set_config
    lcs.unique_machine_id=<28_char_value>" modifies the machine's unique
    machine id, but if the endpoint is restarted, it is reset to the
    original default value. 

    APAR IY43487
    Symptoms: When an endpoint log file is flooded with lots of messages
    and the log_size parameter is not set large enough, then the
    task_endpoint program running on the endpoint can terminate
    abnormally.

    APAR IY44766
    Symptoms: Upgrading to endpoint version 109 causes a blank endpoint
    label tab to appear in the LCFEP statistics popup window on Windows
    95 / 98 endpoints.

  Fixes from 3.7.1-TMF-0102LA:

    Internal CMVC defect 155006
    Symptoms: The mrt_machine_id() API provided by the libmrt272 library
    is exported to applications who may or may not have the proper
    definitions to use this API.  In particular, this can cause the
    Linux DM_EP_ENGINE to terminate abnormally.

    Additional Information: This fix in this patch for 155006 together
    with Distributed Monitoring (DM) patch 3.7-DMN-0046LA enables DM on
    supported Linux platforms.

    Internal CMVC defect 155685
    Symptoms: Linux endpoints do not create the lcf.id file when the
    endpoint is started. This can cause problems for applications, like
    Distributed Monitoring, that need information from that file.

    APAR IY40599, Internal CMVC defect 154481
    Symptoms: If the Framework gateway (not the TEC gateway) starts and
    stops very frequently, such as on a three minute cycle, a TEC
    adapter communicating with that gateway can terminate abnormally.

    Additional Information: This fix is in the 3.6.5 lcf_bundle included
    in this patch and is also listed in the 3.6.5-TMF-0020 section
    below.

  Fixes from fix pack 3.7.1-TMF-0099:

    Internal CMVC defects 152601, 137673
    Symptoms: A distribution can be paused only once from the Mobile
    console progress dialog. After the distribution resumes, the
    progress bar immediately goes to the complete state even though the
    download has not finished. 

    Additional Information: The fix for this defect requires that the
    Mobile images in the PC/MOBILE subdirectory of fix pack
    3.7.1-TMF-0098 be installed.  It also requires the libmd2ep library
    installed by this patch, so this patch should be installed in
    conjunction with the Mobile images in fix pack 3.7.1-TMF-0098.

    Internal CMVC defect 153137
    Symptoms: Multi-threaded programs, such as ITM version 5.1, running
    on a Linux endpoint can hang when doing upcalls.

    APAR IY24961
    Symptoms: Endpoints crash if they cannot resolve a gateway hostname
    received in a login packet from the Endpoint Manager. The Endpoint
    Manager sends the hostname based on the select_gateway_policy, so an
    invalid name in the select_gateway_policy can cause this crash.

    APAR IY31787
    Symptoms: When an endpoint image is built and used to simultaneously
    update workstations, these workstations can end up with the same
    hardware system ID. This issue impacts inventory scans and TDS.

    Additional Information: The fix for this APAR used algorithms
    covered by the following copyright:

    Notice for the Network Working Group Internet Draft "UUIDS AND
    GUIDS," Which was Used to Create an ID-Generating Algorithm for IBM
    Tivoli Configuration Manager

    Copyright (C) The Internet Society 1997. All Rights Reserved.

    This document and translations of it may be copied and furnished to
    others, and derivative works that comment on or otherwise explain it
    or assist in its implementation may be prepared, copied, published
    and distributed, in whole or in part, without restriction of any
    kind, provided that the above copyright notice and this paragraph
    are included on all such copies and derivative works.  However, this
    document itself may not be modified in any way, such as by removing
    the copyright notice or references to the Internet Society or other
    Internet organizations, except as needed for the purpose of
    developing Internet standards in which case the procedures for
    copyrights defined in the Internet Standards process must be
    followed, or as required to translate it into languages other than
    English.

    The limited permissions granted above are perpetual and will not be
    revoked by the Internet Society or its successors or assigns.

    APAR IY34740
    Symptoms: When the wruntask command is used to run a task on an
    endpoint and one or more carets are specified for the "-a" parameter
    (i.e., wruntask -t <task> -l <lib> -h <ep> -o 015 -a "arg1^" -a
    "^arg2" -a "ar^g3"), then on Windows NT, 2000, or XP, the bash shell
    executing the command receives arguments with two carets for every
    one that was specified.

    APAR IY35980
    Symptoms: When running multiple endpoints on a single system, there
    is no simple way to determine which endpoint instance spawned a task
    or method. On UNIX, it is possible to process the LCF_DATDIR
    variable and extract the instance number, but other platforms (such
    as Windows NT) do not readily provide this capability for scripted
    tasks.

    Additional Information: The fix for this APAR is to create a new
    environment variable, LCF_INSTANCE. For each endpoint, the value of
    LCF_INSTANCE should match the instance number used in the LCF_DATDIR
    variable (and the lcfd-# service name for NT).

    NOTE: The fix for IY35980 is not provided on NetWare or OS/2
    endpoints since multiple endpoints are not supported on individual
    NetWare or OS/2 systems.

    APAR IY36681
    Symptoms: Limit the cases where the endpoint detects the need to
    switch to an alternate port due to a ConnectionLost exception caused
    by a "0 byte recv" exception in the listener loop.  This allows the
    endpoint to continue to use the same port in more ConnectionLost
    situations.

    APAR IY36695
    Symptoms: Daylight savings time changes can trigger the MDist2 depot
    to reload. 

    Additional Information: The fix for this APAR requires both the
    endpoint binaries provided in fix pack 3.7.1-TMF-0097 and the
    binaries provided in this patch.  Thus, both patches must be
    installed to have the fix for this APAR.

    APAR IY39360
    Symptoms: When an invalid or unknown HTTP request is received by the
    endpoint, it returns an error page to the browser which quotes the
    URL (minus the protocol and host portion).  This error page should
    not be returned to the browser.

  Fixes from 3.7.1-TMF-0095T (Test Fix):

    Internal CMVC defect 149661
    Symptoms: The fix for IY32431 in patch 3.7.1-TMF-0090 closed the
    file descriptor used for the lcfd.log file when a task is run on an
    endpoint.  However, closing the file descriptor led to two problems:
    1) stdout/stderr outputs were no longer written to the display
    window or log file for the task, and 2) after the task is run, the
    task_endpoint process does not log messages to the lcfd.log file.

    APAR IY22853
    Symptoms: If Windows NT endpoint version 40 (from the 3.6.2 GA
    release) is upgraded to a Tivoli Management Framework, version 3.7.1
    endpoint using "wadminep upgrade" from a Tivoli region, the upgrade
    is successful, but the endpoint file LCF37100.SIG might be missing
    on the endpoint.  This problem can also occur if this endpoint is
    used as proxy to install another Windows NT endpoint.

    APAR IY23078
    Symptoms: When a User Admin profile with at least 20 users is
    distributed to an endpoint, the AEF actions for only the first 19
    records in the profile are executed.

    APAR IY24385
    Symptoms: After the installation of patch 3.7.1-TMF-0021 as a new
    endpoint (where the endpoint has not successfully connected to its
    gateway yet), using the browser interface to interrogate the
    endpoint results in the display of an incorrect value for the
    hostname field on the resulting HTML page.

    APAR IY29890
    Symptoms: When running the wruntask command with the -i option
    (which reads standard input and passes it to the task as its
    standard input), text with umlauts is transferred correctly when the
    task is run on a managed node, but not when the task is run on an
    endpoint.

    APAR IY30925
    Symptoms: If an endpoint cannot log in to its gateway after an
    automatic upgrade, the "start_delay" variable can sometimes be set
    to an unreasonable value (4247232), which is equivalent to 49 days,
    before it will attempt another login.

    APAR IY32620
    Symptoms: Linux endpoints use the gethostid() system call to return
    a value that is used for the inventory hardware ID.  This value is
    built from the etc/host file contents, but for customers using DHCP,
    the etc/host file is not used, so the value is 0 for those
    endpoints.

    APAR IY32696
    Symptoms: When the "logfile=" option in the last.cfg is modified
    either by the "wep <ep> set_config" command or by directly modifying
    the last.cfg file, the modification is reverted to its previous
    value when the endpoint restarts. 

    APAR IY33193
    Symptoms: When an HP-UX endpoint is shut down, the endpoint attempts
    to execute the stop command in several rc files (rc0.d, rc1.d, and
    rc2.d).  This causes a log file error message since the first stop
    command is successful, but the other stop commands are not
    successful (because the endpoint is already stopped.)

    APAR IY33617
    Symptoms: If an endpoint running Windows 95/98/XP with LCF version
    94 or 98 is booted when not connected to the LAN, the LCFEP program
    can fail with an invalid page fault.  This typically happens with
    Mobile users.

    APAR IY34250
    Symptoms: The "-g" option on the winstlcf command allows customers
    to specify the gateway for a new endpoint to contact during login.
    When "-g" is specified and the endpoint is either rebooted or put
    into suspended mode before the endpoint has had a chance to login to
    the assigned gateway, the "login_interfaces" line in the last.cfg
    file is not saved, and the assigned gateway information is lost.  If
    broadcast mode is also disabled, the endpoint will not be able
    contact a gateway.

    APAR IY34438
    Symptoms: After a initial install or upgrade of a Windows XP
    endpoint to endpoint version 103, clicking on the Tivoli icon in the
    task tray brings up the statistics window, but this window is
    invisible because it matches the desktop background. The only way
    you can tell the window is open is because there is an icon on task
    bar.  The workarounds for this problem is to reboot, log out and log
    back in, or to stop lcfep (by selecting "remove icon") and then
    restart lcfep.

    APAR IY34974, APAR IY34806
    Symptoms: For endpoint patches prior to patch 3.7.1-TMF-0085, the
    installation of endpoint code on a Windows 2000 AD target would
    create the Tivoli_Admin_Privileges group as a Domain Local group and
    correctly add the installer IDs. After applying patch 3.7.1-TMF-0085,
    the Tivoli_Admin_Privileges group is created as a Global group and
    the installer IDs cannot be added to it.  The installation fails
    with a message similar to: "Install failed to give you membership
    in the group Tivoli_Admin_Privileges".

    Additional Information: The fix for this APAR requires both the
    endpoint binaries provided in this patch and the binaries provided
    in 3.7.1-TMF-0093 or fix pack 3.7.1-TMF-0097. Thus, both patches
    must be installed to have the fix for this APAR.
    
    NOTE: the fix for APAR IY34974 also corrects the problem reported in
    APAR IY34806.

    APAR IY35064, Internal CMVC defect 149800
    Symptoms: The new LCFD parameters (recvDataTimeout,
    recvDataNumAttempts, and recvDataQMaxNum) introduced in patch
    3.7.1-TMF-0062E can result in tasks failing when a short default
    timeout expires. The error message will be similar to: "The task
    failed to execute.  Data was not received because the connection was
    reset by the peer. ipc_recv failed: connection reset by peer".

  Fixes from 3.7.1-TMF-0091 (Limited Availability release):

    Internal CMVC defect 150720
    Symptoms: The upgrade of Linux-ix86 endpoints fails when upgrading
    from an earlier version to endpoint version 107 and displays a
    message that file libmrt.so could not be opened.

    APAR IY32278
    Symptoms: The shutdown of a Windows 95/98 endpoint can cause the
    following error to be displayed: "Microsoft Visual C++ Runtime
    library Runtime Error. Program
    C:\Program Files\Tivoli\lcf\bin\win95\mrt\lcfd.exe".

    APAR IY35138
    Symptoms: File names in non-DOS format are truncated because the
    NetWare ADMIN.NLM is loaded without long file name support.

  Fixes from 3.7.1-TMF-0090 (includes fixes from 3.7.1-TMF-0085,
    3.7.1-TMF-0085A, and 3.7.1-TMF-0086): 

    Internal CMVC Defect 146644.1
    Symptoms: A fix was made in patch 3.7.1-TMF-0075 for a problem in
    which the lcfd could crash when it cannot resolve a non-existent
    hostname in its interface list.  This fix is extended to cover some
    additional situations.

    Internal CMVC defect 148952
    Symptoms: When "address_notif_interval" is set to a value, such
    as 5, in the last.cfg file, the lcfd executable can exhibit a memory
    leak.

    APAR IY24195.1
    Symptoms: The Inventory GUI fails when it tries to execute a task on
    a Windows NT endpoint.  A wrunuiep error message is displayed
    stating that a memory location could not be read.

    Additional Information: The fix for this problem removes an earlier
    fix that was intended for future use by Software Distribution.
    Because the current releases of Software Distribution have addressed
    APAR IY24195 without requiring any Framework changes, this
    earlier fix is not currently needed.

    APAR IY34160 / Internal CMVC Defect 148175)
    Symptoms: Downcalls to endpoints (for example, the "wadminep
    view_version" command) or upcalls from endpoints can cause the
    handle count to increase by one for each downcall or upcall.

    APAR IY34335
    Symptoms: The fix for APAR IY32431 in 3.7.1-TMF-0080E added a
    feature so logging to LCFD.LOG could be disabled when executing
    tasks on endpoints via the task_endpoint(.exe) method. This fix
    called a new LogClrLogfileValid() entry point in the libmrt
    library. When 3.7.1-TMF-0080E was installed on a gateway, tasks that
    were run on AIX endpoints that had not yet been upgraded would fail
    because the LogClrLogfileValid() entry point was not present in the
    libmrt library on the AIX endpoint. 

  Fixes from 3.7.1-TMF-0080E:

    Internal CMVC defect 142657
    Symptoms: APAR IY25091 added functionality to update the endpoint's
    machine unique ID with the following command:

      wep <ep> set_config lcs.machine_unique_id=...

    While the APAR changes do allow the updating of the data stored in
    the endpoint manager database and the data stored on the endpoint's
    lcf.id file, these changes do not update the unique ID stored in the
    lcf.dat file.

    APAR IY20724
    Symptoms: The value of szDir in the section SdComponentDialog-0 of
    the lcf silent installation script that is shipped with the lcf
    installer has the hard-coded value C:\Program Files\Tivoli\lcf. This
    should be changed so that szDir has a value of " " -- that is, a
    space surrounded by quotes.  This setting causes the silent
    install to use the default location to install the lcf images.

    Additional Information: The fix for this APAR is provided in the
    InstallShield images included in this patch.

    APAR IY21597
    Symptoms: The env.exe command uppercases all environment variables
    on Windows NT.

    Additional Information: The fix for env.exe in this patch is for
    endpoints.  The fix in patch 3.7.1-TMF-0088 is for Tivoli regions
    and managed nodes.

    APAR IY22415
    Symptoms: The ntfsinfo.exe binary calculates invalid percent values
    for disk drives with a huge capacity.

    Additional Information: The fix for ntfsinfo.exe in this patch is
    for endpoints.  The fix in patch 3.7.1-TMF-0088 is for Tivoli
    regions and managed nodes.

    APAR IY26496
    Symptoms: When installing a Windows 2000 endpoint, the Back button
    does not behave as expected in the following situations: 
      1) On the "Endpoint installation options" page, clicking Back
      returns to the "Welcome" page instead of the "License" page.
      2) On the "Endpoint Installation" page, clicking Back behaves
      like selecting Next; that is, both buttons take you to the next
      screen, "Setup complete."
      3) After the installation is complete, it does not prompt you to
      restart.

    Additional Information:
    NOTE 1: For item 2), the Back button should not be enabled in this
    situation, so the fix for this APAR was to disable the Back button.
    For item 3), no fix was necessary.  A reboot is not requested if TAP
    is already installed on the machine, or if (on Windows 95/98) there
    are shared files that could not be overwritten during installation.
    Thus, the installation does not always prompt for a reboot.
    However, if more predictability is required, then in the case of a
    silent installation, the user can record a silent installation
    script not including the reboot prompt and pass the option rebootok
    to the installer during the silent installation to cause a reboot to
    happen. 
    
    NOTE 2: This fix for this APAR is provided in the InstallShield
    images included in this patch.

    APAR IY26653
    Symptoms: In an environment where: 1) there are two Windows NT
    domain controllers, domain_1 and domain_2, 2) domain_2 trusts
    domain_1, 3) a Windows 2000 machine is a member of domain_2, 4) an
    endpoint is installed on the Windows 2000 machine, and 5) the TRAA
    account is set to "domain_1\Administrator", then running wlcftap
    returns the following error: "The specified domain either does
    exist or could not be contacted".

    Additional Information:
    NOTE 1: the fix in this patch is only applicable to endpoints. Patch
    3.7.1-TMF-0088 provides this fix for Tivoli region servers and
    managed nodes.
    
    NOTE 2: A reboot is required to complete the installation of the
    TivoliAP.dll that is modified by the fix for IY26653.
    
    NOTE 3: If an account using trusted domain accounts tries to upgrade
    a Windows 2000 server to endpoint version 106 (or later) without
    first disabling the TRAA account, the upgrade may return error
    messages saying the upgrade failed.  However, the upgrade was
    actually successful, and when the endpoint is rebooted, the
    TivoliAP.dll provided in this patch is loaded.

    APAR IY27248
    Symptoms: The silent install of the Tivoli Management Agent is not
    actually silent because two DOS popup windows write information to
    the screen.

    Additional Information: This fix for this APAR is provided in the
    InstallShield images included in this patch.

    APAR IY29100
    Symptoms: Upgrading an endpoint from version 3.7 to 3.7.1 when
    nobody is logged on to the desktop or when the desktop is locked
    causes the upgrade to fail to add the lcfep icon to the taskbar
    area and to the registry.

    APAR IY29254
    Symptoms: Upgrade of endpoint using wadminep fails if locked files
    are encountered. The error is similar to: "** Exception caught in
    run_impl: lcfmove, rename src 
    d:\Tivoli\lcf\bin\w32-ix86\mrt\upgrade\libmrt.dll to dest
    d:\Tivoli\lcf\bin\w32-ix86\mrt\upgrade\lib.tmp failure, errno is 17
    FAILED upgrading endpoint '<epname>' do_upgrade_rpt, error return
    from iom_mdist".

    APAR IY30319
    Symptoms: The lcfd in endpoint patch 3.7.1-TMF-0033 (endpoint
    version 95) cannot be loaded on Netware 5.1 systems running in
    protected mode.

    APAR IY32431
    Symptoms: When a task is run on an endpoint, the file descriptor
    used for the lcfd.log file is not closed, which can cause problems
    if the script wants to perform an operation such as unmounting the
    file system.

    Additional Information: The fix for this APAR is to make a check for
    the environment variable TaskEnableCloseFD.  If this environment
    variable is present and has a value of 1, then the lcfd.log file
    descriptor will be closed before the task is executed. 

    APAR IY32450
    Symptoms: If the address_notif_interval in last.cfg is set to a
    value such as 90, Internet Explorer is connected to the endpoint's
    page, and Internet Explorer is left unattended for 90 seconds, then
    an error message indicating referenced memory could not be read is
    displayed, and the endpoint must be restarted.

  Fixes from 3.7.1-TMF-0075:

    Internal CMVC Defect 134335
    Symptoms: With multiple, simulated endpoints on a UNIX
    platform, Inventory scans are able to add all the simulated
    endpoints to their database only for AIX machines.

    Internal CMVC Defect 135503
    Symptoms: The execution of a task on a NetWare 6 endpoint can cause
    NetWare to trap during task execution.  On a NetWare 5 endpoint,
    there is no trap, but the GUI or CLI that was used to execute
    the task will timeout.

    Internal CMVC Defect 139580
    Symptoms: When the parameters address_notif_interval and
    address_notif_retry_count are set for a NetWare or Windows 98
    endpoint, the lcfd executable can terminate abnormally.

    APAR IY17762
    Symptoms: The NetWare startup file LCF.NCF gets corrupted after
    running a "wadminep upgrade" command.

    APAR IY24392
    Symptoms: Distributing a File Package to a NetWare endpoint can
    sometimes cause an abend in the system log similar to "page fault
    processor exception error code 00000000 ...". The problem typically
    happens when many distributions are in progress.

    APAR IY25790
    Symptoms: When using Internet Explorer to access the TMA Daemon
    Status Page on an endpoint running version 94 on Windows NT and
    clicking the Refresh button on the browser twice in quick
    succession, lcfd will close its socket connection. Subsequent
    downcalls to the endpoint will fail until lcfd rebinds to its port,
    usually after the udp_interval has elapsed. 

    APAR IY28741
    Symptoms: The TIVOLI_ADMIN_PRIVILEGES group on Windows 2000 Domain
    Controller servers using Active directory in a BDC relationship to a
    Master of Operation Domain Controller is not getting the permissions
    assigned to it by the endpoint installer.  This can cause the
    execution of tasks to fail with an "access is denied" error message.

    Additional Information: The fix for IY28741 is contained in the
    libacct60.dll library, but the code in libacct60.dll that is
    affected by this fix is only invoked during the installation
    process.  This means that:

    * This fix is not available on Tivoli regions or managed nodes
      because the installation of a version 3.7.1 Tivoli region or
      managed node uses the Tivoli Management Framework, version 3.7.1
      CD-ROM which does not contain this fix.

    * This fix is not available on upgraded endpoints if an older
      libacct60.dll was used for the original installation of that
      endpoint.

    Hence, this fix is only available on new endpoint installations
    using either the InstallShield images from 3.7.1-LCF-0020 or the
    "winstlcf -N <proxy> ..." command, where <proxy> has a libacct60.dll
    with the IY28741 fix.
    
    NOTE: The libacct60.dll library is included in 3.7.1-TMF-0097 for
    consistency with 3.7.1-LCF-0020, even though the inclusion of
    libacct60.dll in 3.7.1-TMF-0097 does not provide a fix for IY28741
    on Tivoli regions or managed nodes.

    APAR IY29293
    Symptoms: For managed nodes and endpoints on Windows NT/2000/XP
    systems, if a task is created and launched using
    "BuiltinNTAdministrator" as the user on the managed node or
    endpoint, an error message about LookupAccountName failing is
    written to the lcfd log file.  No error message for managed nodes is
    written to the oservlog, however.

    Additional Information: The fix for IY29293 affects binaries on
    managed nodes and endpoints, so this fix is in both patch
    3.7.1-TMF-0097 and 3.7.1-LCF-0024.  As the text above indicates,
    though, this problem is not visible on managed nodes.

    APAR IY31720
    Symptoms: If during the lcfd service startup, no domain controller
    is available for the authentication of the TRAA account, lcfd fails
    to initialize TAP and the following error displayed in the lcfd.log
    file "Error 0: tap_call_init failed (rc = 2453)".  Subsequent
    operations on the endpoint then fail.  This needs to be changed so
    that lcfd retries the TAP initialization on these subsequent
    downcall requests. 

  Fixes from 3.7.1-TMF-0066:

    Internal CMVC Defect 140090
    Symptoms: The distribution process of an ITM 5.1 profile (via
    MDist2) on UNIX endpoints core dumps when endpoint patches
    3.7.1-TMF-0044, 3.7.1-TMF-0055E, 3.7.1-TMF-0060, and 3.7.1-TMF-0062E
    are installed. 

  Fixes from 3.7.1-TMF-0062E:

    Internal CMVC Defect 131667
    Symptoms: The Distributed Monitoring, version 4.1 engine that runs
    on PC endpoints has a memory leak during upcalls.  This memory leak
    also affects Tivoli Enterprise Console, version 3.8.

    Internal CMVC Defect 134502
    Symptoms: If a program (such as TELNET or netcat) connects to an
    endpoint's main socket and does not send any data, it can create a
    situation in which the Tivoli region is not able to communicate
    across the connection to the TMA.  The fix for this includes the
    addition of the following three new parameters to the lcfd program
    to control the queue that lcfd uses to manage incoming requests:

      1) recvDataTimeout: How many seconds to wait for data on an
      incoming connection before requeuing the connection (default = 2).

      2) recvDataNumAttempts: How many times to attempt to receive data
      on a connection before closing the connection (default = 10).

      3) recvDataQMaxNum: How many connections to hold in the pending
      connection queue at one time (default = 50).

    APAR IY16990
    Symptoms: A control character at the end of the lcf_env.sh and
    lcf_env.cmd files prevents them from terminating with a correct
    return code (0) even if successful.

    Additional Information: The fix for this APAR is included only in
    the InstallShield images provided in this patch for new endpoint
    installations.  This fix is not applicable to endpoints that are
    upgraded with the contents of this patch.

    APAR IY28146
    Symptoms: In an environment where the incorrect Windows 2000 context
    is set and a distribution with Tivoli User Administrator, version
    3.8 is done, the gateway eventually times out with a "communication
    reset by peer" message instead of displaying a popup error message.

    APAR IY28879
    Symptoms: When trying to do an installation with winstlcf for a 
    Windows NT endpoint using a proxy machine, there are errors on the
    CreateDirectory function if the share name does not contain a "$"
    (for example, "C$").

  Fixes from fix pack 3.7.1-TMF-0060:

    Internal CMVC defect 120559 / APAR IY28709
    Symptoms: When software distribution requires input from a user on a
    Windows XP target endpoint, the window on the endpoint is placed
    into the task bar, but the user cannot double-click the window or
    open the window.

    APAR IY15375.1
    Symptoms: The execute bit is turned on for $LCF_DATDIR/lcfd.log for
    "others". The execute bit should be turned off for everyone in this
    file.

    APAR IY20655
    Symptoms: An upgrade failure can occur on Windows NT/2000/XP systems
    if TivoliAP.dll has been disabled.  The upgrade fails while
    attempting to copy file permissions from the previous version of
    TivoliAP.dll.  This should be treated as a warning only, not as a
    fatal error, so the upgrade can continue.

    APAR IY23342
    Symptoms: The contents of the uninst.bat file (by default, found in
    "C:\Program Files\Tivoli\lcf") points to the directory
    "C:\WINNT\Profiles\...", which does not exist.  Because of this,
    running "uninst RemoveTAP" and rebooting does not remove
    TivoliAP.dll from the System32 directory and leaves DELTAP.bat in
    "C:\WINNT\Profiles\..." as well.

    Additional Information: The fix for this APAR is included only in
    the InstallShield images provided in this patch for new endpoint
    installations.  This fix is not applicable to endpoints that are
    upgraded with the contents of this patch.

    APAR IY25091
    Symptoms: The "wep <ep> set_config" and "wep <ep> set" commands can
    be used to set the "lcs.machine_unique_id=<28_char_value>" on an
    endpoint.  However, these commands only alter the value in the
    endpoint's lcfd cache or the endpoint manager.  Because the last.cfg
    file on the endpoint is not updated, the old ID value is read back
    into the cache and used when the endpoint is restarted.

    Additional Information: This fix is only applicable to AIX and PC
    (Windows, OS/2, and NetWare) endpoints.  The fixes for IY25091 are
    applicable to both Tivoli region Servers / managed nodes and
    endpoints.  Thus, both 3.7.1-TMF-0097 (for Tivoli region servers or
    managed nodes) and 3.7.1-LCF-0024 (for endpoints) must be installed
    for this fix.

    APAR IY27844
    Symptoms: Certain Tivoli Management Framework, Version 3.7.1
    endpoints do not run the login_policy when they do a normal login
    to their assigned gateway.

  Fixes from 3.6.5-TMF-0020 (not released):

    Internal CMVC defect 146616
    Symptoms: Correct a "Format illegal type error" message affecting
    Distributed Monitoring that is related to Windows 95 endpoints
    waking up from suspended mode.

    APAR IY20655
    Symptoms: A upgrade failure can occur on Windows NT/2000/XP systems
    if TivoliAP.dll has been disabled.  The upgrade fails while
    attempting to copy file permissions from the previous version of
    TivoliAP.dll.  This should not be treated as a fatal error, but only
    as a warning, so the upgrade can continue.

    APAR IY34897
    Symptoms: When pre-3.7B NetWare endpoints are upgraded to post-3.7B
    endpoints, the LCFD.NLM cannot be restarted because the LCF.NCF
    specifies old library names instead of the new library names.

    APAR IY40599, Internal CMVC defect 154481
    Symptoms: If the Framework gateway (not the TEC gateway) starts and
    stops very frequently, such as on a three minute cycle, a TEC
    adapter communicating with that gateway can terminate abnormally.

  Fixes from 3.6.5-TMF-0019 and 3.7.1-TMF-0041E:

    NOTE: The Tivoli Management Framework, Version 3.7.1 release
    contains binaries for endpoints at version 80 or later in the
    lcf_bundle.40 directory and binaries for earlier endpoint versions
    in the lcf_bundle directory.  This patch provides updates to both of
    those directories.  The updates in the lcf_bundle directory are the
    binaries that were released with patch 3.6.5-TMF-0019. Specifically,
    the fix for IY25410 in patch 3.6.5-TMF-0019 will be needed for
    Distributed Monitoring releases that are linked with 3.6.x
    libraries, and the fix for IY22626 in 3.6.5-TMF-0019 will be needed
    for upgrading 3.6.x versions of OS/2 endpoints.

    APAR IY25410, Internal CMVC defect 128312
    Symptoms: The lcfd process on an endpoint binds to its assigned
    port, and applications like Distributed Monitoring (DM) can reuse
    that same port.  This causes a problem for DM applications by
    allowing multiple processes on the same listening port, which
    results in multiple invocations of dm_ep_engine.

    APAR IY22626
    Symptoms: An attempt to upgrade an OS/2 endpoint using the command
    "wadminep <ep> upgrade", where the endpoint version number is 64 or
    less, results in a failure. Error SYS3175 is reported in lcfd.log.

  Fixes from 3.7.1-TMF-0055E:

    Internal CMVC defect 128312
    Symptoms: The lcfd process on an endpoint binds to its assigned
    port, and applications can reuse that same port.  This causes a
    problem for the applications by allowing multiple processes on the
    same listening port.

    Additional Information: Patch 3.7.1-TMF-0044 contained a fix for
    128312 that was applicable to Distributed Monitoring (DM).  The fix
    in this fix extends that earlier fix to applications other than
    DM.

    Internal CMVC defect 131553
    Symptoms: Enable customers to control access to the TMA
    information presented on the TMA's web pages by requiring the user
    to authenticate to the TMA using the HTTP userid and password for
    the TMA in the Tivoli region.

    Additional Information: Currently, the TMA controls access to this
    information through the use of the http_disable option.  The current
    options for http_disable are:

      0 - Default.  Anyone can see the web pages and, if they know the
          HTTP userid and password, can make changes to the options for
          the TMA and restart it. 
      1 - Anyone can see the web pages, but no changes can be made.
      2 - The web pages are not displayed at all.

    The fix for this defect adds another value:

      3 - User must authenticate to the TMA using the HTTP userid and
          password (as seen on the "wep <TMA-label>" command) before any
          of the web pages are presented, or else no pages are
          displayed.  This means that the browser function is available,
          but protected, using the userid and password.  If
          http_disable=3 is set, the user is allowed to change any
          configuration parameters (just like the http_disable=0
          setting) since the user is already authenticated.

    Internal CMVC defect 131696
    Symptoms: Initial logins and migration logins using TCP/IP should
    respect the udp_attempts and udp_interval settings to allow the
    endpoint to retry logins destined for a gateway.  Adding this
    capability brings the TCP/IP logins into functional alignment with
    the udp broadcast model and makes logins work consistently with the
    way they worked prior to the addition of TCP/IP login functionality.

    Internal CMVC defect 132265
    Symptoms: During initial login processing, the TMA cycles through
    its list of known gateways, contacting them in the order in which
    they were specified on the command line options.  However, the first
    gateway in the list is tried twice.

    APAR IY17830
    Symptoms: When browsing an endpoint directory, a filename with more
    than 24 characters is truncated.  This can happen when importing a
    Software Package into a Software Package Profile with the Import
    dialog and in the Location of Input File group box, selecting an
    endpoint and browsing. 

  Fixes from 3.7.1-TMF-0044:

    Internal CMVC defect 128718
    Symptoms: The updata directory on the endpoint should not be created
    when LCFD starts.  The updata directory is used to store upcall data
    files when allow_proxy_upcalls is TRUE and filefree_upcalls is
    FALSE.  The updata directory should only be created when it is
    needed, such as when allow_proxy_upcalls is TRUE, filefree_upcalls
    is FALSE, and an upcall is performed.

    Internal CMVC defect 129269
    Symptoms: Allow the command "wep <ep> set_config log_threshold=x" to
    dynamically change the logging level on the endpoint without having
    to restart the TMA.

    APAR IY03771
    Symptoms: Windows 95 endpoints report their hostnames as fully
    qualified names with the network name included.  The hostname should
    not include the network name.

    APAR IY19899
    Symptoms: If the Locale setting for the decimal point is not a full
    stop (the English number setting), the values entered for
    Event IDs are incorrectly converted.  This can happen on non-US
    machines.

    Additional Information: The fix in patch 3.7.1-TMF-0091 is for
    endpoints.  A similar fix for Tivoli region servers and managed
    nodes is in 3.7.1-TMF-0093.

    APAR IY23751
    Symptoms: The endpoint binaries in patch 3.7.1-TMF-0005 display
    unnecessary debug information on the NetWare console screen.

    APAR IY24353
    Symptoms: If the Version 3.7 dm_ep_engine is running on an endpoint
    and the lcfd process tries to start, lcfd does not successfully
    bind to a port and, therefore, does not start properly.  Also, the
    endpoint does not try to use the alternate port listed in the
    last.cfg file.

  Fixes from fix pack 3.7.1-TMF-0033:

    Internal CMVC defect 119088
    Symptoms: Add support for Chinese National Standard GB18030 since
    new products released to the China are required to support this code
    page.

    Additional Information: This fixes for 119088 in this patch are
    only applicable to endpoints.  Fixes for Tivoli region Servers and
    managed nodes are in 3.7.1-TMF-0093.

    APAR IY16042
    Symptoms: When a command like "wadminep view_version" or "wadminep
    view_cache_index" is executed on a UNIX endpoint, a file with
    endpoint status information like "cache_hits" is created in the
    "/tmp" directory, but never deleted.

    APAR IY19078
    Symptoms: When multiple tasks are run simultaneously on an endpoint,
    an error message similar to:

        run_task ** Exception caught in run_impl: remove
        (E:\Tivoli\lcf\Tiv16E.SH) failed errno=2

    can be generated.

    Additional Information: During the testing of IY19078, the reported
    problem with errno=2 was verified as fixed.  However, in some cases
    with a large number of tasks (500+), an errno=9 was observed both
    on systems which had this patch and systems which did not have this
    patch.  Internal defect 127582 has been created for this errno=9
    problem and will be addressed in a future patch or fix pack.

    APAR IY22155
    Symptoms: Windows 95/98 endpoints can hang the Windows shutdown when
    an endpoint cannot establish a connection with its gateway.  An "LCF
    not responding" message is displayed, which requires user
    intervention to continue the shutdown process.

    APAR IY25259
    Symptoms: Endpoint version 94 from patch 3.7.1-TMF-0021 does not use
    alternate gateways.  For an isolated endpoint login, the endpoint
    fails to cycle through the list of alternate gateways.

  Fixes from 3.7.1-TMF-0021:

    Internal CMVC defect 124050
    Symptoms: Add a routine to the mdist2 net_stream API that allows
    applications to set an error message that will be displayed by the
    Mobile GUI in the event of a failure.

    Additional Information: The fix for defect 124050 is in an endpoint
    library that is used by the Mobile subsystem and is a prerequisite
    of the Mobile portion of 3.7.1-TMF-0094.  The Mobile portion of
    3.7.1-TMF-0094 contains a fix for defect 124061, which corrects a
    problem with Mobile distributions.  Thus, both this patch and the
    Mobile portion of 3.7.1-TMF-0094 must be installed to have the fix
    for 124061.

    The fix for 124050 in this patch is also a prerequisite of the
    Software Distribution patch 4.1-COU-0024 (specifically, for APAR
    IY22708 in 4.1-COU-0024).  Thus, both this patch and patch
    4.1-COU-0024 must be installed to have the fix for IY22708.

    Internal CMVC defect 125453
    Symptoms: The fix for IY17872 in patch 3.7.1-TMF-0005 added changes
    to avoid a continuous loop when lcfd wakes up from a suspended
    state.  However, these changes can cause lcfd to be unresponsive for
    udp_interval seconds when an lcfd port is closed.

    APAR IY18726
    Symptoms: On an OS/2 Warp Server, an endpoint will install and run
    successfully.  However, once the config.sys file reaches a size of
    about 30K, it fails to start.  It appears as though the lcfd does
    not allocate enough space to read in the environment variables.

    APAR IY19684
    Symptoms: A Windows NT endpoint with two NIC cards fails its initial
    login to a gateway when using the
    "-D LOCAL_IP_INTERFACE=<SECOND NIC ADDRESS>" parameter.

    APAR IY20118 
    Symptoms: If you install an endpoint on Windows 98, the endpoint
    logs into the gateway correctly.  If you then log off the Windows 98
    session, the endpoint is disconnected and the lcfd.log (debug level
    3) contains the message "SystemEvent: Received WM_CLOSE event".  The
    customer must stop/start the lcfd locally after relogging to a
    Windows 98 session.

    APAR IY20800
    Symptoms: Bringing up an endpoint HTTP web access page using a
    string about 200 to 300 characters long following the port number
    specification can cause a buffer overflow.

    APAR IY20970
    Symptoms: The NetWare addadmin.nlm module allows a maximum of 61
    characters for the context name.  The fix for this APAR increases
    that limit to 256 characters.

    APAR IY21032
    Symptoms: After an OS/2 endpoint is installed and has logged into a
    gateway, the LCFD.ID file does not get created.  When the endpoint
    is rebooted, the LCFD.ID file is created, but it has a different ID
    then the ID in the endpoint manager database.

    APAR IY22926
    Symptoms: The lcfd executable can core dump after receiving an
    upcall_start command from Distributed Monitoring.  

    APAR IY24110
    Symptoms: A problem was introduced in patch 3.7.1-TMF-0005 in which
    endpoints with alternate gateways would not migrate to those
    alternate gateways when the primary gateway was down.

  Fixes from 3.7.1-TMF-0005:

    Internal CMVC defect 40354
    Symptoms: Add support for Secure Console, a NetWare feature that
    allows user to improve their network security.  Once activated,
    path specifiers are disabled, and new search paths cannot be
    created.  Thus, only the modules stored in a directory specified in
    a search path can be loaded, and to be loaded, the module must be
    named without its full path name.

    Internal CMVC defect 117297
    Symptoms: For the Tivoli Management Framework, Version 3.7 release,
    the emx*.dll files are not present in the directory
    lcf_bundle.40/bin/os2-ix86/tools.  This defect was fixed in Tivoli
    Management Framework, Version 3.7.1, but is provided in this patch
    Tivoli Management Framework, Version 3.7 installations.

    Internal CMVC defect 117565
    Symptoms: The lcf_bundle directory on Windows NT has a copy of the
    Tivoli Management Framework, Version 3.7 OS/2 tools, which are
    dependent on emx*.dll(s).  It should have the Tivoli Management
    Framework, Version 3.6.5 tools.

    Internal CMVC defect 118030
    Symptoms: If you use winstlcf to install an endpoint to a Windows NT
    machine that does not have the "tmersrvd" account defined and that
    does not have TivoliAP.dll in the %SystemRoot%\system32 directory,
    the installation will be incomplete.

    Internal CMVC defect 118116, APAR IY15755
    Symptoms: When a task is launched on an endpoint and the root_user
    idmap is set to BuiltinNTAdministrator, the task execution fails
    with a "user not found" error.

    Additional Information: The fix for 118116 in this patch is only
    applicable to endpoints.  A similar fix is made for Tivoli region
    servers and managed nodes in patch 3.7.1-TMF-0093.

    Internal CMVC defect 118758
    Symptoms: If the TRAA account specified for use by TAP is disabled,
    and the administrator issues "wadminep <ep> view_version" (for
    example), LCFD traps attempting to spawn the admin method.

    Internal CMVC defect 119217
    Symptoms: On endpoints, lcfd has memory leaks in certain situations
    when connecting to a gateway.

    Internal CMVC defect 119929
    Symptoms: Signaling the Service Control Manager that the service
    has stopped before completing all shutdown tasks causes an error
    dialog box to appear on Windows XP Beta 2.

    Internal CMVC defect 119930
    Symptoms: To run tasks and methods on endpoints in the more
    restrictive Windows 2000/XP environment, a spawned process must
    have read and execute permission for its script or binary.

    Internal CMVC defect 119932
    Symptoms: When using the WIN32_WHOAMI_EFFECTIVE parameter,
    win32_whoami queries the current process security descriptor owner
    to see if the current user is a member of the Administrators
    group. This is not a reliable indicator (especially on Windows XP),
    so you must determine group membership explicitly.

    Internal CMVC defect 119933, APAR IY14574
    Symptoms: Because the default security settings for Windows 2000/XP
    are more restrictive than Windows NT, you can longer require
    Everyone to have read/execute access to System32 or add tmersrvd to
    Power Users.

    Internal CMVC defect 120948, APAR IY17084
    Symptoms: If the keyword "do_compress=yes" is set when creating a
    filepackage block with the 3.6.2 Object Packager, the filepackage
    block is created, but it just consists of one line of text and not
    the expected file.

    Internal CMVC defect 122548
    Symptoms: Endpoint initial and isolated logins need to use TCP, not
    UDP.  The current endpoint code sends out a UDP packet for an
    endpoint's initial or isolated login attempts, but in firewall
    environments, most UDP operations are restricted.

    APAR IY08217 
    Symptoms: Endpoints cannot contact gateways through firewalls
    because they do not adhere to the port range restrictions like
    managed nodes do.

    Additional Information: The fix for IY08217 requires the
    installation of this patch, which is applicable to endpoints, and
    patch 3.7.1-TMF-0093, which is applicable to gateways.  Because
    patch 3.7.1-TMF-0093 is only for Tivoli Management Framework,
    Version 3.7.1, not Tivoli Management Framework, Version 3.7, then
    the fix for IY08217 is not available on Tivoli Management Framework,
    Version 3.7, even though this patch can be installed on Tivoli
    Management Framework, Version 3.7 systems.

    APAR IY14451
    Symptoms: The oserv cannot be started if the TMERSRVD domain account
    is disabled.  The fix for IY14451 affects TivoliAP.dll and is not
    applicable to endpoints.  However, it is included in this patch in
    case an endpoint is installed on a Tivoli region or managed node.

    Internal CMVC defect IY14630
    Symptoms: The "wep set interfaces" command cannot set the interface
    table with a gateway hostname for access through a NAT firewall.

    APAR IY16013
    Symptoms: When a "wadminep <ep_name> upgrade" command is issued for
    a Windows 95/98 endpoint, the endpoint automatically reboots.  A
    dialog box is needed on the endpoint that informs the user that a
    reboot will be happening.

    Additional Information: The fix for IY16013 affects binaries on the
    endpoint as well as the wadminep binary on the gateway.  Patches
    3.7-TMF-0028 and 3.7.1-TMF-0093 provide the wadminep binary for
    Tivoli Management Framework, Version 3.7 and Tivoli Management
    Framework, Version 3.7 1, respectively.  This patch provides
    endpoint binaries for both Tivoli Management Framework, Version 3.7
    and Tivoli Management Framework, Version 3.7.1.  Thus, for a Tivoli
    Management Framework, Version 3.7 environment, both patch
    3.7-TMF-0028 and this patch must be installed to have the fix for
    IY16013, and for a Tivoli Management Framework, Version 3.7.1
    environment, both 3.7.1-TMF-0093 and this patch must be installed to
    have the fix for IY16013.

    APAR IY16086
    Symptoms: Add the address_notif_retry_count lcfd parameter, which
    controls the number of retries that are made when the lcfd attempts
    to send its current IP address to the gateway (see
    address_notif_interval).  When the gateway cannot be contacted, the
    lcfd will wait the number of seconds specified by the udp_interval
    parameter and retry the connection to the gateway.  It will repeat
    this process of waiting and retrying until either the connection is
    made or the number of retries specified by this parameter are
    exhausted.  If the number of retries is exhausted, the lcfd will
    attempt to contact the next gateway in its list of gateways.

    APAR IY17872
    Symptoms: For endpoints, the lcfd executable on Windows 95 laptops
    goes into a continuous loop after the laptop wakes up from suspend
    mode.  System error 10050 may be reported.

    APAR IY18729
    Symptoms: On OS/2 Warp Server, patch 3.7.1-TMF-0001 installs
    endpoint version 92 correctly.  However, if no gateway is available,
    then after about 5 minutes, the endpoint times out and traps.  Thus,
    if a gateway goes down and no backup gateway exists, all endpoints
    have to be restarted after gateway is brought back up.

    Additional Information: The problem reported in IY18729 was caused
    by an incorrect fix in patch 3.7.1-TMF-0001.

    APAR IY19325
    Symptoms: During software distributions, an error similar to the
    following may appear in the software distribution log files:
    "Operation unsuccessful.  A checkpoint offset was not set for
    segment ID (SWDISEP_WIN95) version (1.0) because the segment was
    locked."

    Additional Information: The fix for IY19325 affects binaries on the
    endpoint as well as the gateway.  3.7.1-TMF-0093 provides the
    gateway binaries and this patch provides the endpoint binaries. For
    a Tivoli Management Framework, Version 3.7.1 environment, both
    3.7.1-TMF-0093 and this patch must be installed to have the fix for
    IY19325.

  Fixes from 3.7.1-TMF-0001:

    Internal CMVC defect 117780
    Symptoms: In Windows NT 4.0, running any task as the hidden user ID
    "System" kills the lsaa.exe security program.  This prevents any
    security actions, like logins, from occurring until the system is
    rebooted.

    Additional Information: The fix in this patch is for endpoints.
    3.7.1-TMF-0093 contains this fix for Tivoli regions and managed
    nodes.

    APAR IY14722
    Symptoms: The LCFD process on Windows NT leaks memory when it is
    trying to login to a gateway that is down, and it has no alternate
    gateways set in the last.cfg file.

    APAR IY16290
    Symptoms: The endpoint service (lcfd.exe) causes Windows 2000
    systems to reboot if the CrashOnAuditFail key is enabled.

Architecture(s):

    Solaris, AIX 4, HPUX 10, Windows 2000, OS/2, NetWare
    Linux-ix86, Linux-s390  (Endpoint Only)

    Note: This patch contains endpoint fixes for all the above platform
    types.  The first six platform types listed can also be gateways,
    and this patch can be installed on those gateways in order to
    upgrade endpoints of any of the above platform types with the fixes
    in this patch.

Patches superseded by this patch:

    3.7.1-TMF-0001
    3.7.1-TMF-0005
    3.7.1-TMF-0021
    3.7.1-TMF-0033
    3.7.1-TMF-0041E
    3.7.1-TMF-0044
    3.7.1-TMF-0055E
    3.7.1-TMF-0060
    3.7.1-TMF-0062E
    3.7.1-TMF-0066
    3.7.1-TMF-0075
    3.7.1-TMF-0080E
    3.7.1-TMF-0085
    3.7.1-TMF-0085A
    3.7.1-TMF-0086
    3.7.1-TMF-0090
    3.7.1-TMF-0091
    3.7.1-TMF-0095
    3.7.1-TMF-0099
    3.7.1-TMF-0102LA
    3.7.1-LCF-0013
    3.7.1-LCF-0014LA
    3.7.1-LCF-0015LA
    3.7.1-LCF-0016
    3.7.1-LCF-0017
    3.7.1-LCF-0018
    3.7.1-LCF-0019LA
    3.7.1-LCF-0020
    3.7.1-LCF-0021

    3.7.1-TMF-0009
    3.7.1-TMF-0037
    3.7.1-TMF-0068
    3.7.1-TMF-0071
    3.7.1-TMF-0076

Dependencies:

    TMF_3.7
    3.7-TMF-0016 is recommended if installed on a 3.7 system.

Database Changes and Special Considerations:

    1) As noted in the Problems Fixed section above, the Framework 3.7.1
    release contains binaries for endpoints at version 80 or later in
    the lcf_bundle.40 directory and binaries for earlier endpoint
    versions in the lcf_bundle directory.  This patch provides updates
    to both of those directories.  The updates in the lcf_bundle
    directory are the binaries that were released with patch
    3.6.5-TMF-0019 plus one fix from the unreleased 3.6.5-TMF-0020.

    2) In some situations, additional configuration steps may be needed
    to enable applications whose targets include NetWare endpoints.  For
    example, for an installation that resides on SYS:\tivoli\lcf, the
    command:

        load waddpath SYS:\tivoli\lcf\dat\1\cache\lib\NW4

    may need to be executed to specify the directory path to be used
    during the distribution.  After executing the above command, the
    NetWare endpoint should be stopped and restarted prior to performing
    the distribution.

    3) The NetWare Secure Console fix provided in defect 40354 enables
    Tivoli endpoints to run in Secure Console mode on NetWare servers.
    Secure Console is a NetWare operating system feature that allows
    users to improve their network security by preventing the execution
    of modules that are not stored in a secure path. Once Secure Console
    is activated, path specifiers are disabled and new paths cannot be
    added to search paths. In other words, the modules stored in a
    directory specified in the search path can be loaded, but must be
    named without specifying their full qualified pathname before being
    loaded.  To enable endpoints to work in a secured environment, all
    paths used to run methods must be defined as search paths. The
    system administrator must also perform the actions described below
    before Secure Console can be activated.

    Patch 3.7.1-LCF-0024 provides updated endpoint modules, and the
    waddpath and wupdncf commands.  After this patch has been installed,
    the wupdncf command must be run to modify the SYS:SYSTEM\LCF.NCF
    startup script. The wupdncf command also performs the following
    tasks:

      - Removes the full path specification for the LCFUTILS and LCFD
        commands.

      - Adds a command to update the search path at the beginning of the
        endpoint startup script that will add the paths SYS:TEMP and
        $BINDIR to the search path.

      - Creates the SECCON file in the %BINDIR directory, which is used
        to control usage of Secure Console mode or standard mode.

    NOTE: The endpoint starts in secured mode if the SECCON file is
    present. If the endpoint does not find the SECCON file, it
    automatically starts in standard mode.

    The LCF.NCF file must be executed before Secure Console is
    activated. Otherwise, the SEARCH ADD command will fail. The startup
    sequence of the server should be rearranged so that the LCF.NCF file
    is listed before the SECURE CONSOLE command.

    The waddpath command adds the paths needed to run other Tivoli
    applications that are designed to support Secure Console mode of
    operation. The waddpath command accepts a fully qualified pathname
    as a parameter and adds it to the search path. For example,

      load waddpath <path>

    adds the following line at the top of the LCF.NCF file:

      search add <path>

    The server must be powered off to activate the new search paths when
    Secure Console is active.

    NOTE: Search paths cannot be added if Secure Console is on. You must
    power off to remove Secure Console.

    4) Endpoint Upcall Firewall Enablement is provided in the fix for
    APAR IY08217.  See the Readme file for patch 3.7.1-TMF-0008 for a
    description of this fix.

    5) For 4.1 environments, the 4.1 endpoint patches 4.1-LCF-0022 and
    later do not provide updates to the lcf_bundle or lcf_bundle.40
    directory in order to simplify the installation of these 4.1
    endpoint patches in 3.7.1 environments which contain 4.1 endpoints.
    Thus, if newer lcf_bundle and lcf_bundle.40 directories are needed
    for backward compatibility in a 4.1 environment, then this 3.7.1
    patch can be installed in a 4.1 environment to provide those two
    directories. 

    The following is a summary of the directory names used on a gateway
    for the endpoint binaries in different Framework releases:

      36x binaries (endpoint version < 80) are in lcf_bundle
      37x binaries (endpoint version 80 - 40999 )are in lcf_bundle.40
      41x binaries (endpoint version >= 41000) are in lcf_bundle.41000

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

    See the image report for this patch in the file 371LCF24/image.rpt
    for a complete list of the files replaced by this patch.

Patch Contents:

    - This README file
    - The cdrom image for this patch
    - The image report for this patch
    - The endpoint installation images for NetWare 4, OS/2, Windows.
      These installation images are in the directory 371LCF24/PC/LCF
      that is created when the patch is extracted from the tar file.

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.7.1-LCF-0024.tar

        On a Windows 2000 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.7.1-LCF-0024.tar

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

    2)  If this patch is to be installed on a release level of Tivoli
        Management Framework, Version 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, click 
            Desktop --> Install --> Software Installation Service.
        b)  SIS initializes and brings 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 fix pack 3.7.1-LCF-0024 using the file
            browser, and double-click the PATCHES.LST file.
        g)  Select fix pack 3.7.1-LCF-0024 in the Import Product
            dialog, and click the Import button.
        h)  When the import is complete, click OK on the Global Progress
            Dialog.
        i)  Select fix pack 3.7.1-LCF-0024 in the Select Product
            dialog, if it is not already selected, and click OK.
        j)  Click the Select Machine button on the Install Spreadsheet
            dialog.
        k)  Select the machines you would like to install fix pack
            3.7.1-LCF-0024 on and click OK.
        l)  Click the appropriate cells in the Install Spreadsheet
            dialog. 
            NOTE: This should yield an "X" in the cells for the machines
            on which you want to install fix pack 3.7.1-LCF-0024.
        m)  Click Install.
        n)  Select the install algorithm you want to use on the
            Installation Algorithm dialog, and click OK.
        o)  SIS will perform the installations you designated
            in the Install Spreadsheet dialog.
        p)  Installation is complete. Check the Additional 
            Installation Instructions section below.

    3)  Perform the following steps to install the patch using the
        Tivoli GUI 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.
            Click the patch. 
        f)  Select the clients to install this patch on. This patch
            needs to be installed on gateway machines.
        g)  Press Install to install the patch.

Additional Installation Instructions:

    This patch upgrades the endpoints from earlier versions to version
    37124.  To upgrade your endpoints, perform the following steps: 

    1) Make sure that the endpoint has logged into the Tivoli region.

    2) Verify that the endpoint has logged in by using the "wep ls"
       command.

    3) Before the upgrade, enter the following command:
  
        wadminep <ep_name> view_version

       The version number returned should be a value less than 37124,
       depending on which other patches affecting endpoint code have 
       been applied.

    4) From the Tivoli region server or the gateway that the endpoint is
       logged into, enter the following command:

        wadminep <ep_name> upgrade

       NOTE: The upgrade will use binaries from the machine on which the
       upgrade command is executed.  So, for example, if the upgrade
       command is executed on a Tivoli region server and the endpoint's
       gateway is a different machine, then the binaries on the Tivoli
       region server (not the endpoint's gateway) will be used for the
       upgrade.

    5) After the upgrade, enter the following command: 
 
        wadminep <ep_name> view_version

       It should return a 37124.

    ------------------------------------------------------------------

    The 3.7.1 gateway uses a bundles_map that identifies ranges of
    endpoint version numbers to distinguish 3.6.x, 3.7.x, and 4.1.x
    endpoints. The installation of this patch updates that bundles_map
    so that the five digit endpoint version number in this patch and in
    4.1.x endpoint patches are handled correctly.  For this updated
    bundles_map to be used by the gateway, however, the gateway must be
    restarted.  Thus, after applying this patch, use the wgateway
    command to restart each gateway where this patch was installed.

    ------------------------------------------------------------------

    This patch contains the Windows 2000 library TivoliAP.dll.  Since
    TivoliAP.dll may already be in use by Windows 2000, the Windows 2000
    system must be rebooted after an upgrade (or a new installation
    where an older version of TivoliAP.dll was in use) so that this new
    version of TivoliAP.dll will be loaded.  If you do not reboot, then
    Windows 2000 will continue to use the older TivoliAP.dll that was
    previously loaded.

    The TivoliAP.dll being replaced is used by the Windows 2000 security
    service.  Due to this library being locked, we must follow the
    Microsoft solution for handling locked libraries.  This solution
    dictates that we must reboot the Windows 2000 system to allow the
    locked library to be replaced at boot time.

    NOTE: The version of TivoliAP.dll supplied in this patch is the same
    as the version supplied in endpoint patches:

       3.7.1-LCF-0016    (endpoint version 37116)
       3.7.1-LCF-0017    (endpoint version 37117)
       3.7.1-LCF-0018    (endpoint version 37118)
       3.7.1-LCF-0020    (endpoint version 37120)
       3.7.1-LCF-0021    (endpoint version 37121)

    except for timestamp information, but is different from all earlier
    endpoint versions.  Thus, if you are upgrading from one of the
    endpoint versions listed above to version 37124 in this patch, then
    it's not necessary to reboot the Windows 2000 endpoints. For older
    endpoint versions, however, there is no problem in continuing to run
    with a previous version of TivoliAP.dll on Windows 2000 except that
    certain fixes will not be available. Thus, this endpoint reboot does
    not have to be done when an endpoint is upgraded and can be deferred
    until a later time. 

    ------------------------------------------------------------------

    NOTE: The Linux endpoints do not support the following monitors:

      * Client RPC timeouts
      * NFS bad calls
      * RPC bad calls
      * Jobs in print queues
      * Total size queued
      * Page -scans

    Installation of an endpoint using the winstlcf command with its
    default options may fail or hang. This problem affects Red Hat 6.2
    (and higher). The default winstlcf endpoint installation uses the
    Linux rexecd daemon on both the source and the target for
    communication. On the Linux operating systems mentioned above, the
    rexecd daemon contains a defect which prevents Tivoli endpoints from
    installing. Because of security policy in Red Hat 6.2 (and higher),
    root access via the rexecd has been disabled, which prevents Tivoli
    endpoints from installing. 

    Workaround: Install the endpoint using the winstlcf command with the
    -e Trusted Host option as follows:

    Follow operating system instructions to configure the target's
    .rhosts file to allow trusted host root access for the gateway from
    which the installation is being performed. If configured properly,
    the following command executed from the gateway should return
    "hello": 

       rsh target_machine_name -l root echo hello

    If "Permission Denied" is returned, consult operating system
    documentation on how to correctly configure trusted host access and
    repeat the above test.

    From the gateway in which you successfully ran the test above,
    install the target endpoint using the Trusted Host access method as
    follows:

      winstlcf -e target_machine_name

    Contact the appropriate vendor to obtain the following service patch
    which corrects rexec:

    Red Hat 7.0: Patch "glibc-2.2-12" as described in Red Hat Service
    Advisory "RHSA-2001:001"

    Turbolinux: Contact vendor to obtain a rexec fix or use the
    workaround.

    Follow operating system instructions to properly enable rexec to
    allow root access to the target since, due to security
    considerations, many operating system vendors disable rexec by
    default. Tivoli strongly recommends that once the Tivoli
    installation is complete, rexec access to the target be disabled or
    restored to a configuration recommended by the operating system
    vendor.

Known Defects:

    None.
