***********************************************************
***********************************************************
**                                                       **
**  NOTICE:  This Patch has been superseded by patch     **
**  3.6.1-TMF-0078                                       **
**                                                       **
**  Please use it instead unless otherwise directed.     **
**                                                       **
***********************************************************
***********************************************************


Date:   February 14, 2000

Patch:  3.6.1-TMF-0066

Component:  Tivoli Framework 3.6.1

General Description:

    This patch fixes several problems: (1) the maximum dispatcher number
    is increased to allow for values larger than 64K, (2) an earlier
    change affecting the security_group_Library security group and User
    Administration is backed out, (3) a problem with wrpt is fixed, and
    (4) a problem in patch 3.6.1-TMF-0050 is corrected.  This patch
    supersedes patches 3.6.1-TMF-0050 and 3.6.1-TMF-0058 and requires
    that patches 3.6.1-TMF-0004, 3.6.1-TMF-0035, and 3.6.1-TMF-0051 be
    installed prior to the installation of this patch.

Problems Fixed:

  New fixes in 3.6.1-TMF-0066:

    Internal CMVC defect 48749
    Symptoms: In large installations with many managed nodes and
    endpoints, the dispatcher number may exceed the maximum value of
    64K.  The fix for this defect increases the maximum dispatcher
    number to allow values larger than 64K.

    Internal CMVC defect 84037
    Symptoms: User Administration fine grained roles do not work as
    expected.

    Additional Information: In patch 3.6.1-TMF-0008 (superseded by
    3.6.1-TMF-0051), the security_group_Library:user was added to
    all Administrators capabilities.  This change incorrectly allows
    Administrators without any roles to view information that was
    previously only viewable by Administrators that had certain roles.
    This patch, therefore, contains the following fixes: 1) When an
    Administrator is created, the Administrator will no longer have the
    security_group_Library:user role, and 2) Certain objects in the
    database will be modified to remove the security_group_Library
    security group.

    APAR IY03003
    Symptoms: The wrpt command fails on AIX with the message "A failure
    was detected by oserv daemon: general failure ...".

    APAR IX85877
    Symptoms: Endpoints on DHCP machines are unreachable after their
    IP address changes.  (This patch affects the gateway only.  Patches
    3.6.1-TMF-0025 or 3.6.1-TMF-0052 must be installed and DHCP
    endpoints upgraded to 3.6.1-TMF-0025 or 3.6.1-TMF-0052 before this
    fix is available on those endpoints.)

    Additional Information: The fix for the endpoint portion of IX85877
    was made in patch 3.6.1-TMF-0025, which was later superseded by
    3.6.1-TMF-0052, and is correct.  However, the fix for the gateway
    portion of IX85877 made via defect 75296 in 3.6.1-TMF-0050, which
    was later superseded by 3.6.1-TMF-0058, is not correct.  The fix in
    3.6.1-TMF-0050 doesn't cause any regressions -- it just doesn't fix
    the problem.  Thus, this patch contains a corrected fix for the
    gateway portion of IX85877.

  Fixes from 3.6.1-TMF-0058

    APAR IX85081
    Symptoms: While scanning PC Managed Nodes or doing software
    distributions, a 'method' failed with error 2816 is received on
    some nodes while others will complete without error.  The fix for
    this APAR involved changing the underlying communication mechanism
    of the oserv on Solaris from TLI to sockets.  See the Database
    Changes and Special Considerations section below for additional
    information regarding actions to be taken after installing this
    patch.
    
    APAR IY03364
    Symptoms: Memory leak shown in tec_reception using ps -elf.

    Internal CMVC Defect 62157
    Symptoms: Executing the "wrpt -t" command can cause OS/2 gateways to
    crash.
    
  Fixes from 3.6.1-TMF-0050
    
    Internal CMVC Defect 75296
    Symptoms: When a 3.6.1 endpoint on a a computer running Windows 95
    is distributed a filepack with the "reboot after receive" option
    set, the computer hangs at the splash screen during shutdown.  This 
    patch affects the gateway only.

    Additional Information: As mentioned above, the fix for the gateway
    portion of IX85877 made in 3.6.1-TMF-0050 via defect 75296 is not
    correct.  The fix in 3.6.1-TMF-0050 doesn't cause any regressions --
    it just doesn't fix the problem. 
 
Architecture(s):

    Solaris, AIX 4, HPUX 10, SunOS 4, Windows NT 3.5.1 and 4.0

Patches superseded by this patch:

    3.6.1-TMF-0050
    3.6.1-TMF-0058

Dependencies:

    TMF_3.6.1
    3.6.1-TMF-0004
    3.6.1-TMF-0035
    3.6.1-TMF-0051

