Debugging *Srvpgm in V5R3 with STRDBG

5 pts.
Tags:
Development
We just upgraded to V5R3 and suddenly I'm having problems trying to set breakpoints in RPG module source used in service programs. It sets breakpoints ok, just in the wrong places. Seems like the source and object are mismatched. Is this a known issue at V5R3 that I need to get a PTF for or should I keep looking for a problem in my own code? These were working service programs in V5R2. I am currently recompiling in V5R3 to TGTRLS(*PRV) on both the service programs and the programs that call the procedures in the service program. They were previously compiled at *CURRENT (when we were on V5R2). The reason we are compiling to *PRV now is that not all our production machines are at V5R3 yet.
ASKED: July 14, 2005  1:34 PM
UPDATED: July 15, 2005  9:44 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

This is just an off-the-top-of-my-head-guess(TM) but could it be that the source display has been changed somehow? The dspmodsrc can show different views of the code including straight source and compiled. Maybe the default changed.

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following