|
Is there a limit on the line# for a breakpoint in STRDBG? I have a
coworker trying to set a breakpoint on 11729 (I know the program is huge!)
and it jumps to the o-specs and sets the breakpoint there. Through trial
and error, they found that up to line 9999 worked. I verified the source
matches the program. This happens when you use the "RPG listing" view too.
I was able to set a breakpoint in another large program at a line > 9999
successfully. This happened to be in a subprocedure so it made me try a
subprocedure in that first program. When I do that it sets the breakpoint
at the end of the subprocedure (closing p-spec) instead of the line I want.
Any ideas?
--
Brian J. Garland
Vermont Information Processing, Inc.
brian.garland@xxxxxxxxxx
--
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or company to whom they are
addressed.
Do not disclose, distribute, or copy this email to others outside your
company. If you have received this email in error, please notify the
sender
immediately and delete this email from your system.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.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.