|
We are thinking of compiling all of our programs with DBGVIEW *ALL. Currently our programs are compiled with DBGVIEW *NONE. DBGVIEW *ALL more than doubles the size of the object. Can someone explain what the different debug views do? I have a choice of *STMT, *SOURCE, *LIST, and *COPY. What we want is to be able to dump a program which has an execution error and view the contents of the fields, and to use IBM's source debugger without having to re-compile the program first. Also I'd like to know if there are performance issues associated with compiling with a debug view other than *NONE. Most of our programs are compiled with the CRTBNDRPG command. -- ___________________________________________________________ Jerry R. Keppler Pattonville School District Computer Programmer 11097 St. Charles Rock Road (314) 213-8045 Voice St. Ann, MO 63074-1509 (314) 213-8650 Fax mailto:kepplerj@pattonville.k12.mo.us +--- | 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 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.