RE: debug not working with CLP??

Sounds like you're not setting a breakpoint. STRDBG, locate where you
want the program to stop, put your cursor on a line, and hit F6. F12 to
get out of debug, then call the program. It should run to the
breakpoint.

> -------- Original Message --------
> Subject: Re: debug not working  with CLP??
> From: "Booth Martin" <booth@xxxxxxxxxxxx>
> Date: Tue, October 04, 2005 11:59 am
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> 
> I used both  suggested options, and the debugger doesn't show a page, blank
> or otherwise.  If i run the program it just runs as if it isn't in debug,
> but it is.
> 
> I'll just continue to change it to CLLE to debug, then change it back after.
>   
>  
> ---------------------------------
> Booth Martin
> http://www.martinvt.com
> ---------------------------------
> -------Original Message-------
>  
> From: Midrange Systems Technical Discussion
> Date: 10/03/05 23:16:13
> To: Midrange Systems Technical Discussion
> Subject: Re: debug not working with CLP??
>  
> If the debug screen opens and you see no source, then you did not
> compile the program with debug information, as someone else
> mentioned. Probably. I don't remember, but it might be that you get
> no message when debugging OPM programs, as I think you do with an ILE
> program that has no debug information.
>  
> If you do have source showing, F6 sets the breakpoint. I strongly
> suggest also using F1 at the command line, where you can get more
> information. E.g., you can set a breakpoint that breaks when a
> certain condition is met. There are also options to run for a certain
> number of statements, IIRC.
>  
> If you have source showing and set no breakpoint, you can have the
> program stop at the first executable statement by using F10,
> otherwise used for stepping statement by statement. If you use F12
> without setting a breakpoint, you will not stop in the running of the
> program. In this latter case, use DSPMODSRC to show the source again,
> then set a breakpoint or use F10.
>  
> Also, as I said in another post, I suggest doing everything as CLLE -
> there are only a couple gotchas to watch out for, and you can find
> about them in the CL manual, IIRC, or in an ILE manual.
>  
> HTH
> Vern
>  
> At 02:39 PM 10/3/2005, you wrote:
>  
> >If I try to debug a CLP program with STRDBG OPMSRC(*YES)  The debugger
> >starts but there are no breakpoints, nor a place to set them, that I can
> >find.
> >
> >What I have done is to change the source from CLP to CLLE, compile it, and
> >then start the debugger, find my problems, fix them, and then change the
> >source back to CLP.  That seems pretty bush league to me.  I should be
> smart
> >enough to debug CLP, right?
> >
> >The question I was asking is: How does one use the debugger for CLP?
> >
> >
> >
> >---------------------------------
> >
> >Booth Martin
> >
> >http://www.martinvt.com
> >
> >---------------------------------
> >
> >-------Original Message-------
> >
> >
> >
> >From: Midrange Systems Technical Discussion
> >
> >Date: 10/03/05 14:27:35
> >
> >To: Midrange Systems Technical Discussion
> >
> >Subject: Re: debug not working with CLP??
> >
> >
> >
> > > Thats exactly what I have been doing, but it seems pretty bush league to
> >me,
> >
> > > so i was asking the experts here..
> >
> >
> >
> >*what* is bush league?  What is your question, exactly?  What part of
> >
> >debugging a program leaves you looking for a better alternative?  Because
> >
> >I haven't a clue what you're getting at.
> >
> >
> >
> >--
> >--
> >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> >To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> >To subscribe, unsubscribe, or change list options,
> >visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> >or email: MIDRANGE-L-request@xxxxxxxxxxxx
> >Before posting, please take a moment to review the archives
> >at http://archive.midrange.com/midrange-l.
>  
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>  
> .
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.