IBM Support

IT05023: ANR1130E MESSAGE ABOUT LOCK CONFLICT DURING DATA MOVEMENT

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • During data movement operations  in sequential devices that
    involve  large files,
    the following error is issued:
    
    ANR1130E <Process>  is ended for volume <Volume Name>
    There is a lock conflict. (SESSION: <ID> , PROCESS: <ID>)
    
    Customer/L2 diagnostics:
     When files are large compared to the volume size they end up
    needing to span volumes often with part on each volume.
    For example, with migration,  each process is assigned a volume
    to work on with each process working on the objects on   that
    volume as well as the   objects that span onto other volumes.
    As migration is working it needs
    to get locks on the  files as it evaluates the objects to move
    and eventually moves them.  When there are  objects spanning
    across multiple volumes the migration processes can end up
    waiting on a lock for  an object this is currently being moved
    by another process as it evaluates objects to move.
    This  started showing up after the change for APAR  IC94886 that
    added an extra level of locking when doing
    autocopy during migration to prevent conflicts with "backup
    stgpool".
    
    
    Tivoli Storage Manager Versions Affected:  Tivoli Storage
    Manager Server v6.3.5  on all platforms.
    
    
    Initial Impact: Medium
    
    Additional Keywords: ANR1130E lock conflict migration autocopy
    IC94886 MDVREGR-6.3.3-TSMSRV
    

Local fix

  • Turning off autocopy will prevent these lock conflicts.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Tivoli Storage Manager server users.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * projected to be fixed in levels 6.3.6, 7.1.1.100, and 7.1.3. *
    * 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

    IT05023

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-10-23

  • Closed date

    2015-05-05

  • Last modified date

    2015-05-05

  • 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

  • R63A PSY

       UP

  • R63H PSY

       UP

  • R63L PSY

       UP

  • R63S PSY

       UP

  • R63W PSY

       UP

  • 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: 63A

Reference #: IT05023

Modified date: 05 May 2015