IBM Support

PI92362: DEBUGGING COMPOSIT ASSEMBLER MODULE IN REMOTE DEBUGGER : CAN NOTSET BREAK POINTS AFTER LDD OF NON ACTIVE CU

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • After you did the following in your current assembler debug
    session:
    Issue a LDD of not current CU
    Go to module pane
    expand down this CU
    double click on it
    you do not see the source for this CU (you need to do a find)
    the source is still commented out - but you can set break
    points ( Source should not be commented out anymore )
    *********
    Hit STEP to set focus back to the active CU ( STEP will be
    executed too)
    you can not set break points in the current CU anymore
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users who debug HLAsm with multiple compile units in the     *
    * same file using the language editor System z LPEX Editor.    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When using the modules view to switch between compile units  *
    * that point to the HLAsm file, a user is no longer able to    *
    * add breakpoints to the compile unit in which they are        *
    * currently stepping.  This problem only occurs when using the *
    * language editor System z LPEX Editor.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • This problem was caused by the debug UI not correctly handling
    the scenario when multiple compile units point to the same file
    and was not resetting the compile unit mapped to the language
    editor System z LPEX Editor.
    
    This issue is fixed in the following products:
    IBM Developer for z Systems
    IBM Developer for z Systems Enterprise Edition
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI92362

  • Reported component name

    DEV FOR Z SYS

  • Reported component ID

    5724T0700

  • Reported release

    E10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-15

  • Closed date

    2018-12-07

  • Last modified date

    2018-12-07

  • 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 SYS

  • Fixed component ID

    5724T0700

Applicable component levels



Document information

More support for: Rational Developer for System z

Software version: E10

Reference #: PI92362

Modified date: 07 December 2018