IC37588: ANR2571W SCHEDULED SESSION DENIED

APAR status

• Closed as program error.

Error description

• Customers' may run into an issue with
  the TSM Scheduler denying access to all
  incoming scheduled sessions. Here is the
  message that will be issued:
  .
  ANR2571W Scheduled session from node XXXXXXX (XXX)
  has been denied, scheduled sessions are not currently
  available.
  .
  This message will be issued for every scheduled
  session that is attempting to access the TSM
  Server. It does not matter if the schedule is running
  in prompted or polling. ALL scheduled session
  activity will be disabled until the TSM Server is
  recycled. The problem is that the CSV->sessionsInUse
  is not being decremented in certain instances.
  An example of this would be if a client is
  rejected because it is down-level. The session
  would exit without decrementing the counter.
  .
  To determine if a customer is suffering from this
  issue, have them issue the following commands:
  .
  Show csvars
  Show session
  .
  The show csvars will reveal 2 fields which are
  important:
  Sch Sessions in use : XX
  Max Scheduled Sessions : XX
  .
  These values will most likely match indicating
  the maximum number of scheduled sessions have
  been reached. The customer should then
  analyze the Show session output and verify
  that XX number of sessions are active as
  indicated in the Show csvars output.
  .
  If the Show csvars count and Show session count
  do not match, then more than likely this APAR
  applies. Obviously, if the Show csvars and Show
  session match, then the maximum number of scheduled
  sessions have been reached and the customer should
  look at reducing the scheduled sessions during
  this timeframe or increase the maximum scheduled
  sessions.
  .
  NOTE:
  This APAR applies to all TSM Server platforms.
  .
  Initial Impact: Medium
  Additional Keywords: Global variable central scheduler
                       denied sess MSGANR2571W polling
                       prompted ANS1351E
  .
  Local Fix:
  1) Recycle the TSM Server.
  2) Review the actlog for the session which is
  being continuously rejected and address the
  problematic node.
  

Local fix

• 1) Recycle the TSM Server.
  2) Review the actlog for the session which is
  being continuously rejected and address the
  problematic node.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All ITSM users running scheduled sessions.   *
  ****************************************************************
  * PROBLEM DESCRIPTION: See error description.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing PTF when available. This        *
  *                 problem is currently projected to be fixed   *
  *                 in PTF level 5.2.3 and 5.1.9. Note that      *
  *                 this is subject to change at the             *
  *                 discretion of IBM.                           *
  ****************************************************************
  Scheduled sessions that terminate during session
  initialization can still count as a scheduled session
  in use after the session terminates.  Reasons for the
  termination during session initialization include
  invalid password and down level client.
  

Problem conclusion

• The server has been modified to remove these
  session from the number of scheduled sessions in use.
  

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:

  PQ83106 PQ83107

Fix information

• Fixed component name

  TSM SERVER 510

• Fixed component ID

  5698ISMSV

Applicable component levels

• R51A PSY

     UP

• R51H PSY

     UP

• R51L PSY

     UP

• R51P PSY

     UP

• R51S PSY

     UP

• R51W PSY

     UP

• R52A PSY

     UP

• R52H PSY

     UP

• R52L PSY

     UP

• R52P PSY

     UP

• R52S PSY

     UP

• R52W PSY

     UP