I am taking it upon myself to break in to the world of ILE programming.
In setting up source members that contain

all of my procedures, I was wondering about what standards you all use.
I want to avoid (of course) having the same

procedures ending up in different source members without noticing it.
For example, many programs would access

our customer file. Do you base your source members on what files the
procedures use? Say, one source member

of procedures for each file? Or do you just build them on what the
application will need. I'd like to determine a good

standard operating procedure before things get out of control. Thanks
for any suggestions.



























Bob Ostrowski | Senior Programmer/Analyst

TRAINOR GLASS COMPANY | National - IT

760 Indiana Highway 212 E, Michigan City, IN 46360

T 708.293.4218 | F 708.293.6218 | C 708.560.5813

bob.ostrowski@xxxxxxxxxxxxxxxx <mailto:bob.ostrowski@xxxxxxxxxxxxxxxx>
| www.trainorglass.com <http://www.trainorglass.com>




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.