A fix is available
APAR status
Closed as program error.
Error description
Begin eventlogging fail with ANR1821W message when eventlogging was begun and ended once. The problem can occur only when using the language other than en_US. Here are an example how the problem would occur while issuing commands: tsm: SERVER>begin eventlogging filetext ANR1825I Event logging active for the FILETEXT receiver. tsm: SERVER>end eventlogging filetext ANR1822I Event logging ended for the FILETEXT receiver. tsm: DUNKIN>begin ev filetext ANR1821W Event logging not started for the FILETEXT receiver. Customer/L2 Diagnostics: ---------------------------------------- The problem can occur when using language other than English. It can be confirmed that the same number of outq entries are remained even after issuing "end eventlogging" command. tsm: SERVER>show outq Stream 1141d3058, buffered=0 (0 blocks), catch opts=, cancelled=0, inReadyBusy=0, outReadyBusy=1 Stream 11285bcd8, buffered=0 (0 blocks), catch opts=Default NoLimitQ , cancelled=0, inReadyBusy=0, outReadyBusy=0 tsm: SERVER>begin eventlogging filetext ANR1825I Event logging active for the FILETEXT receiver. tsm: SERVER>show outq Stream 1143974b8, buffered=0 (0 blocks), catch opts=Default , cancelled=0, inReadyBusy=0, outReadyBusy=1 Stream 1141d3058, buffered=0 (0 blocks), catch opts=, cancelled=0, inReadyBusy=0, outReadyBusy=1 Stream 11285bcd8, buffered=0 (0 blocks), catch opts=Default NoLimitQ , cancelled=0, inReadyBusy=0, outReadyBusy=0 tsm: SERVER>end eventlogging filetext ANR1822I Event logging ended for the FILETEXT receiver. tsm: SERVER>show outq Stream 1143974b8, buffered=0 (0 blocks), catch opts=Default , cancelled=0, inReadyBusy=0, outReadyBusy=1 Stream 1141d3058, buffered=0 (0 blocks), catch opts=, cancelled=0, inReadyBusy=0, outReadyBusy=1 Stream 11285bcd8, buffered=0 (0 blocks), catch opts=Default NoLimitQ , cancelled=0, inReadyBusy=0, outReadyBusy=0 tsm: DUNKIN>begin ev filetext ANR1821W Event logging not started for the FILETEXT receiver. ---------------------------------------- TSM Versions Affected: TSM Servers 6.X on all platforms. Initial Impact: Low Additional Keywords: zz61 zz62 zz63 filetext eventlogging ANR1821W
Local fix
- use en_US language - restart TSM server process
Problem summary
**************************************************************** * USERS AFFECTED: All Tivoli Storage Manager server users of * * event logging. * **************************************************************** * PROBLEM DESCRIPTION: See ERROR DESCRIPTION. * **************************************************************** * RECOMMENDATION: Apply fixing level when available. * * This problem is currently projected to be * * fixed in levels 5.5.7, 6.2.5 and * * 6.3.2. * * Note that this is subject to change at * * the discretion of IBM. * **************************************************************** *
Problem conclusion
This problem was fixed.
Temporary fix
Comments
APAR Information
APAR number
IC80541
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
62A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-12-24
Closed date
2012-02-26
Last modified date
2013-08-22
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
R55A PSY
UP
R55H PSY
UP
R55L PSY
UP
R55S PSY
UP
R55W PSY
UP
R61A PSY
UP
R61H PSY
UP
R61L PSY
UP
R61S PSY
UP
R61W PSY
UP
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":"62A"}]
Document Information
Modified date:
19 September 2021