|
Or move the cursor where you want it and hit "run to location" in WDSC. Duane -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Michael_Schutte@xxxxxxxxxxxx Sent: Thursday, April 20, 2006 1:26 PM To: RPG programming on the AS400 / iSeries Subject: Re: Tool to convert Subroutine to SubProcedure But there's another way around that. Put a break point immediately after the subroutine and let it run... :)) Michael Schutte David Gibbs <david@xxxxxxxxxx om> To Sent by: rpg400-l@xxxxxxxxxxxx rpg400-l-bounces@ cc midrange.com Subject Re: Tool to convert Subroutine to 04/20/2006 02:22 SubProcedure PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@midrang e.com> Peter Dow (ML) wrote: > There is one minor benefit to simply changing subroutines to procedures > -- when debugging to step through the code, you can choose to not go > through a procedure by simply pressing F10; to step into the procedure > you would have to press F22. Now that you mention it ... that *IS* a fairly good reason to convert subroutines to procedures, even if you don't do anything else. david -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.