McKown, John wrote:
I know this is likely an application problem. But the programmers are
likely going to request help in debugging this error. The manual states
that it is most likely a memory overlay problem. But I have no idea how
I, with no application knowledge, can determine which COBOL statement in
their program is causing the overlay. Is there anything that I can
suggest other than using SSRANGE?
ref:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ceea9170/8.0
Compile with TEST(SYM); this should give you the source
statement line in error, as well as a formatted dump of
all the datat items, on your CEEDUMP.
Alternatively, the CEEDUMP might have an offset into the
offending module and that should help you get back to the
source statement in error.
In more sophisticated bugs regarding storage, you might
look at John Monti's excellent SHARE presentations on
LE Debugging.
Kind regards,
-Steve Comstock
The Trainer's Friend, Inc.
303-393-8716
http://www.trainersfriend.com
z/OS Application development made easier
* Our classes include
+ How things work
+ Programming examples with realistic applications
+ Starter / skeleton code
+ Complete working programs
+ Useful utilities and subroutines
+ Tips and techniques
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
