IV08641: BDT SERVICE CRASHES

Tivoli Framework Patch 4.1.1-TMF-0129

APAR status

• Closed as program error.

Error description

• bdt_service carshes with CORE file.
  Following entris can be seen from core result.
  core '/var/spool/Tivoli/db/tivoli.db/core' of 27818:
  bdt_service
   ff238c38 write_all_reads (f2a7c0, 1, bf6000, 1, d7580, 0) + 1a8
   ff239880 bdt_new_conn_thread (af5620, ff2390cc, bf60c0,
  ff2c387c,
  fedee308, 0) + 7b4
   ff2c3894 tmf_cthread_body (bea1d0, 2000, 1, ff2c43e4, fedee308,
  fedf76f0) + cc
   ff2c4864 ???????? (ad5f4, bea1d0, bf61a0, bfc0, 0, bea1d1)
  -------------------------
   Also, bdtlog may leave some messages below..
  2011/06/07 03:04:37 -09: BDT_CONNECT: timeout or abort (24) on
  semaphore
  - channel aborted (169292574I51008IX2:000218a34DED08A5 optman50)
  2011/06/07 03:04:39 -09: query: port=51008 status=1
  2011/06/07 03:05:01 -09: query: port=51008 status=1
  2011/06/07 03:05:10 -09: status: BDT service is OK: port=51008
  status=1
  2011/06/07 03:10:01 -09: query: port=51008 status=1
  2011/06/07 03:10:10 -09: status: BDT service is OK: port=51008
  status=1
  2011/06/07 03:10:23 -09: query: port=51008 status=1
  2011/06/07 03:10:23 -09: query: port=51008 status=1
  2011/06/07 03:15:00 -09: query: port=51008 status=1
  2011/06/07 03:15:10 -09: status: BDT service is OK: port=51008
  status=1
  2011/06/07 03:20:00 -09: query: port=51008 status=1
  2011/06/07 03:20:10 -09: status: BDT service is OK: port=51008
  status=1
  2011/06/07 03:20:48 -09: BDT log file is opened
  2011/06/07 03:20:48 -09: BDT service status thread is created
  2011/06/07 03:20:48 -09: status: status thread has started
  2011/06/07 03:20:48 -09: Initialize BDT service.
  2011/06/07 03:20:48 -09: Initialize BDT service.
  ---
  

Local fix

• non, but the bdt_service is a process which can start up
  automatically depends on the requirement.
  

Problem summary

• ************************************************************
  * USERS AFFECTED:
  * Users using the Single Port BDT
  ************************************************************
  * PROBLEM DESCRIPTION:
  * The bdt_service crashes in the write_all_reads function.
  ************************************************************
  * RECOMMENDATION:
  * Apply the fix when available.
  ************************************************************
  

Problem conclusion

• The local fix module has been sent to the customer.
  The fix will be included in the future GA patch.
  

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:

Fix information

• Fixed component name

  MGMT. FRAMEWORK

• Fixed component ID

  5698FRA00

Applicable component levels

• R431 PSY

     UP