PH27715: IDZ EDIT BREAKPOINT WIZARD NOT SHOWING UP WHEN EDITING BREAKPOINT DURING REMOTE DEBUG

APAR status

• Closed as program error.

Error description

• IBM Developer for Z/OS - IDz - v14.2.3
  
  During a remote debug session on IDz, if the user try to edit
  an existing breakpoint, by right-clicking the breakpoint and
  selecting 'Edit Breakpoint', a wizard dialog is presented
  allowing the user to make changes and save them.
  
  However, when debugging a program and trying to edit a
  breakpoint the wizard dialog does not show up, and no pop-up
  error message is presented.
  
  Checking the Error Log view, the user will find a Unhandled
  event loop exception. Opening this error event, the user will
  see the following on the Exception Stack Trace:
  java.lang.StringIndexOutOfBoundsException: String index out of
   range: 0
  
  Top entries on the stack trace point to LineBPWizardPage on
  the com.ibm.debug.pdt.internal.ui.dialogs component.
  
  This issue happens when the load modules source dataset names
  do not have a common path or high level qualifier (HLQ).
  

Local fix

• As a workaround the user can remove the existing breakpoint,
  and add a new one with the required changes.
  If the breakpoint to be re-added is not on the source of
  where the current program is suspending, the user need
  to open the source first from the Module view.
  Removing and adding breakpoints is not affected by this issue.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users who uses remote debug and wants to modify a created    *
  * statement breakpoint                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * During a remote debug session, the Edit Breakpoint dialog    *
  * does not appear when attempting to modify a breakpoint.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• This problem was caused by incorrect perception source file
  names of program's compile units will share same common path.
  
  This problem is fixed in the following products:
  - IBM Debug for z/OS
  - IBM Developer for z/OS
  - IBM Developer for z/OS Enterprise Edition
  

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

  DEV FOR Z/OS

• Fixed component ID

  5724T0700

Applicable component levels