Re: CPF7E56 - Identifier is ambiguous

Hi Matt -

Why does the IBM debugger give this message for a non-qualified field
(Identifier is ambiguous)?

The field VITEMID is defined in three files.
FVNDRCOST  IP   E           K DISK
FVNDRMASTERIF   E           K DISK    PREFIX(VM)
FVNDRITEM  IF   E           K DISK    PREFIX('VI.')

Here's the definition for making one field qualified.
D VI            E DS                  EXTNAME(VNDRITEM) QUALIFIED

I try to view the contents of field VITEMID from VNDRCOST (not qualified nor
prefixed).

How do I tell the debugger to view this field without making modifications
to the program to only prefix without the dot (.)?

Sorry for the delay. I've been on vacation and even though I read the message, I wanted to try one thing out at work today before responding.

I'm sending this to the RPG400 list as well since it is specific to RPG IV debugging and since I would like some additional input from Barbara Morris.

Essentially the same question arose on the RPG400 list last week.

The answer is that if you are referencing a field with two instances, to see it in debug you must qualify it, even to reference a field in an unqualified data structure. You do this with:

eval [field] of [datastructure]

According to Barbara, on V5R2 and following you can also do it with:

eval [datastructure].[field]

So far, so good. The only thing I can't find a way to do, and this is where I would like some more input from Barbara ...

You can have a standalone field with the same name as a field in a qualified data structure. You can view/change the data structure field using the methods given above.

Barbara, how can you view/change the standalone field? There is no data structure name to associate it with. Or is V5R2 smart enough to let you view/change the standalone field with just: eval [field]
V5R1 won't let you do this.

Ken
http://www.ke9nr.net/
Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind.