Re: ILE - module overwiew?

[Jim Essinger <esinger@xxxxxxxx>]

Greetings;

I find it easiest to use the binding directory for a program or a project 
(system) that contains the names of all the modules and where they can  be 
found.  Then on the compile (CRTBNDCBL) or the create program command, list 
the binding directory.  The compiler looks into the directory to resolve 
all the links for the program to the modules it calls.  I have created CL 
programs to compile all of the modules, then run the create program, 
essentially recreating everything for program or system.  Sometimes that is 
easier than trying to do it manually.  Depends on the complexity of the 
program/system.

Hope this helps

Jim Essinger
Senior Programmer/Analyst
Student Loan Fund of Idaho
esinger@fmtc.com
208-452-4058

At 10:10 AM 7/26/2001 +0200, you wrote:

>Hello.
>
>I'm still working my way into ILE:   In the OPM-world, all nessecary kode 
>for a program is kept in the source member(except copys), and compiling 
>the source gives you a runnable program.  The program overwiew is kept in 
>the source files.
>
>In the ILE-world, a program can be put together from several modules(each 
>module has its own sourcecode).  Then I come to my question:  What is the 
>best way of keeping track of which modules goes into which programs?  This 
>can  obviously be a big problem unless it is kept in some code 
>somewhere(CL-pgms keeping the info???)
>
>What is common practice/wise to do?
>
>
>Mvh.
>
>Geir Kildal

+---
| This is the COBOL/400 Mailing List!
| To submit a new message, send your mail to COBOL400-L@midrange.com.
| To subscribe to this list send email to COBOL400-L-SUB@midrange.com.
| To unsubscribe from this list send email to COBOL400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---END