Database Changes and Special Considerations:

    Please read this Readme in its entirety before applying this patch.
    After this patch is applied, gateways on Solaris2 interps will no
    longer work until any managed nodes that gateways are running on
    have either been (1) shut down and then restarted, or (2)
    re-executed, as described in the following paragraphs.

    Note: Once you have restarted your TMR server and all managed nodes,
    a new patch ID, TMF_3.6.1A, is created. This patch ID is not
    displayed in the patch list on the GUI, but you can view it in the
    output of the wlsinst command. If you are using SIS, you must
    re-synchronize your database to pick up the new patch ID. 

    Solaris Systems Sharing Files with NFS

    The patch installation procedure for Solaris systems that share
    files with NFS has changed for this patch because of the change from
    TLI to socket communication contained in this patch.  In particular,
    an oserv boot script runs as the final step of the patch upgrade
    process.  If your Solaris systems share both binary and library
    directories over NFS, some of those systems could hang if the
    systems are not restarted in the manner documented below.

    Note: This patch should **NOT** be installed on Solaris systems
    where: (1) the binary directory is shared over NFS, but the library
    directory is not, or (2) the library directory is shared over NFS,
    but the binary directory is not.  It should only be installed on
    systems where either both the both binary and library directories
    are shared over NFS or neither of these two directories are shared.
    Furthermore, if a group of Solaris systems share a common binary
    directory, then they must also share the same common library
    directory.  For example, if the Solaris machines in group A share a
    binary directory and the Solaris machines in group B share a
    different binary directory, then a machine in group A can't share a
    library directory used by group B, and a machine in group B can't
    share a library directory used by group A.

    If your TMR contains Solaris systems that use NFS to share both the
    binary and library directories use the following procedure.
    Otherwise, proceed to the "Other Systems" heading below.

    To shut down and then restart your systems, follow these steps:

    1. From the TMR server, run the following command to shut down all
       managed nodes: 

       odadmin shutdown clients

    2. Run the following command to restart the TMR server:

       odadmin reexec 1

    3. Run the following command to restart all managed nodes:

       odadmin start clients

    Note: Gateways on Solaris 2.x systems will not operate until the
    managed node on which the gateway is running is restarted.  The
    shutdown and restart is required for the upgrade only.  After you
    have restarted the managed nodes following the upgrade, you can use
    the odadmin reexec command to restart these systems in the future.

    Other Systems

    If your TMR does not contain Solaris systems that use NFS to share
    both the binary or library directories, you can restart your oserv
    processes using the shutdown method listed in "Solaris Systems
    Sharing Files with NFS" above, or re-execute them using the
    following method.

    To re-execute the oserv process on the managed nodes in your TMR,
    issue the following commands from the TMR server:

      odadmin reexec 1
      odadmin reexec clients

Files Replaced by this Patch (for all supported values of INTERP):
    
    $BINDIR/bin/dbIX79633
    $BINDIR/bin/wcrtpol
    $BINDIR/TMF/BASESVCS/Library_prog1
    $BINDIR/TAS/Administrator/AdminCol_prog1

    $BINDIR/bin/oserv
    $BINDIR/TMF/LCF/gateway
    $LIBDIR/libwo.SL
    $LIBDIR/libtmf.SL

    $BINDIR/bin/odadmin
    $MSGCAT/C/admin_msgs.cat

Files Replaced or Added by this Patch (for solaris2 $INTERP only): 
    
    $BINDIR/bin/oserv_361TMF58_before.sh
    $LIBDIR/libtmf.361TMF58.SL
    $LIBDIR/libwo.361TMF58.SL

Patch Contents:

    This README file
    The cdrom image for this patch
    The image report for this patch

Applying the Patch:    

    1)  Extract the patch:

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

        # cd $PATCH
        # tar xvf 3.6.1-TMF-0066.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.1-TMF-0066.tar

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

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

        NOTE: SIS can install Tivoli products on any hardware
              platform supported by Tivoli, but there are some
              hardware platforms on which SIS cannot be run. Please
              check your SIS User's Manual for the list of platforms
              on which SIS can be run.

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

        a)  From the Tivoli Desktop, pull down 
            Desktop --> Install --> Software Installation Service.
        b)  SIS will initialize, and bring up the Get Installation
            Password Dialog.  Enter your Installation Password.
        c)  Click the Install Button on the dialog which contains
            the Tivoli image.
        d)  Click the Select Product Button on the Install Spreadsheet
            Dialog.
        e)  Click the Import Product Button on the Select Product
            Dialog.
        f)  Locate the media to 3.6.1-TMF-0066 using the file browser,
            and select the PATCHES.LST file by double-clicking it.
        g)  Select 3.6.1-TMF-0066 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.1-TMF-0066 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.1-TMF-0066 on 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.1-TMF-0066 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
            needs to be installed on the TME server and on each 
            managed node client.
        g)  Press the "Install" button to install the patch.

Additional Installation Instructions:

    After applying this patch, perform an "odadmin reexec all"
    to refresh the oservs on the TMR server and gateways. 

Known Defects:

    None.
