Re: Step over a subroutine

Vern,

That is what I was doing. But I was in an 20+ year old Order Entry bohemeth full of subroutines and indicators. I had to google CHGJOB SWS(10000100) and *U1, etc. I had never used those!

Anyway... the right-click and Run to Location is perfectly fine.

Another neat thing I found was the ability to copy the Monitor window contents (i.e. huge data structures full of variable data) to the clipboard. I could paste it into Notepad++ and compare the contents from the previous call.

Thanks everyone.

Greg

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Thursday, March 28, 2019 5:14 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Step over a subroutine

Hi Greg

I just put a breakpoint on the line after the EXSR command. Not pretty,
but effective - also, gets ugly when there are so many of the little
beasties.

Ken's suggestion to put breakpoints on the ENDSR could be better if
there are many calls to the same subroutine.

Vern

On 3/28/2019 2:08 PM, Greg Wilburn wrote:

Is there a way to "step-over" a subroutine when going through a program? Something similar to how F6 behaves on a procedure (runs it but doesn't step through it).