Comments on: Wierd messages in ISDB

By: tomliotta

tomliotta — Thu, 12 Aug 2010 07:06:52 +0000

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

By: gilly400

gilly400 — Mon, 13 Oct 2008 11:33:53 +0000

Hi,

I would say the RPG program cycle is the cause – do you normally use it, or is this an exception?

Regards,

Martin Gilbert.

By: floyd02

floyd02 — Fri, 10 Oct 2008 19:31:28 +0000

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?

By: sloopy

sloopy — Wed, 08 Oct 2008 14:49:13 +0000

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

By: gilly400

gilly400 — Tue, 07 Oct 2008 15:42:56 +0000

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.