× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Peter

Isn't this the normal behavior when you specify *SOURCE for debug view? If I do that, then I need the source for any kind of debugging. That's one reason I use *ALL.

Now when we distribute product, we strip all debugging information. But I always have a fully-debuggable module around - well, for some stuff - and can get it to a production machine as needed for testing.

And *SOURCE on SQL modules is the same as *ALL, I'm told - could be wrong there, but it seems to work.

Regards
Vern

Colpaert, Peter wrote:
The one big disadvantage of SEP debugging (in my opinion) is that it won't remember any added sources.

Our sources are on the development system, and if I want to debug a program on the production system, I have to add - every time - the source member on the other system.

I understood that this was on the to-do list of the WDSCi team (?).


Peter Colpaert
Software Engineer, Philips Consumer Luminaires

Industrieterrein Satenrozen 11, 2550 Kontich, Belgium
Tel. +32/ 3 450 74 09, Fax +32/ 3 450 74 33, Internal 1317
peter.colpaert@xxxxxxxxxxx, www.philips.com

Simply Switch to printing double-sided and printing less






-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-
bounces@xxxxxxxxxxxx] On Behalf Of GKern@xxxxxxxxxxxxxxxx
Sent: donderdag 30 april 2009 17:38
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Why upgrade from WDSC to RDi?

"Okay, what is SEP?"

Service Entry Point - as noted by another respondent.

This is the only way to debug programs nowadays, and this is especially
true for batch jobs since SEP does all the service job tasks
automatically. It also allows you to step in and out of modules &
procedures too without having to register each object in a 'debug
mode'.

Just last week I found that while I was editing a source member, I
could
set a breakpoint (just for the heck of it - and I wasn't in debug
mode). I
tested the program in debug and sure enough the program stopped at my
breakpoint.

A small thing but its an advantage in that I can set break points while
editing or reviewing code which means I don't have to remember all my
'attention points' when I do get into debug mode.

And SEP will remember your monitored variables and breakpoints so that
if
I need to debug the same program in the future those debug properties
are
still intact.

And the monitor view lets you observe all your variables.


The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.