|
Likely you already tried stepping through the code in debug, but if not, this may tell you where the situation is. Queries are really big time hogs, if there are queries involved you might look there, and that includes embedded SQL. What often works for me also is to let the program run in one job, and use the WRKJOB on that one from another job, and select the view for the program stack. Then watch the statement numbers and f10 through it to refresh the stack display. This will often give you a really strong hint as to the problem, from which system names are running, etc. --Alan
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.