×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 12/01/2010, at 10:34 PM, Larry Ducie wrote:
A Person 'object' is implemented in three SRVPGMS.
Curious. Why? Surely a given object should be implemented in a single
service program--at least from the point of the consumer? The PERSON
service program may use other service programs (e.g., ADDRESS, ENTITY,
etc.) but that shouldn't affect the consumer.
Seems to me your binding issue could be solved by having a single
PUBLIC binding directory which contains all your "object" service
programs. This is referenced by your consumers so they can resolve to
all 'objects' and 'methods'.
For development you would either:
o not use binding directories but rather list the modules and service
programs in the creation script (I'm presuming you use some form of
Change Management System to perform your builds)
o or use binding directories only for modules (one per service
program). You would still list the service programs directly.
You'd still have to edit the build scripts if you split a service
program but it's easier to search scripts (i.e., source) than binding
directories. If you frequently have to split service programs (i.e.,
objects) then you don't have your design correct.
I'm not suggesting that nested binding directories wouldn't be a good
thing (although cyclic references could prove problematic) but rather
that I think it's not required.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
As an Amazon Associate we earn from qualifying purchases.