Re: Subprocedure Question

what i would do (i did it) is :
for each file :    1 source RPG with all procedures, and one exported DS
(like filename)
                        1 source for /copy PI
                        create one service PGM by module
                        Add the *SRVPGM to a single bnddir
In each pgm that use a file :
                        Add the BNDDIR at "H" spec.
                        Add the /copy for PI
                        If i want data, add an external DS, imported (from
the service pgm) qualified

You may want a convention name :

    Myfile         is the file
    Io_Myfile    is the EDS name

    Myfile.field1 ... are the fileds name

    Procedure names :
        Read_Myfile, Delete_MyFile, Create_Myfile....

    It will make all procedure, ds unique.

Hope this help.



----- Original Message ----- 
From: "Wall, Isa (ED)" <IWall@xxxxxxxxxxxxxxxxxxxx>
To: <rpg400-l@xxxxxxxxxxxx>
Sent: Thursday, September 01, 2005 4:04 PM
Subject: Subprocedure Question


I would like to ask your option on the following subject.  I am planning
on implementing subprocedures for all file actions.  For example, if you
want to read, setll, open, update or write a record to a file you would
call a subprocedure.  I am planning on creating a module for each file.
Inside each module I would create all subprocedures related to that file
and logicals.  My question is the next step which I don't know what is
my best action.  I now have a module for each file do I create a binding
directory for all the modules.  To me this does not make sense as we
have thousands of file in our system.  So do I create a service program
for each module and at compile time bind them as I need them?  Is there
another way I can do this?  What is the best to handle this?

Thanks.


Isa Wall
Programming Manager
Everglades <http://www.gneil.com/>  Direct, Inc.
720 International Parkway
Sunrise, FL 33325
* 954-514-2259
* 954-851-1201 Fax
* iwall@xxxxxxxxxxxxxxxxxxxx