× 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: Debugging COBOL ILE - a BUG?
  • From: "Schaefer P. ONeill" <soneill@xxxxxxxxx>
  • Date: Mon, 30 Jul 2001 10:19:24 -0400

There is a compiler directive that is needed to avoid sparse-ing memory of 
unused variables.  If you have the compiler options book, you should be 
able to find it ...

Good Luck,
Schaefer

At 08:18 AM 7/30/01 , you wrote:


>Hello.
>
>Does anyone know why a WORKING-STORAGE element definition on lowest level, 
>is not available in the 'EVAL' command in the debugger, UNLESS IT IS 
>REFFERED TO WITHIN PROCEDURE DIVISION?
>
>An example from real life:
>
>WORKING STORAGE SECTION.
>01 WS-FIELDS.
>       05 X                     PIC 9.
>       05 Y                     PIC 9.
>
>PROCEDURE DIVISION.
>MAIN SECTION.
>A-000.
>           move 1 to X        (note that Y is not reffered to)
>...
>debugging: EVAL X  gives result = 1 (OK)
>                         EVAL Y gives error message 'Identifier does not 
> exist'
>
>In my example, the 'Y' got its value in return  from a called procedure, 
>but was not available in the debugger neither before nor after tha call!
>
>
>
>Mvh.
>
>Geir
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.265 / Virus Database: 137 - Release Date: 7/18/01

Schaefer P. ONeill
7912 O'Neal Road
Raleigh, NC  27613-1047
(919)-571-0046 (voice)
(919)-571-0048 (fax)
(877)-668-7255 (toll free)

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.