|
Is there actually an upper limit of procedures to a module? Modules to a service program? Total procedures in a service program?
Every export from a service program is given a number -- that number is a 32-bit signed integer, so you'd never be able to have more than 2.1 billion exported subprocedures and/or data items. I don't know if there's anything else that imposes a limit or not.
And what is the correct analogy of a Java Class to an ILE construct? Is it Class is equivalent to Module? Or Class is equivalent to Service program?
It's not really a one-to-one relationship, since they don't work exactly the same way.
However, the closest analogy (my opinion, only) would be: Module = Class SrvPgm = JAR BndDir = compile-time CLASSPATHOf course, it all depends on how you use it. Without a class/object structure that the items in a module are a part of, you can really organize your code any way that you like. Personally, I like to group related functions, so I think of a module as being like a class. I think of a srvpgm as being like a collection of classes (a JAR)
I guess what I'm saying is that the relationship above is how *I* use it, and how I recommend using it. Anyone can come along and do it differently, it's just not what I recommend ;)
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.
midrange.com
