Re: Module does not contain debug data -- WDSCI-L

× 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.

Subject: Re: Module does not contain debug data
From: qsrvbas@xxxxxxxxxxxx
Date: Fri, 18 Jan 2008 13:54:41 -0800
List-archive: <http://archive.midrange.com/wdsci-l>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Websphere Development Studio Client for iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

Buck wrote:

Justin Taylor wrote:

I am trying to set an SEP for an RPGLE program. I enter the Program,
Module and Procedure names and receive a message that says, "Module
(module name) does not contain debug data".

This is most probably a compile option, DBGVIEW. I personally prefer *LIST, but some like *SOURCE. The other thing to consider is OPTIMIZE - it needs to be *NONE.

When I compile for debug, I always use DBGVIEW(*ALL). I haven't seen where it has any drawbacks and there are rare circumstances when it's very useful.

Tom Liotta

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.