× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



As a final note, in case anyone else has this problem, PTF SI18282 fixed the breakpoint problem.

Nelson Smith wrote:

Rob,

Further testing has isolated the problem down to modules containing procedures with a /copy inside the procedure itself. /copy's in the main D-specs don't cause a problem. Unfortunately, all my procedures have a standard PSSR subroutine in them that is /copied in. Astericking those out provides a clunky work-a-round. This problem did not exist at V5R2. And, I did load all 5 PTF's you mentioned earlier.

Before I start haranguing IBM, Could you check and see if you have any procedures with a /copy in them and if so, do the breakpoints set ok on those modules? Or perhaps, just add a /copy of some source code into the test sample below. Thanks for your help.

rob@xxxxxxxxx wrote:

I created a simple program that utilized a subprocedure from a service program.
Then I did STRDBG PGM(NELSON) UPDPROD(*YES)
F14=Work with module list
Program/module Library Type SRVPGM ROUTINES *SRVPGM
  SRVPGM                         *MODULE
NELSON ROB *PGM NELSON *MODULE
Set a breakpoint in SRVPGM here
370       C     WorkDate      SubDur    AnySunday     WorkNum:*D
Which is the first C spec in the subprocedure
CALL NELSON
And I think it was this line it first stopped on
358       P     DayOfWeek   B                   EXPORT
Then I did
F10=Step
and it went to the breakpoint.

Rob Berendt



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.