SE56680: RDP 8.0.3 DEBUG WITH SERVICE ENTRY POINTS FAILS WHEN THE RSE CONNECTION NAME CONTAINS AN AMPERSAND ('&') CHARACTER

Rational Developer for i Fix Pack 9.0.1 for 9.0

APAR status

• Closed as fixed if next.

Error description

• If the name of the Remote Systems Explorer (RSE) connection to
  the IBM i in RDP contains an ampersand ('&') character then when
  a program or service program hits an active Service Entry Point
  (SEP) the program will stop and wait for the debugger but the
  debug session will not be activated.
  
  Examination of the workspace Error Log will contain
  "!MESSAGE Could not parse the kicker XML stream"
  followed by a stack trace showing an XML parser error.
  

Local fix

• Change the name of the RSE connection to remove any special
  characters including the '&' character.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Debug users who use the '&' character in     *
  *                 the RSE connection name.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Service entry point debug fails if the  *
  *                      RSE connection name contains the '&'    *
  *                      character.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If the RSE connection name contains the '&' character, service
  entry point debug will fail and the debug session is not able
  to start on the IDE.
  
  This problem is fixed in the RDi 9.0.1 update.
  

Problem conclusion

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

Applicable component levels

• R803 PSY

     UP

• R850 PSY

     UP