|
Hi Nelson, I am working on V5R3 1) I had created a main module "PGMMOD1" DNum1 S 4 0 INZ(700) DNum2 S 4 0 INZ(800) DProc1 Pr DNum1 4 0 DNum2 4 0 C CALLP Proc1(Num1 :Num2) C Eval *inlr = *on 2) I had created a Sub-module "MOD1" HNomain DProc1 Pr DNum1 4 0 DNum2 4 0 * PProc1 B Export DProc1 PI DNum1 4 0 DNum2 4 0 C Eval Num1 = Num1 + Num2 C Num1 Dsply C Return PProc1 E 3) I had compiled both the main module "PGMMOD1" and sub-module ""MOD1" With Compiler options "*DEBUGIO" and Debugging views "*Source" 4) I had created a Service program "SRVPGM1" with module "MOD1" CRTSRVPGM SRVPGM(HSCDC09/SRVPGM1) MODULE(MOD1) EXPORT(*ALL) SRCFILE(HSCDC09/SOURCE) 5) I had created a program with the same name as main module "PGMMOD1" CRTPGM PGM(PGMMOD1) MODULE(PGMMOD1) BNDSRVPGM(HSCDC09/SRVPGM1) 6) STRDBG , then I added break points to the main module "PGMMOD1" Then STRDBG PGM(PGMMOD1) UPDPROD(*YES) 7) The F14 = Module list , added Service program as shown below Opt Program/module Library Type SRVPGM1 *LIBL *SRVPGM SRVPGM1 HSCDC09 *SRVPGM MOD1 *MODULE PGMMOD1 HSCDC09 *PGM PGMMOD1 *MODULE Selected 8) Now selected Option = 5 for "Mod1" and could able to add break points To this module "MOD1" 9) F3 from the debugging mode and then called the main program Call PGMMOD1 , I am at my break point that was specified earlier and could able to start debugging. Thanks Sadiq ... -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Nelson Smith Sent: Saturday, July 16, 2005 5:11 AM To: RPG programming on the AS400 / iSeries Subject: Re: Debugging problem at V5R3 OK, if it works for you then it must be something unique to my machine. I can't even set that initial breakpoint, much less run the program to it. That's the main thing I wanted to confirm before going to IBM with this. I was hoping someone else had already run into this issue. I can't think of anything unique about our system that would cause it to work differently than anyone else's that have been on V5R3 for awhile. 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 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 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.