|
>In my mind, I imagine ILE to be a four tiered hierarchy: > >Binding Directory (one or many) has > Service Program (one or many) has > Module (one or many) has > Function (one or many) > >I realize that more arrangements can be made than >this, but this seems principally how I can see it working. Your description is fine. Bear in mind that the run time requirements should drive the service program activation group attribute. >Right now, my biggest issue with the whole deal >comes down to managing the service programs. I want to clearly state that the following is strictly my own opinion, and may not represent best practise. If you need more than 5 or 6 service programs I'd be surprised. In a very large application you might make it to a dozen or so. >A 'make' utility might go a long way towards >making the system work efficiently. I haven't looked at it in ages, but there is a MAKE tool in IBM's QUSRTOOL. It requires C, but if you're on V5 you are entitled to a no extra charge C license. --buck
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.