Date:   December 17, 2003

Patch:  4.1-TMF-0030

Component:  Tivoli Framework 4.1

General Description:

    4.1-TMF-0030 corrects problems affecting Mobile, JCF, JRIM, the
    MDist2 GUI, and the Tivoli Desktop for Windows. This patch supercedes
    4.1-TMF-0021 and 4.1-TMF-0023. No other patches need to be installed
    prior to the installation of 4.1-TMF-0030. It's recommended, but not
    required, that 4.1-TMF-0034 and 4.1-LCF-0022 be installed in
    conjunction with 4.1-TMF-0030 for additional fixes.

Problems Fixed:

  New fixes in 4.1-TMF-0030:

    Internal CMVC defect 154944
    Symptoms: Add an additional connect() method to RIM_session that
    allows IOM to use an existing Orb.

    Additional Information: The fix for this defect requires that the
    JRIM images in the JAVA/JRIM41 subdirectory be installed. See the
    Database Changes and Special Considerations section below for more
    information about 154944.

    APAR IY31420
    Symptoms: The TEC console cannot be opened for a TEC managed node
    that has: (1) two or more NIC cards, or (2) the IP address of the
    machine was changed and the wlocalhost file is used to bring up the
    oserv.

    Additional Information: The fix for this APAR requires that the JCF
    images in the JAVA/JCF41 subdirectory be installed.

    APAR IY34400
    Symptoms: If the Mdist2 GUI is started from the Tivoli GUI by double
    clicking on the "Distribution Status" icon, and it does not have
    authority to access the X server, then the attempt to start the
    Mdist2 GUI fails silently.  That is, it appears as if the double
    click was ignored.

    Additional Information: The fix for this APAR requires that the
    images in the 41TMF030 directory be installed.

    APAR IY36313
    Symptoms: Under certain circumstances, the MDist2 GUI cannot be
    launched from the desktop. The following error is generated:
    "FRWSL0024E A failure was detected by the oserv daemon: FRWOG0010E
    requested resource not found". The CLI command, however, works
    without error.

    Additional Information: The fix for this APAR requires that the
    images in the 41TMF030 directory be installed.

    APAR IY38298
    Symptoms: APM commands, such as wmonpln, can sometimes hang when
    there is a large amount of stdout output. This was also fixed in
    3.7-TMF-0048 and is included here for APM 4.2.

    Additional Information: The fix for this APAR requires that the JCF
    images in the JAVA/JCF41 subdirectory be installed.

    APAR IY38642
    Symptoms: In the 3.7.1 release, the MDist2 GUI could be launched by
    an administrator who had either RIM_View or Senior roles. The GA
    release of Framework 4.1 introduced an undocumented change so that
    the Senior role is now required to launch the MDist2 GUI.

    Additional Information: The fix for this APAR requires that the
    images in the 41TMF030 directory be installed.

    APAR IY41224
    Symptoms: When single_port_bdt and iom_by_name are set to true, and
    an attempt is made to open a connection to the SPBDT service over
    NAT, the IP address is still used as the destination address instead
    of the hostname.  This results in a failed connection attempt since
    this IP address is not reachable.

    Additional Information: The fix for this APAR requires that the JCF
    images in the JAVA/JCF41 subdirectory be installed.

    APAR IY44586
    Symptoms: A java exception is reported in an Mdist2 GUI console
    pop-up when checking the progress of an Inventory scan.

    Additional Information: The fix for this APAR requires that the
    images in the 41TMF030/41MD201 subdirectory be installed.

    APAR IY46447, APAR IY51944
    Symptoms: If the SPBDT host has a name that starts with the letter
    "I", then the parsing logic in the Key constructor fails, which
    results in MDist2 distribution failures in iom open. 

    Additional Information: The fix for this APAR requires that the JCF
    images in the JAVA/JCF41 subdirectory be installed.

  Fixes from 4.1-TMF-0023:

    APAR IY22161
    Symptoms: When the Tivoli Desktop is launched from a Windows 95 / 98
    workstation and a large notice is opened, an empty window is
    displayed.  The fix for this APAR increases the limit for the size
    of a notice to 64K bytes for Windows 95 / 98 and 2.14G bytes for
    Windows NT / 2000 / XP.  Note: A notice will have header information
    that is about 3K bytes, so the largest size of the notice text is
    approximately 61K bytes on 95 / 98.

    Additional Information: The Tivoli Desktop for Windows contains
    multi-line edit controls whose text limit is restricted by the upper
    limit imposed by each version of Windows for a multi-line edit
    control.  Microsoft documentation specifies that the upper limit is
    64K for Windows 95 / 98 and 2.14G for Windows NT / 2000 / XP.  The
    fix for this APAR requires that the DSWIN images in the DESKTOP
    subdirectory be installed.

    APAR IY26117
    Symptoms: DSWIN hangs intermittently when displaying the splash
    screen on Windows 2000 and XP.

    Additional Information: The fix this APAR requires that the DSWIN
    images in the DESKTOP subdirectory be installed.

    APAR IY27214
    Symptoms: The Tivoli Desktop does not remove the ADL (Active Desktop
    List) object from the database when exiting via 'X' button on the
    upper right-hand corner of the main dialog.  The effect of this is
    that the ADL object stores obsolete desktop, which must be manually
    removed.

    Additional Information: The fix this APAR requires that the DSWIN
    images in the DESKTOP subdirectory be installed.

    APAR IY31135
    Symptoms: Dswin does not handle disabling submenus properly.  When
    using the Logfile Format Editor, the message "A failure was detected
    by the oserv daemon: general failure" is displayed if the "Open
    Logfile" option is used before the "Open Format" option.

    Additional Information: The fix for this APAR requires that the
    DSWIN images in the DESKTOP subdirectory be installed.

    APAR IY31490
    Symptoms: When a pop-up window that has columnized data (like the
    Tivoli Desktop/About/Installed Products/Patches) is up, the data in
    the window ("Patch Information", in this case) may extend past the
    end of the visible field. However, there is no slider bar that
    enables the user to read all the text.

    Additional Information: The fix in this patch is for the Tivoli
    Desktop for Windows and requires that the DSWIN images in the
    DESKTOP subdirectory be installed.  A separate fix for X Windows
    will be provided in a future patch.

    APAR IY32410
    Symptoms: DSWIN uses 100% of the CPU and takes a long time to open a
    GUI in the Japanese environment for the Distributed Monitoring (DM)
    Edit Monitor.

    Additional Information: The fix for this APAR requires that the
    DSWIN images in the DESKTOP subdirectory be installed.

    APAR IY34049
    Symptoms: When a task that uses TLL to present a dialog with input
    'command' and 'target' arguments is run repeatedly, then eventually a
    failure can result in the output display on the desktop. This failure
    occurs about once in every 25-35 executions of the task.

    Additional Information: The fix in this patch is for the Tivoli
    Desktop for Windows and requires that the DSWIN images in the
    DESKTOP subdirectory be installed.  For Unix platforms, the fix
    for IY34049 will be provided in a future patch. 

    APAR IY34677
    Symptoms: After opening a UserProfile in the Tivoli Desktop for
    Windows and selecting "Find" from the pulldown menu under "View" on
    the User Profile Properties screen, the table may not scroll to the
    user specified in the Find dialog.

    Additional Information: The fix for IY34677 requires that the DSWIN
    images in the DESKTOP subdirectory be installed.

    APAR IY37528
    Symptoms: When using the Spanish version of Dswin, the class fields
    (Job Class, Hold Class, Message Class and SYSOUT Class) in the TSO
    Segment of the RACF Catagory do not appear to accept any
    values. (Actually, Dswin does allow values to be entered in those
    fields, but the field size is too small, so the value cannot be seen
    on NT and is only partially visible on Windows 2000.)

    Additional Information: The fix for IY34677 requires that the DSWIN
    images in the DESKTOP subdirectory be installed.

  Fixes from 4.1-TMF-0021:

    Internal CMVC defect 152456
    Symptoms: Add a way to remove the "don't display this..." checkbox
    from the Mobile new distribution popup dialog and have the dialog
    better identify the product.  If allowGeneral is set to false, this
    checkbox will not be displayed and if set to true, the checkbox will
    be displayed.  (The default value of allowGeneral is true.)  A
    graphic identifying the popup as a Tivoli product has also been
    added and the title of the dialog has been modified.

    Additional Information: The fix for this APAR requires that the
    Mobile images in the MOBILE subdirectory be installed.  It is
    also recommended that endpoint patch 4.1-LCF-0022 be installed on
    the endpoint where Mobile is running.

    APAR IY28234
    Symptoms: Launching Mobile from the system tray (Taskbar) and from
    the desktop produce inconsistent results. The connection setup
    dialog box should be displayed in both situations.

    Additional Information: The fix for this APAR requires the
    libmobile60.dll that is installed by 4.1-LCF-0022. It also requires
    that the Mobile images in the MOBILE subdirectory be installed.

    APAR IY34156
    Symptoms: There is no way to tell if a particular machine has the
    original 3.7.1 GA version of Mobile or a newer patched version,
    which makes it hard to determine whether the new version needs to be
    installed. The fix for this APAR adds a version number (including a
    build number) to the "About" dialog.

    Additional Information: The fix for this APAR requires that the
    Mobile images in the MOBILE subdirectory be installed.  It is
    also recommended that endpoint patch 4.1-LCF-0022 be installed on
    the endpoint where Mobile is running.

    APAR IY34319
    Symptoms: The mobile.cfg file is not accessible by all users. If a
    non-Administrator uses the mobile client, the mobile icon does not
    change to the yellow background with an exclamation point. Double
    clicking on the mobile client will start the client and the package
    will install. When the install completes an error message similar to
    "Mobile needs to be reset. Please reboot the computer" is displayed.

    Additional Information: The fix for this APAR requires that the
    Mobile images in the MOBILE subdirectory be installed.  It is
    also recommended that endpoint patch 4.1-LCF-0022 be installed on
    the endpoint where Mobile is running.

    APAR IY35150
    Symptoms: There is a misleading statement in the Mobile Help which
    may cause customers to believe that the Mobile GUI is continually
    polling the gateway.  Although the GUI doesn't poll the gateway, the
    Mobile agent does make upcalls at intervals set by the user.  The
    Mobile agent does this on startup until the first successful upcall.
    This fix for this APAR changes the behavior of the Mobile agent so
    that a single upcall is made on startup. The interval will still be
    used, however, for checking if disconnected results are available to
    be returned to the gateway. 

    Additional Information: The fix for this APAR requires both the
    Mobile binaries provided in this patch in the MOBILE subdirectory
    and the gateway / rpt2 binaries provided in 4.1-TMF-0019.  Thus,
    both patches must be installed to have the fix for this APAR.

    APAR IY43672
    Symptoms: Software distributions with Expiration dates that are
    distributed to Mobile clients running the Tivoli Mobile Console can
    indefinitely hang when attempting to execute a "PERFORM OPERATION"
    on distributions that have already expired.

    Additional Information: The fix for this APAR requires that the
    Mobile images in the MOBILE subdirectory be installed.  It is
    also recommended that endpoint patch 4.1-LCF-0022 be installed on
    the endpoint where Mobile is running.

    APAR IY46343
    Symptoms: The Mobile client reads the history file at startup and
    writes the file once at shutdown.  However, if the Mobile client
    does not shutdown normally, the history accumulated will not be
    written to the history file.

    Additional Information: The fix for this APAR requires that the
    Mobile images in the MOBILE subdirectory be installed.  It is
    also recommended that endpoint patch 4.1-LCF-0022 be installed on
    the endpoint where Mobile is running.

