Re: Identifying where *modules are used

Al - yes - I'm promoting the use of /copybooks as a new standard. Mostly
for global constants, H specs, and PR specs. We've had a few others in
place for awhile but now I'm trying to expand their use.

Nick - thanks for the code sample - I'll give that a whirl.

Charles - I agree - we'd have been better off not using CALLB, but its use
started before I arrived here and was a standard practice until about 2
years ago when I started pointing out that this practice has been
discouraged for some time. And I've also pointed out to the staff the
redundancy of having modules bound into multiple programs. In one case we
have a small function that converts ISO dates to USA format and
vice-versa, and I found it was bound into over 300 programs! Can you say
service program???? So yes - that is on my radar too.

Scott - thanks for clarifying. I actually learned A LOT about how to
implement true ILE functionality from your Socket program tutorials and
your IFS handling routines. Now I'm using that experience to promote the
same principles for development and ongoing maintenance of our custom
code. (And thanks for the timely article about naming conventions in this
months System i News.) I also understand your comment too about making
routines available as web services, stored procedures & sql functions (and
thanks again Charles (Wilt) for setting me straight a week or two ago when
creating my first UDF).

I truly appreciate all your responses.

Regards, Jerry

Gerald Kern - MIS Project Leader
Lotus Notes/Domino Administrator
IBM Certified RPG IV Developer
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx


This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential and privileged
information. Any unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please inform the
sender by reply e-mail and destroy this and all copies of this message.