Re: Using prototypes...

I know this is not directly the subject, but I have always
wondered why people has different sourcefiles for different
source types.

Yes it only takes about 5 sec to go up and change the
sourcefile name and reposition in the new sourcefile, but
because you do it so frequently, yoo have probably had done
it more that 100.000 times wich equals +150 hours of doing
absolutly nothing productive ;-)

I have only two sourcefiles a QDDSSRC to DB2 definitions
and a QSRC for the rest and all source is grouped by a
4-8 character prefix and the sourcefiles resides in the
same lib as the objects they correspond.

Programs are organized as ...

PXGENDB2 RPGLE powerEXT: DB2 RPC Generator BASIC
PXGENDB2CL CLLE powerEXT: DB2 RPC Generator BASIC
PXGENDB2CM CMD powerEXT: DB2 RPC Generator BASIC
PXGENDB2PX CLLE powerEXT: Create All PX-DB2 RPC into PEXTCGI
PXGENDB2T SQLRPGLE powerEXT: DB2 RPC Generator BASIC Template
PXGENDB2TR RPGLE powerEXT: DB2 Default trigger

Libraries are organised as ...

E600DTASDV USR ALLIGATOR DB2 Database - Customer Name
E600LIBSDV USR ALLIGATOR Modified Pgms - Customer Name
E600STD USR ALLIGATOR Financials Ver. 7.0
W600DTASDV USR Way2Trade DB2 Database - Customer Name
W600LIBSDV USR Way2Trade Cgi Programs - Customer Name
W600TMP USR Way2Trade Temporary Work Files
PEXTDTASDV USR powerEXT DB2 Database - Customer Name
PEXTAFW USR powerEXT Application Framework 1.1
PEXTCD2 USR powerEXT Core 1.5 - CGIDEV2 Version
S600DTASDV USR Way2Trade DB2 Database - Customer Name
S600STD USR Way2Trade Application Framework Build
S600EDI USR Way2Trade XML/EDIFACT API Library 15.0

"SDV" represents a "systemID" and is just a parameter, there could be
a "TST" for a test environment ect.

Standard libraries can also be changed by adding a suffix, S600STD
could be S600STDNEW in one setup so I'm able to run quite a diffent
setup and many customer at the same system.

And because the sourcefiles always follows the object library nobody
can question where the source is.

Regards
Henrik




Simon Coulter <shc@xxxxxxxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
07-05-2010 15:36
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>


To
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: Using prototypes...







On 07/05/2010, at 10:21 PM, Robert Rogerson wrote:

My question is, is this normal practice or shouldn't the prototypes
file be
in the modified_source library and the library list in the COMPILES
JOBD be
changed to add modified_source as the last library list entry?

To me, prototypes (and other include files) are source and should
therefore be in the source library--in a file with a sensible name
such as RPGLEINC.

If for some reason you cannot add the source library to the compile
job description then qualify the location on the /COPY directive.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------