Wierd messages in ISDB

320 pts.
Tags:
ISDB
RPG
Hi, I have an elaborate program stream that starts with a CL which calls an RPG program that builds an OPNQRYF statement and selects records. After that, there are 9 RPG programs, one of which I’m trying to debug using ISDB. When I try to step through the RPG program, I receive a group of message that I do not understand like: ISDB stopped at statement *DETC in program P57697 */ ISDB stopped at statement 9000 in program P57697 */ ISDB stopped at statement .DRVRC06 in program P57697 */ ISDB stopped at statement 9100 in program P57697 */ ISDB stopped at statement 16300 in program P57697 */ ISDB stopped at statement *DETL in program P57697 */ ISDB stopped at statement *GETIN in program P57697 */ ISDB stopped at statement A000000 in program P57697 */ ISDB stopped at statement .FILESEL in program P57697 */ ISDB stopped at statement .DRPCSS in program P57697 */ ISDB stopped at statement *TOTC in program P57697 */ ISDB stopped at statement *TOTL in program P57697 */ ISDB stopped at statement *OFL in program P57697 */ These were retrieved from the joblog but when they occur, each one of these message appears in the message line at the bottom of the screen in the form; ‘Statement (whatever) was expected but not found” and the source is positioned to the top of the screen. Repeated pressing of the F5 key just causes another message to display and only after many repeat presses of the F5 key do I finally hit some code, but then they start over again. Some of these same messages appear every time a new record is read. I cannot begin to tell you how frustrating this is. I have read that a similar condition can occur when the program cycle has not been used and the initialization subroutine is involved. I am using the program cycle and not using the *INZSR. I begin the debugging session with the CL and then add the RPG I want to debug and then step through the CL without any messages. Only when I get to the RPG program do they start appearing. Any insight as to what causes this behavior or how to prevent it will be greatly, greatly appreciated.

Answer Wiki

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

Does the source match the compile program object? In other words, has the souce been changed after compilation?

No

Discuss This Question: 5  Replies

 
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
  • Gilly400
    Hi, I suspect it's because you're using the cycle. *DETC, *DETL, *GETIN etc are used by the cycle, but are not statements in your source code. By pressing F5 you step to the next executable instruction each time - many of which are generated by the cycle and are not in your source code. I suggest you use breakpoints in your program, you can add one from ISDB as soon as your source gets displayed. If you use the *INZSR there are also various instructions which get added to your program without having any source, so you would get a similar result. Regards, Martin Gilbert.
    23,730 pointsBadges:
    report
  • Sloopy
    Add breakpoints after the IO parts of your code and, when you get to a READ or CHAIN or whatever, just press the function key to run to the breakpoint, instead of the key to step through the code. Regards, Sloopy
    2,195 pointsBadges:
    report
  • Floyd02
    I appologize for the delay. I understand what you are saying but is there some underlying cause to this as I have never encountered it before and I have been writing CL controlled RPG program for some time?
    320 pointsBadges:
    report
  • Gilly400
    Hi, I would say the RPG program cycle is the cause - do you normally use it, or is this an exception? Regards, Martin Gilbert.
    23,730 pointsBadges:
    report
  • TomLiotta
    The first likely possibility is that the source found by the debugger does not match the compiled program. There might be many reasons for that. Keep in mind that the debugger might not think the correct source is the same as what you think. The next likely possibility -- STRISDB??? Are you serious? How old is your system? Hopefully, you're running a version 3 or early version 4 system. If not, I'd find it hard to trust anything it said nowadays. Quit using STRISDB and use STRDBG OPMSRC(*YES) at the very least. One of the other modern debuggers might even be better. At the very least, look up every possible PTF related to STRISDB and get them installed. (I wouldn't expect to find many -- IBM hasn't enhanced ISDB for years.) Finally, a couple statements don't quite seem to fit together: I have never encountered it before and I have been writing CL controlled RPG program for some time? ...and... When I try to step through the RPG program, I receive a group of message that I do not understand like: What is it about the statements that you don't understand? Anyone who knows RPG/400 and has been writing it for "some time" should have no problem understanding those messages. Tom
    125,585 pointsBadges:
    report

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