PM51963: Debug behavior mapping preference setting produces differing results in v8.0.x

Rational Business Developer Fix Pack 3 (8.0.1.3) for 8.0.1
Rational Business Developer Fix Pack 8 (7.5.1.8) for 7.5.1

APAR status

• Closed as program error.

Error description

• Environment: windows
  Product name: IBM? Rational? Business Developer
  
  Program Version    :  8.0.1.1
  Description.
  Debugging with the Debug behavior mapping preference setting
  produces differing results in RBD v8.0.x from that observed in
  v7.1.0.5.
  
  Setting the Debug behavior mapping-? Source as a wildcard (*) .
  Implementing a Call to program or a Transfer to program
  statement within the applicable source code if the target
  program is named in a different case and is within another
  package the debugger produces the following example error : The
  source for the program named ?MYFUNCTION? could not be found.
  Check that its project was successfully built.  Generated code
  will be run instead.
  
  Setting the Debug behavior mapping-? Generated and a wildcard
  (*).
  Implementing a Transfer to program statement within the
  applicable source code the debugger throws the following example
  error:
  com.ibm.etools.egl.interpreter.infrastructure.InternalDebuggerEx
  ception:
  Cannot start ?myfunction?. It is an external program.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When setting the debug behavior mapping to use generated
  code instead of source code, the transfer statement was
  issuing an error because this is not supported. Before the
  behavior mappings were supported for the transfer statement
  there was no error and the source code was always used.
  
  There was also a problem when the case of the transfer
  target did not match the part declaration (for example:
  transfer to "programA" when it is defined as "PROGRAMA").
  This was only a problem if the target was not already
  resolved in the IRs (such as using a variable as the
  transfer target).
  

Problem conclusion

• The transfer statement no longer throws an error if there is
  a behavior mapping says to use generated code. Instead this
  mapping will be ignored and source code will be used, like
  before.
  
  The workspace search for transfer targets is now
  case-insensitive.
  

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

  RATL BUS DEV

• Fixed component ID

  5724S5000

Applicable component levels

• R801 PSN

     UP