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



It has to do with the compile options. The default option is *NOUNREF which
means that if the variable is not referenced in the module, you will not be
able to see the contents in debug or a program dump. If the module is
compiled with the option *UNREF, then those variables will be available for
debug and dumps.

From the compile help:

*NOUNREF
Unreferenced data items are not included in the compiled module.
This reduces the amount storage used, allowing a larger program
to be compiled. You cannot look at or assign to an unreferenced
data item during debugging when the *NOUNREF option is chosen.
The unreferenced data items still appear in the cross-reference
listings produced by specifying OPTION (*XREF).

*UNREF
Unreferenced data items are included in the compiled module.

HTH

Jim

On Wed, Dec 23, 2009 at 10:04 AM, twrpwrorl none <twrpwrorl@xxxxxxxxxxx>wrote:


Hello.



We've just moved from COBOL OPM to COBOL ILE. When deliberately producing
a dump by calling QlnDumpCobol, I'm not getting a dump of ALL the variables.
But I am getting some of them. I can't understand why. I have several
fields in one 01-level which is in the FILE SECTION. The fields are copied
in using COPY DD-ALL-FORMATS. Yet only one field from this 01-level is
printed in the dump. I've searched on QlnDumpCobol but it only tells me
that fields must be in the "HLL symbol table" for them to be dumped. I
would think all fields would be in the symbol table, but I don't know much
about this.



Any ideas why fields are not appearing in the dump? TIA.

_________________________________________________________________
Hotmail: Free, trusted and rich email service.
http://clk.atdmt.com/GBL/go/171222984/direct/01/
--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
list
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.