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:

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

Unreferenced data items are included in the compiled module.



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


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.
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page