× 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: help: how to debug CLLE program - no one answered!
  • From: Scott Klement <klemscot@xxxxxxxxxxxx>
  • Date: Tue, 6 Feb 2001 18:05:20 -0600 (CST)


I tried two different CLLE programs... one doing a RCVF from a database
file, the other doing a RCVF from a display file.

Both EVAL and F11 seem to work just fine in STRDBG. 

I'm at V3R2, though.  



On Tue, 6 Feb 2001 StoneJ@GourmetAward.com wrote:

> When I use STRDBG to debug a CL program (type=CLLE), I cannot seem to view
> variable value using EVAL in some situations.
> 
> Here is the error message I receive:
> 
>  Tried to refer to all or part of an object that no longer exists. + 
>  Error occurred during operation.
> 
> This error occurs at both v4r4 and v4r5.  I traced the problem to the RCVF
> command - anytime I use that command I cannot view any variables with F11. 
> 
> Could someone else please try to debug a CLLE program and display a variable
> value when a pgm contains RCVF.  Does it work for you???
> 
> Any ideas how to work around this?
> 
> Thanks

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.