Re: Problem with non QUALIFIED DS

[Alan Campin <alan0307d@xxxxxxxxx>]

Don't see where this deals with multiple modules in one service program.

What I do is

XVDYNL         = Top level binding instructions.
XVDYNL_M01 = Module one.
XVDYNL_M02 = Module two.
XVDYNL_B     = Bindary
XVDYNL_PR   = Prototype

XV means system utility.

So you can have up to 99 modules in a service program and modules can be of
any type. RPGLE, CLLE, CBLLE, etc.

All procedures are prefixed with the service program id
DYNL_LoadServiceProgram for example to provide uniqueness.

I also use a single source file QSRCF so that when I display XVDYNL* in a
PDM I get all the pieces.

On Wed, Sep 23, 2009 at 10:25 AM, Lim Hock-Chai <
Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote:

> 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?
>
>
>
>
>
> ----------
> --
> This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.