× 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.



For the small service programs I had with about 25 procedures
total in one service program I added all 3 of my modules, in the
other I added 2.  The 3rd module was specific to a certain
application, the other 2 were generic.

So, I had modules:
DATETIME (Date/Time routines)
SYSTEM   (System API call interfaces)
CARTAGE  (Specific to the Cartage application)

Service program CARTAGE contained all 3 modules.
Service program GENERAL contained DATETIME and CARTAGE.

So if I was writing a Cartage program I would use the CARTAGE
service program.  If I was writing any other program, I would
use the GENERAL service program.

I am not sure if this is the proper way to do it, but I felt it
was the best at the time.

Regards,

Jim Langston
Programmer/Analyst
Cels Enterprises, Inc.

-----Original Message-----
From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
Behalf Of Bill Meecham
Sent: Tuesday, August 28, 2001 12:49 PM
To: RPG400-L@midrange.com
Subject: Procedure Management Procedures


This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Hello All -
In an ILE environment what are you folks doing to manage the procedures that 
you have created?  Do you keep all of your procedures
in 1 service program?  How do you track the names and what they do, with notes 
in the prototype file?  Are you using modules as well
as procedures in programs?  Are you using modules in procedures?
I'd just like to get an idea of how folks are managing these things and what 
some of the development environment models are like.
Thank you!
Bill M



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.