|
> One global binding directory. One module per service program, > named the same as the service program and using *Caller. > Everything is extremely simple to implement, maintain, and use. I have yet to > have any problems with doing it this way. The question was, why do it differently? How about security for one thing. Regarding service programs always running *Caller - that's my typical suggestion, but there are reasons not to. Depending on design, it might be advisable to use named AG for cleanup reasons. It's a must when using JNI to allow Java programs to call procedures in RPG service programs because the Java runs in the default activation group and you must end job to cleanup that up. One module per zervice program - hard to do when you have RPG and CL (one example) code you want to include in a service program. I'll stop for now! Gary Guthrie
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
