Might be a bug.  I noticed that behavior and it seems like the debug
still points to the old version of the service program loaded within
job's resources.  
Try signing off and on and see what happens.

Elvis

-----Original Message-----
From: c400-l-bounces@xxxxxxxxxxxx [mailto:c400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Doc
Sent: Wednesday, March 12, 2003 5:59 PM
To: C400-L@xxxxxxxxxxxx
Subject: [C400-L] Compile options to enable Debugger on V5R1

Hey All

I've got an ILE RPG program that calls service program.  The service 
program is composed of one module, written in ILE C.

I compile the C module with the usual CRTCMOD DBGVIEW(*ALL), and then do

the CRTSRVPGM command.  All's fine.

I compile the RPGLE program with CRTRPGMOD DBGVIEW(*ALL), and then do a 
CRTPGM command, binding to the service program.  All's fine.

I start the debugger on the RPG program, and set a breakpoint where I 
want to call the C function.  All's fine.

I call the RPGLE program.  The breakpoint trips, and I see the RPGLE 
program displayed.  I press F22 to drill into the service program, and 
the debugger tells me source is unavailable.

How does THAT happen?  The ILE C module information in DSPSRVPGM shows 
DBGVIEW(*ALL).

Any ideas?

Thanks!

-Doc


_______________________________________________
This is the C programming iSeries / AS400 (C400-L) mailing list
To post a message email: C400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/c400-l
or email: C400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/c400-l.





This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2019 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 here. If you have questions about this, please contact [javascript protected email address].