PM97390: RDz trace causes performance problem due to excessive trace output for the trace points in findBadHex()

8.5.1.6: UI24911 PTF for Rational Developer for System z Host Options
8.5.1.4: UK98515 PTF for Rational Developer for System z Host Options
Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Rational Developer for System z trace causes performance problem
  due to excessive trace output for the trace points in
  findBadHex()
  
  Tracing is activated by specifying debug_level=2 in
  rsecomm.properties or the command /f rsed,appl=rcl on
  
  Analyze of the logs from test1 and showed that the performance
  delay is caused by a very high increase of entries in the
  ffsget.log. The following 2 log output lines are repeated many
  times depending on the source data. Most of these two
  tracepoints are in one or more short timeframes.
  
  14:25:05.720 [ffsgfinf.c:2728 0x21451f00]
               44168340: findBadHex()
               Entered: offset=613688
                       badHexLocations=4416CCA0 badHexValue
                       Addr=4417BDD0  length=80 size=128 (144)
  14:25:05.721 [ffsgfinf.c:2796 0x21451f00]
               44168340: findBadHex()
               Exited: offset=613688
                       badHexLocations=4416CCA0 badHexValue
                       Addr=4417BDD0  count=0 (133)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 01.All RDz users                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: 01.Too much traces in debug_level=2     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  01.The following traces are too much in debug_level=2.
     findBadHex() Entered: findBadHex() Exited:
  

Problem conclusion

• 01.Now, the following traces are written in debug_level=3.
     findBadHex() Entered:
     findBadHex() Exited:
  

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:

Modules/Macros

• FEKFMAIN FEKFMAI6
  

Fix information

• Fixed component name

  RD/Z HOST

• Fixed component ID

  5724T0723

Applicable component levels

• R850 PSY UK98515

     UP13/10/31 I 1000

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.