RE: Max CL program size for debug? -- MIDRANGE-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: Max CL program size for debug?
From: Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>
Date: Fri, 16 Aug 2002 11:29:03 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I have never run into a limit on CL programs (I have several over 1400
lines).

>The annoying thing is that the maximum
>field length that can be displayed
>in DSPPGMVAR is 2000 bytes.

I declared a 4096 variable, then debugged it with STRDBG and ADDBKP.  This
worked (V5R1):
dsppgmvar '&large' start(2001)

In STRISDB, this worked:
d (2001)&large

  --buck

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.