This may be related to this:
PK43462: AE IC50193 FIX COMPLETION - CLIENT SCHEDULER SESSIONS ARE NOT
BEING TERMINATED AFTER BEING IDLE FOR A LONG TIME
A specific fix for this item is not yet available electronically
This record will be updated with a link to the fix if the APAR is new.
For APARs older than 365 days, contact your support center.
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.
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.
Mel Dennis
Backup Systems Engineer
Siemens IT Solutions and Services, Inc.
PGST Data Center Operations
4400 Alafaya Trail
MC Q1-108
Orlando, FL 32826
Tel.: 407-736-2360
Mob: 321-356-9366
Fax: 407-243-0260
mailto:melburn.dennis AT siemens DOT com
www.usa.siemens.com/it-solutions
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Fred Johanson
Sent: Thursday, August 23, 2007 1:12 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Immortal sessions
Came in Monday after a week off and saw this on one of my machines:
Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name
Number Method State Time Sent Recvd Type
------ ------ ------ ------ ------- ------- ----- --------
------------------
9,299 Tcp/Ip IdleW 302.6 11.6 M 7.2 K Node WinNT UCTECHSHARE
H
9,708 Tcp/Ip Run 0 S 423 1.8 K Node WinNT UCTECHSHARE
16,642 Tcp/Ip IdleW 254.1 11.6 M 7.2 K Node WinNT UCTECHSHARE
H
16,957 Tcp/Ip Run 0 S 1.1 M 335.8 K Node WinNT UCTECHSHARE
20,296 Tcp/Ip IdleW 230.7 11.7 M 7.2 K Node WinNT UCTECHSHARE
H
20,600 Tcp/Ip Run 0 S 1.1 M 335.8 K Node WinNT UCTECHSHARE
31,976 Tcp/Ip IdleW 157.5 16.9 M 1.8 K Node Linux86 ORWELL
H
32,464 Tcp/Ip Run 0 S 1.6 M 1.8 K Node Linux86 ORWELL
49,883 Tcp/Ip IdleW 38.8 H 11.7 M 7.3 K Node WinNT UCTECHSHARE
50,283 Tcp/Ip Run 0 S 8.2 K 8.6 K Node WinNT UCTECHSHARE
53,680 Tcp/Ip IdleW 14.2 H 10.1 M 6.6 K Node WinNT UCTECHSHARE
54,124 Tcp/Ip Run 0 S 3.0 M 337.9 K Node WinNT UCTECHSHARE
Server is 5.4.1.0, UCT.. Is 5.3.4.0, and ORWELL is 5.4.0.2
Only these two out of 140 clients. Other 5 machines have similar
immortals.
Anyone else seeing such?
|