|
I've determined the breakpoint setting problem is across the board for me on all modules that don't happen to be the PEP module in a *PGM as well as all modules used in *SRVPGMs. I've even taken out the NOMAIN keyword on one and added a RETURN statement in the C-specs and it still won't set a breakpoint properly, even though STRDBG works fine on the module that is the PEP in the same program.
Since it only occurred when we upgraded and it is affecting all modules that contain procedures only, I have to assume it is a system wide problem. There is still two of those PTFs on the IBM site we haven't loaded yet, so I will try those next even though they were not intended for the same problem.
Thanks Rob, for your help and if anyone comes up with anything else, please let me know.
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 listProgram/module Library Type SRVPGM ROUTINES *SRVPGMSRVPGM *MODULENELSON ROB *PGM NELSON *MODULESet 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 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.