IBM Support

IT03330: DATA MOVEMENT OPERATIONS MIGHT NOT RECOGNIZE A CANCEL REQUEST IN A TIMELY MANNER.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Data movement operations might not cancel in a timely manner if
    the files being moved are very large. How large is relative to
    the environment but the delay is usually noticeable for files
    that are 10GB and larger. In addition, files that are
    deduplicated usually take longer to cancel than files that
    are not deduplicated. The problem is that the current cancel
    recognition code is only regulated at the file level such
    that if the process is currently moving data for one file that
    movement must be complete before the cancel is recognized
    For deduplicated files, all data chunks for the given file
    must be processed and moved before the cancel is recognized.
    This APAR will build in more granularity for the cancellation
    recognition within the data movement processes. There will
    still be occurrences for when a cancel process might not
    be recognized for a longer period of time even after the fix
    for this APAR is applied. For instance, if a large file has
    been completely moved but the transaction is waiting for the
    final commit from the database, this cannot be terminated early
    and the transaction commit will be allowed to complete.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Tivoli Storage Manager server users.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See error description.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * This problem is projected to be fixed in 7.1.3 and above.    *
    * Note that this is subject to change at the discretion of     *
    * IBM.                                                         *
    ****************************************************************
    

Problem conclusion

  • This problem was fixed.
    Affected platforms:  AIX, HP-UX, Solaris, Linux, and Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT03330

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    71A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-23

  • Closed date

    2014-08-26

  • Last modified date

    2015-01-28

  • 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 SERVER

  • Fixed component ID

    5698ISMSV

Applicable component levels

  • R71A PSY

       UP

  • R71H PSY

       UP

  • R71L PSY

       UP

  • R71S PSY

       UP

  • R71W PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 7.1.3

Reference #: IT03330

Modified date: 28 January 2015