Re: Problem with non QUALIFIED DS

David,
My advice: Sit down with your folks and create a standard for your shop
SOON or you will end up with a mess.

I do this in our shop:
- All service program name should always start with SV follow by a 2 to
5 chars code of the application.
==> For example SVCC is our Credit card service program.

- Copy book for the service program should always be the service program
name + CPY.
==> For example SVCCCPY

- All the reference fields used in the protoype should always included
in the copy book and always start with the 2 to 5 chars code + Reffeld +
field name. This field will always have the based keyword and always
qualified if it is a DS.
==> For example:
D*---------------------------------------------------------------------
D* for reference only
D*---------------------------------------------------------------------
D ccReffldCVV2 s 4A based(ccReffld_p)
D ccReffldDSCCTA...
D e ds extname(DSCCTA) qualified
D based(ccReffld_p)





"David FOXWELL" <David.FOXWELL@xxxxxxxxx> wrote in message
news:<mailman.3487.1253716071.1811.rpg400-l@xxxxxxxxxxxx>...
Hi,

I've just added a prototype via a copybook in my module and it won't
compile because it now has several fields defined more than once.

I discover that I now have 2 prototypes copied in, each one with a data
structure parameter declared like so :

D Parm likeds (myds)
D MyDS E DS extname( myfile)

Several field names exist in both the external files. Each time, the
person that wrote the prototype did not qualify the DS.

Also, the DS MyDS is being fed in the procedure by reference to the
field name then MyDS is copied to the parameter :

MyField ='Agatha'
Parm = MyDS

where MyField is declared in the DDS of myFile.


It would seem that I must modify the source of at least one of the
modules using qualified names. I thought, if I just put QUALIFIED after
the MyDS declaration, the source would no longer recompile and I would
instantly find the names of the zones to qualify. This is not so.
However, I'm presuming that now MyDS stays empty.

Any thoughts on this? I'm not looking forward to taking time out to
correct this, test it, etc. Maybe there's a work around?





----------