Direct links to fixes
8.1.1.100-IBM-SPOC-WindowsX64
8.1.1.100-IBM-SPOC-Linuxx86_64
8.1.1.100-IBM-SPOC-Linuxs390x
8.1.1.100-IBM-SPOC-AIX
8.1.1.000-IBM-SPSRV-WindowsX64
8.1.1.000-IBM-SPSRV-Linuxs390x
8.1.1.000-IBM-SPSRV-AIX
8.1.1.000-IBM-SPSRV-Linuxx86_64
6.3.6.100-TIV-TSMALL-SolarisSPARC
6.3.6.100-TIV-TSMSTA-WindowsI32
6.3.6.100-TIV-TSMALL-WindowsX64
6.3.6.100-TIV-TSMALL-Linuxx86_64
6.3.6.100-TIV-TSMALL-Linuxs390x
6.3.6.100-TIV-TSMALL-Linuxppc64
6.3.6.100-TIV-TSMALL-HP-UX
6.3.6.100-TIV-TSMALL-AIX
7.1.7.100-TIV-TSMSRV-WIN
7.1.7.100-TIV-TSMSRV-SolarisSPARC
7.1.7.100-TIV-TSMSRV-Linuxx86_64
7.1.7.100-TIV-TSMSRV-Linuxs390x
7.1.7.100-TIV-TSMSRV-Linuxppc64
7.1.7.100-TIV-TSMSRV-HP-UX
7.1.7.100-TIV-TSMSRV-AIX
IBM Tivoli Storage Manager server V6.3.6.x interim fix downloads
IBM Spectrum Protect Server V8.1 Fix Pack 1 (V8.1.1) Downloads
IBM Spectrum Protect Server V7.1.7.X interim fix downloads
IBM Spectrum Protect Server V7.1 Fix Pack 8 (7.1.8.000) Downloads
APAR status
Closed as program error.
Error description
Under the following circumstances a hang condition can occur when a process or session require a volume that is in use: 1. A process or session requires access to a volume in order to change the volume from the current state to a new state, such as scratch, empty, filling, or readonly. 2. During the state change another process or session has the volume in use as an output volume, and will not allow other sessions or process to have access to the volume. 3. After the session or process using the volume completes, the volume is no longer usable, because the volume is being returned to scratch, or changed to full, or set to readonly. 4. The process or session is hung with in a deadlock trying to recover from the situation while holding internal locks that cause all subsequent volume allocation to hang. When diagnosing the problem look for the following similar out put from the SHOW LOCKS command: LockDesc: Type=36002(as volume id), NameSpace=15568, SummMode=sLock, Key='' Holder: (asvolacq.c:2788 Thread 826091) Tsn=0:16656970, Mode=sLock Waiter: (asvolacq.c:9808 Thread 826091) Tsn=0:16656978, Mode=xLock Use SHOW THREADS/gstack/pstack to find the function on the stack of the hung thread that look similar to the following: pkWaitConditionTracked () WaitForLock () tmLockTracked () AsLockVolIdTracked () CheckForDelete() AsReleaseVol () AsAcquireOutputVol () . Initial Impact: Medium . Tivoli Storage Manager Versions Affected: Applies to all current 6.3 and 7.1 server versions. . Additional Keywords: Hang hung wait session process lock STA TSM
Local fix
Halt and restart the Spectrum Protect server to clear the deadlock.
Problem summary
**************************************************************** * USERS AFFECTED: * * All IBM Spectrum Protect 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.100, 7.1.7.100, 7.1.8, * * and 8.1.1. 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
IT16987
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
71L
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-09-18
Closed date
2016-10-31
Last modified date
2016-12-13
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
Modified date:
26 September 2021