ibmi-brunch-learn

Announcement

Collapse
No announcement yet.

Setting Conditional Break Points in Debugging an Interactive Job

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Setting Conditional Break Points in Debugging an Interactive Job

    Hi,

    I need to debug a RPGLE program by setting conditional breakpoints.

    Currenlty, I am using the following command for setting conditional break point

    Break 70 When Acct# = 100

    But i need to debug the program if the Acct# is either 100 or 150.

    So, I need to modify the above command

    as 'Break 70 When Acct# = 100 or Acct# = 150'

    The above command is having syntax error.

    Can anyone help in this.

  • #2
    Re: Setting Conditional Break Points in Debugging an Interactive Job

    Surya,

    As far as I know, you can only use one condition on a break | when type of condition. You could set the other break condition on the line before or after 70.

    HTH,
    MdnghtPgmr
    "Tis better to be thought a fool then to open one's mouth and remove all doubt." - Benjamin Franklin

    Comment


    • #3
      Re: Setting Conditional Break Points in Debugging an Interactive Job

      Thanks for the reply

      Comment


      • #4
        Re: Setting Conditional Break Points in Debugging an Interactive Job

        Hi

        The way I come around such conditional break is to add aditional lines in *SRC with exact condition to test with IF/ENDIF statements. Then I temporary compile program in QTEMP, execute STRDBG between IF/ENDIF statements. Debugger will stop when the condition will reach. When solution is found, remove the IF/ENDIF statements from *SRC, compile program again, and that it is.
        LP Zdenko

        Comment


        • #5
          Try adding parenthesis for each condition: Break 70 When (Acct# = 100) or (Acct# = 150)

          Comment


          • #6
            I'm not sure why you're responding to a thread posted in 2006? I've not used conditional breakpoints but it is likely things have changed since then...

            Comment

            Working...
            X