ILE debugger and qualified field names

[GlenKerner]

If I read the code right you are defining "field" to be like "field" maybe you are using the wrong field name in the "like" definition. Your example has both defined at the same field

[D.Handy]

Doc, You didn't say what release you are on. Prior to V5R1, you have to use the syntax "EVAL field OF ds", ie eval field of frog. I've heard that V5R2 allows the more intuitive format eval frog.field Doug

[john@thejoiners.net]

Doc - glad I'm not the only one experiencing this problem. I've scoured the 'V5R1 (and V5R2) RPG Programmers Guide - Part 3 Debugging and Exception Handling' multiple times trying to find the answer to this question - but always come away with nothing. As you probably already know, you can view the contents of a DS subfield by qualifying the EVAL (ex. EVAL Field1 OF DataStrucuture1), but how to qualify the EVAL on a standalone field? Grasping at straws, I've tried qualifying the field to the procedure (EVAL StandAloneField1 of Procedure1), MODULE, and PROGRAM, but no luck. I'm thinking this is something the IBM debugger team forgot about when they added support for qualified data structures. Or perhaps this is a subliminal message from IBM that we should start using their PC-based source debugger? I would sure like to know the answer to this if you get it. Drop me a line at john@thejoiners.net and let me know. JJ

[R.Cozzi]

ALthough I don't have access to V5R2, you might try using the Debugger's built-in function to access the stand-alone field. EVAL %VAR(field) This works particularly well when the field name is also a Debugger command. For example, if you have a field named QUAL, simply press F11 on QUAL or entering "EVAL QUAL" will fail with a syntax error. But, typing in: EVAL %VAR(qual) Works just fine.

[Guest.Visitor]

Well, after reading everyone's replies (thanks for taking the time to read and write, all), here's what I've got: Glen Kerner - 12:02pm JAN 21, 2003 pst (1.)

If I read the code right you are defining "field" to be like "field" maybe you are using the wrong field name in the "like" definition. Your example has both defined at the same field

I thought about that, but I don't think this is the problem-- the idea with the qualified field is to allow the same variable name to be used multiple times in different data structures to avoid naming conflicts. Bob Cozzi - 08:58am JAN 22, 2003 pst

ALthough I don't have access to V5R2, you might try using the >Debugger's built-in function to access the stand-alone field.

EVAL %VAR(field)

Went that route too. Got the "Identifier is ambiguous" message once again. So, no dice. john34 - 07:43am JAN 22, 2003:

Or perhaps this is a subliminal message from IBM that we should start using their PC-based source debugger?

I sure hope not. Code/400 gives me the ache. Knowing full well that last statement will likely cause a holy war, I'm moving to Brazil or Trenton, NJ. Thanks again everyone. If I figure it out I'll let you know. -Doc

[Guest.Visitor]

But not from me. In today's Tech Tips newsletter from iSeriesNetwork.com (formerly News/400): 2. QUALIFIED DATA STRUCTURES AND THE DEBUGGER Q: When debugging an RPG program, how can I display the values of a qualified data structure's subfields? I can display the entire data structure, but I can't find a way to display individual subfields. A: With V5R2, you can use the following: Eval DataStructureName.SubfieldName Prior to V5R2, you can use this: Eval SubfieldName of DataStructureName Thanks to Barbara Morris for sharing this information. So, for those of us in V5R1 and older, we have a bit more typing to do. Thanks all. -Doc

[john@thejoiners.net]

But this still doesn't solve the problem with displaying standalone fields that the debugger deems "Ambiguous", because you have nothing to qualify them with. Very frustrating :-( JJ

[Guest.Visitor]

Can you put the cursor on the stand alone "field" and get the content? And secondly, have you posed this to iSeries Network guru Gary Gunther? I'd be interested in the anwer he might have. Beyond him, I don't know of another person, except RPG Development, who might have the answer.

[B.Morris]

john34 wrote: > > But this still doesn't solve the problem with displaying standalone fields that the debugger deems "Ambiguous", because you have nothing to qualify them with. > > Very frustrating :-( > JJ, the problem is fixed in V5R2 by changes made to both the RPG compiler and debugger. For V5R1, try defining the standalone field as a subfield of an unqualified data structure. You wouldn't have to change any of the code that uses the field, but the debugger allows you to say ===> EVAL X OF Y even if Y is not qualified.

[Guest.Visitor]

Hey all I've got a mickey mouse example of code. Go look. I'll wait. The code compiles just fine. And when I pitch it into the debugger, I can examine the contents of the field result, and the subfields, frog.field and frog.field2. I can also examine the entire frog data structure. However, if I try to do an eval on the standalone field called "field", I get the error message, CPF7E56, Identifier is ambiguous, which does make sense-- but how do I qualify a stand-alone field so's I can look at it in the debugger? Thanks -Doc

---

Code