Architecture(s):

    Solaris, AIX, HPUX, Windows NT / 2000, OS/2

Patches superseded by this patch:

    4.1-TMF-0021
    4.1-TMF-0023

Dependencies:

    TMF_4.1

Database Changes and Special Considerations:

    1) This version of the Tivoli Desktop for Windows (DSWIN) in this
    patch should be installed by running the setup command found in the
    41TMF030/DESKTOP subdirectory for your particular operating system.
    This patch contains the same version of DSWIN that was shipped in
    4.1-TMF-0023.

    2) The version of Mobile in this patch should be installed by
    running the setup.exe command found in the 41TMF021/MOBILE
    subdirectory for your particular operating system. These setup.exe
    files can be used to upgrade Mobile, or they can be used for a fresh
    install on a Windows NT / 95 system where Mobile was not previously
    installed.  This patch contains the same version of Mobile that was
    shipped in 4.1-TMF-0021.

    It is recommended that endpoint patch 4.1-LCF-0022 (or a later
    endpoint patch) be installed on the endpoint where Mobile is
    running.

    3) This patch contains a new version of JRIM that can be installed
    from the 41TMF030/JAVA/JRIM41 subdirectory.  This version of JRIM
    is also provided in certain TEC patches and releases to correct a
    connection problem (internal CMVC defect 154944). The JRIM in this
    patch is supplied for consistency with those TEC patches /
    releases.  Note: This version of JRIM is installed as a product,
    not as a patch.

    4) A new version of JCF is provided in the 41TMF030/JAVA/JCF41
    subdirectory and can be installed using the Tivoli GUI install
    mechanism. These JCF images are a prerequisite for the JRIM images.
    Thus, if JRIM is to be installed, then JCF must also be installed.

    5) The installation image for APAR IY44586 is contained in
    subdirectory 41TMF030/41MD201.  The new mdist2gui.jar in this
    directory replaces the mdist2gui.jar provided in the GA release of
    4.1.  The prior installation of the MDist2 GUI is the only
    prerequisite for the installation of 41TMF030/41MD201.

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

    $BINDIR/TMF/LCF/MDist2Launcher
    $BINDIR/TMF/LCF/MDist2GUI.sh
    $MSGCAT/C/MDist2Launcher_msg.cat

    InstallShield images for Tivoli Desktop for Windows installation on
      Windows NT, Windows 95, and OS/2.
    Setup.exe binaries for Mobile installation on Windows NT and Windows
      95. 

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 4.1-TMF-0030.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 4.1-TMF-0030.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 4.1-TMF-0030 using the file browser,
            and select the PATCHES.LST file by double-clicking it.
        g)  Select 4.1-TMF-0030 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 4.1-TMF-0030 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
            4.1-TMF-0030 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 4.1-TMF-0030 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 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.
            Select the patch by clicking on it. 
        f)  Select the clients to install this patch on. This patch
            needs to be installed on gateway machines.
        g)  Press the "Install" button to install the patch.

Additional Installation Instructions:

    4.1-TMF-0030 contains installation images in several subdirectories.
    For details, see the "Database Changes and Special Considerations"
    section above.

Known Defects:

    None.
