Fixes are available
APAR status
Closed as program error.
Error description
The Tivoli Storage Manager journal daemon times out if it doesn't receive a verb from the client within a default time of 20 minutes. The journal daemon creates a separate listening thread for each session with the client so the time out of each session is independent, means each session has to receive a verb within the configured session time. Even if only one of the sessions opened between the journal daemon and the client times out, the complete backup fails. dsmerror.log shows the following messages: ANS0361I DIAG: unknown thread, fatal error, signal 11 ANS2820E An interrupt has occurred. The current operation will end and the client will shut down. Jbberror.log showed the following messages: ANS0361I DIAG: JnlReadVerb(): Timed out waiting for a verb header to arrive from the client . ANS0361I DIAG: JnlClientSession(Session 1): Error reading data from client, rc=222 . ANS0361I DIAG: psMonitorThread(): exiting RC=0 . L2/Customer diagnostics: Collecting a trace of the journal daemon shows: jnldcomm.cpp ( 970): JnlReadVerb(): Timed out waiting for a verb header to arrive from the client . jnldcomm.cpp (1638): JnlClientSession(Session 2): JnlReadVerb(): rc=222 . JnlClientSession(Session 2): Error reading data from client, rc=222 . JnlClientSession(Session 2): Disconnecting pipe '/tmp/tsmjbbd.pipe.jnlSessionMgr__jnlSession_2'. NpDisconnect(): Entry. JnlClientSession(Session 2): ending with rc=222. closeClientSession(): closing session 2 Initial Impact: Low Additional Keywords: tsm journal incr by date incremental
Local fix
Increase the timeout setting in the tsmjbbd.ini file: [JournalSettings] ; as example set time out to 40 minutes,default is 20 minutes SessionTimeout=2400
Problem summary
**************************************************************** * USERS AFFECTED: Backup-archive client versions 6.3, 6.4 * * and 7.1 running on AIX, Linux and Windows * * platforms. * **************************************************************** * PROBLEM DESCRIPTION: See ERROR DESCRIPTION. * **************************************************************** * RECOMMENDATION: Apply fixing level when available. This * * problem is currently projected to be fixed * * in levels 6.4.2 and 7.1.1. Note * * that until these levels are available, * * this information is subject to change at * * the discretion of IBM. * **************************************************************** *
Problem conclusion
The problem has been fixed so that it no longer occurs.
Temporary fix
6.3.2.3 for AIX and Linux, and 6.3.2.4 for Windows
Comments
APAR Information
APAR number
IC99497
Reported component name
TSM CLIENT
Reported component ID
5698ISMCL
Reported release
64L
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-02-20
Closed date
2014-04-02
Last modified date
2015-04-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
DSMC
Fix information
Fixed component name
TSM CLIENT
Fixed component ID
5698ISMCL
Applicable component levels
R63A PSY
UP
R63L PSY
UP
R63W PSY
UP
R64A PSY
UP
R64L PSY
UP
R64W PSY
UP
R71A PSY
UP
R71L PSY
UP
R71W 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":"64L"}]
Document Information
Modified date:
23 September 2021