OA41925: TEBS: COMMUNICATION FAILURE FROM SERVICE THREAD SHORTAGE

IBM Tivoli Monitoring 6.2.3 Fix Pack 5 (6.2.3-TIV-ITM-FP0005)
IBM Tivoli Monitoring 6.2.3 Fix Pack 4 (6.2.3-TIV-ITM-FP0004)
Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Environment:
  
  This defect is specific to z/OS platforms.
  
  Problem Description:
  
  The proliferation of Tivoli Monitoring agents residing in a
  Tivoli Monitoring server address space results in a
  communications lockup and address space-wide communication
  failures.  This limitation was found in ITM 6.23 but is known to
  exist in all versions of ITM.
  
  Detailed Recreation Procedure:
  
  This can be recreated by configuring a Tivoli Monitoring server
  with five or more Tivoli Monitoring agents configured to reside
  in the same address space.
  
  Related Files and Output:
  
  The signature of this failure can be seen in a state capture as
  the existance of 8 or more active rpc__listen calls.
  
  Severity:    1
  
  Approver:   NC
  

Local fix

Problem summary

• ****************************************************************
  
  * USERS AFFECTED: All ITMS/ENGINE users.                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: IBM TIVOLI MONITORING PRODUCT           *
  *                      COMMUNICATION FAILURES RESULT FROM      *
  *                      the PTF.                                *
  ****************************************************************
  * RECOMMENDATION: ApplySERVICE THREAD SHORTAGE.                *
  ****************************************************************
  The proliferation of IBM Tivoli Monitoring agents residing
  in a IBM Tivoli Monitoring server address space can result
  in a communications lockup and address space-wide
  communication failures.  This limitation was found in IBM
  Tivoli Monitoring 6.23 but is known to exist in all
  versions.  There is no other external symptom other than
  address space-wide rpc and http request timeouts.  The
  signature of this failure can be seen in a state capture as
  the presence of 8 or more active rpc__listen calls.
  

Problem conclusion

• The code has been changed to make the number of service
  threads default to 16.  The previous default was 8.  The
  default service threads can be configured using environment
  variable KDEB_MAX_SERVICETHREADS set to the desired number.
  
  The code has been changed to terminate the address space
  with a U0200 ABEND when a service thread shortage is
  detected.  The following two messages are issued with the
  U0200 ABEND:
  
  ***ERROR: Unable to start new service thread, maximum of <n>
  reached
  Set KDEB_MAX_SERVICETHREADS environment variable to support
  a larger number of service threads
  

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:

  OA43258

Fix information

• Fixed component name

  CT/ENGINE

• Fixed component ID

  5608A41CE

Applicable component levels

• R623 PSY UA71031

     UP13/10/23 P F310

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.