A fix is available
APAR status
Closed as program error.
Error description
There is a timing window on client side deduplication which can cause a server crash if the client ends the main session before the chunk query session terminates. It is not guaranteed to result in a crash, but rather is just a timing window issue when the client main session and chunk query session are ending at the same time. The client should finish the chunk query session first but this does not always occur. Customer/L2 Diagnostics (if applicable) Call stack: (dbx) where tmAbortX(??, ??, ??) at 0x1000b5660 bfEndChunkQrySession(??) at 0x1005ca0c4 SmNodeSession(??, ??) at 0x10066762c HandleNodeSession(??, ??, ??) at 0x100198588 smExecuteSession(??, ??, ??, ??, ??, ??, ??, ??) at 0x10018d1e8 psSessionThread(??) at 0x100057904 StartThread(??) at 0x100020bdc The following ANR9999D message may also be seen: ANR9999D_0974559572 bfDedupEndSession(bfddedup.c:1167) Thread<46363>: bfSessP 11c03ec78, Bad eyecatcher. (SESSION: 15914) ANR9999D Thread<46363> issued message 9999 from: (SESSION: 15914) SSION: 15914) ANR9999D Thread<46363> 0x000000010000d1b8 StdPutText (SESSION: 15914) ANR9999D Thread<46363> 0x000000010000dc34 OutDiagToCons (SESSION: 15914) ANR9999D Thread<46363> 0x0000000100008e9c outDiagfExt (SESSION: 15914) ANR9999D Thread<46363> 0x00000001005ccd00 bfDedupEndSession (SESSION: 15914) ANR9999D Thread<46363> 0x000000010069a230 EndDedupBfSession (SESSION: 15914) ANR9999D Thread<46363> 0x000000010067f37c EndBfSession (SESSION: 15914) ANR9999D Thread<46363> 0x00000001006903d4 CloseSessStats (SESSION: 15914) ANR9999D Thread<46363> 0x00000001006672e0 SmNodeSession (SESSION: 15914) ANR9999D Thread<46363> 0x000000010019858c HandleNodeSession (SESSION: 15914) ANR9999D Thread<46363> 0x000000010018d1ec smExecuteSession (SESSION: 15914) ANR9999D Thread<46363> 0x0000000100057908 psSessionThread (SESSION: 15914) ANR9999D Thread<46363> 0x0000000100020be0 StartThread (SESSION: 15914) *NOTE* None Platforms affected: Server 6.2, 6.3 Unix/Linux/Windows Initial Impact: Medium Additional Keywords: crash core abend ZZ63 ZZ62 dedup chunk
Local fix
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.2.5 and 6.3.4. 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
IC83697
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
63A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-05-23
Closed date
2012-10-29
Last modified date
2012-10-29
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
R62A PSY
UP
R62H PSY
UP
R62L PSY
UP
R62S PSY
UP
R62W PSY
UP
R63A PSY
UP
R63H PSY
UP
R63L PSY
UP
R63S PSY
UP
R63W PSY
UP
[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"63A"}]
Document Information
Modified date:
19 September 2021