|
Ellen, Why use a binding directory? If you know the modules and service programs that a program or service program references, it is not necessary to use a binding directory. Like you, we maintain relations between objects in a file and at this point we have a single binding directory with a single entry. This binding directory was only necessary because one procedure, that is used by several programs, must be bound by copy. Based on the information in the cross reference files we build the CRTPGM or CRTSRVPGM command string. Another parameter that makes the whole job easier is the ALWLIBUPD of the CRTSRVPGM. This parameter helps when there are circular references between service program being moved to production. David Morris >>> Ellen ter Hazeborg <hazeborg@conne.net> 02/02 10:23 AM >>> We do not develop programs for other companies, we only develop them for our company. If we want to make a change, eg. adding a field to a file, we have to do this during the night because most of the users are at home at that time. But we do not like working at night very much and therefore we have written some tools to make such changes without being online. These tools use several files which store information about database relation, program relations and, very important, the relation between source and object. This information we get by using DSPPGMREF and DSPPGM etc. But we do not get any information about how a program with a module has to be compiled ! For that reason we want to get the bind directory to do the compilation. I hope I could explain the reasons (English is not my mother tongue as you already have guessed). Cheers, Ellen * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. Questions should * * be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
As an Amazon Associate we earn from qualifying purchases.
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.