APAR status
Closed as program error.
Error description
A client scheduler session is not being terminated after being idle longer than the IDLETIMEOUT value. A change made with IC50193 allows a client scheduler session to remain active longer than the IDLETIMEOUT value. This may cause sessions to remain active on the server even when the connection has been terminated somewhere in the network. The active sessions may prevent other sessions from starting because either MAXSESSIONS has been reached, or, on MVS, the internal structure that is used to keep track of connections may be exhausted resulting in the message: ANR9999D BPX1COMM(2377): ThreadId <448> Bpx1Listen: No index for communication ANR9999D block...close socket and continue. Client scheduler sessions that have been idle longer than the IDLETIMEOUT (idle timeout) value should be canceled. The SHOW SESSIONS command will display information not displayed by the QUERY SESSION command and includes the session type for a client scheduler session as "SessType=5". The server was modified to terminate client scheduler sessions have been idle longer than 48 hours or 1000 times the IDLETIMEOUT (idle timeout) value. Even tho this APAR is being opened against the z/OS server, the problem also exists on other platform servers. TSM Versions Affected: All 5.4 and 5.4 Servers Customer/L2 Diagnostics (If Applicable): None Initial Impact: Medium Additional Keywords: idle timeout | AE 5.3.5.0 | | AE 5.3.5.1 | | AE 5.4.0.2 | | AE 5.4.0.3 |
Local fix
Manually cancel the sessions that have been idle longer than the IDLETIMEOUT value. Use the CANCEL SESSION command. Additional Symptoms: TSM server may display messages indicating that schedules are completing out of order, or that multiple schedules may be active for a node. ANR2576W An attempt was made to update an event record for a scheduled operation which has already been executed - multiple client schedulers may be active for node NODENAME Additional Keywords IdleW IdleWait MSGANR0482W MSGANR2507I MSGANR2576W MSGANS1809W
Problem summary
**************************************************************** * USERS AFFECTED: All TSM server customers. * **************************************************************** * PROBLEM DESCRIPTION: See ERROR DESCRIPTION. * **************************************************************** * RECOMMENDATION: Apply fixing level when available. * * This problem is currently projected * * to be fixed in level 5.3.6 and 5.4.1. * * Note that this is subject to change * * at the discretion of IBM. * **************************************************************** *
Problem conclusion
The TSM server has been corrected.
Temporary fix
Comments
APAR Information
APAR number
IC52799
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
53A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-05-24
Closed date
2007-05-24
Last modified date
2007-06-08
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
R53A PSY
UP
R53H PSY
UP
R53L PSY
UP
R53S PSY
UP
R53W PSY
UP
R54A PSY
UP
R54H PSY
UP
R54L PSY
UP
R54S PSY
UP
R54W PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"53A","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
08 June 2007