IC89544: DURING INSTALLATION OF FASTBACK SERVER, SOME OF THE .JAR FILES ARE NOT PROPERLY UPDATED.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • After FB  6.1.7 Initial installation
    In FastBack Manager GUI >
    Under General Configuration tab>
    Under DR Configuration TAB >
    DR Target TYPE: TSM is selected
    
    Will show following error next to "Enable Throttling":
    RESOURCE ERROR: FBSG_LBL_TSM_DR_ENABLE_THROTTLING
    RESOURCE ERROR: FBSG_LBL_TSM_DR_THROTTLING_BORDER_TITLE
    
    
    Versions Affected:
    FastBack Manager 6.1.7 on all Supported Platforms.
    
    
    Customer/L2 Diagnostics:
    Some installation files in the package
    (mostly .jar files) are unversioned.
    During installation process, a check of the
    "date modified" vs. "date created"
    is being performed for these files
    to decide if the files were modified
    or not after installation.
    If these dates are different,
    the installer will not update these files,
    thus causing the error.
    

Local fix

  • Ensure that all FastBack related folders
    are excluded from AntiVirus scans.
    
    If there is a another FastBack Server
    (identical version only) available,
    copy and replace the contents
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All fastback 6.1.x users and later           *
    ****************************************************************
    * PROBLEM DESCRIPTION: In some systems when upgrading          *
    *                      FastBack to a newer release, not all    *
    *                      of files are updated properly. It       *
    *                      refers to .jar and .cat files. It       *
    *                      causes unpredictable behavior of the    *
    *                      product. Some times it can result       *
    *                      wrong messages, sometimes it can        *
    *                      affect product functionality.           *
    *                                                              *
    *                      The root cause of the problem is that   *
    *                      .cat files and .jar files are           *
    *                      unversioned and the decision if the     *
    *                      file should be updated by installer     *
    *                      is done according to the next rules:    *
    *                      1) Check sum of the new file is         *
    *                      different from the old file             *
    *                      2) The old file is not modified. This   *
    *                      is checked by comparing "date           *
    *                      created" and "date modified" property   *
    *                      of the file. In case it's different,    *
    *                      the file is considered as modified      *
    *                      and is not updated.                     *
    *                                                              *
    *                      In some systems an activity of          *
    *                      antivirus causes these files "date      *
    *                      modified" property to be changed (the   *
    *                      file itself is not modified, only       *
    *                      this proverty is changes). So rule      *
    *                      number 2 is not violated and the file   *
    *                      is considered as modified by            *
    *                      installer and so is not updated.        *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in level 6.1.7.2 Note that this is subject   *
    *                 to change at the discretion of IBM.          *
    ****************************************************************
    Wrong messages, functionality and unexpected issues after
    upgrading to newer FastBack version.
    

Problem conclusion

  • The problem has been fixed to correct this problem. The installe
    r will update now all .jar and .cat files even in case "date mod
    ified" property was changed
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC89544

  • Reported component name

    TSM FASTBACK

  • Reported component ID

    5724FSBBK

  • Reported release

    61W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-16

  • Closed date

    2013-04-07

  • Last modified date

    2013-04-07

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    TSM FASTBACK

  • Fixed component ID

    5724FSBBK

Applicable component levels

  • R61W PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager FastBack

Software version:

6.1

Reference #:

IC89544

Modified date:

2013-04-07

Translate my page

Machine Translation

Content navigation