IC53464: AE PK43462 FIX COMPLETION - CLIENT SCHEDULER SESSIONS ARE NOT TERMINATED AFTER BEING IDLE LONGER THAN THE IDLETIMEOUT VALUE

APAR status

• Closed as program error.

Error description

• Per APAR IC52799/PK43462, the idletimeout behavior for
  scheduled sessions was changed with APAR IC50193. The
  initial problem was that the fix for IC50193 allowed
  for a master session to remain idle for up to 48 hours
  before being terminated. The fix for APAR IC52799
  changed this behavior so that master sessions would
  remain idle as long as there were associated worker
  sessions still actively backing up data. The master
  session would then recognize that the backup had
  completed and would terminate at some point beyond
  after the completion notification from the client. The
  problem with the previous fix was that the TSM Server
  was not accounting for the possibility that a new
  master session could be started within the same backup
  window, which could cause both master sessions to
  hang indefinitely until forcibly cancelled by the
  TSM server administrator with the cancel session XXXXX command.
  .
  The symptom for this problem will typically be 2
  sessions active per client. One session will show
  a very high idle time (longer than idletimeout) and
  the other one will be in a run state. The session
  in run state will not show any change in
  "bytes sent" or "bytes recvd"
  .
  Q session
  .
   6,203     Tcp/Ip     IdleW      8.6 H        8.5 M       4.2 K
  Node      WinNT        TESTNODE
   7,359     Tcp/Ip     Run          0 S        2.8 M     321.7 K
  Node      WinNT        TESTNODE
  .
  Platforms affected: All TSM 5.4.1 TSM Servers
  .
  Customer/L2 Diagnostics:
  If scheduled sessions are not ending/terminating
  after long periods of time, this APAR most likely
  applies. If show session is issued, the session showing
  high idlewait time should be of sesstype=5:
  show session
  Session 6203:    Type=Node,   Id=TESTNODE
     Platform=WinNT, NodeId=1263, Owner=
     SessType=5, Index=0, TermReason=0
     threadId=197
  There will also be another corresponding session for this node
  with sesstype=5 that has a higher session number:
  Session 7359:    Type=Node,   Id=TESTNODE
     Platform=WinNT, NodeId=1263, Owner=
     SessType=5, Index=2, TermReason=0
     threadId=189
  .
  Initial Impact: High
  .
  Additional Keywords: smmonitorthread affinitycluster affinity
                       timed out term
                       cancel end hung hang maxsession stop q sess
                       show ANR0480W
                       ANR0481W ANS1810E ANS1005E ANS1809W
  

Local fix

• Use Cancel session <session num> for sessions in idlewait that
  are not being terminated by the TSM Server
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: TSM server customers who                     *
  *                 use client schedule.                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available.           *
  *                 This problem is currently projected          *
  *                 to be fixed in level 5.3.6, 5.4.1.1          *
  *                 and 5.4.2. Note that this is subject         *
  *                 to change at the discretion of IBM.          *
  ****************************************************************
  Under certain conditions, TSM server may
  not terminate client scheduler sessions.
  

Problem conclusion

• The TSM server has been corrected.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PK52445 PK52446

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

• R53Z PSY

     UP

• R54A PSY

     UP

• R54H PSY

     UP

• R54L PSY

     UP

• R54S PSY

     UP

• R54W PSY

     UP

• R54Z PSY

     UP