Re: Service programs: navigation

I will echo the point about naming conventions that include product and
application groupings. We use separate libraries for products, and separate
source files for application groupings. Our member names follow a naming
convention too that identifies the product and application.

In addition, you begin to accumulate "framework" functions for things like:

inter-process communications (i.e. data queues, message queues, shared
memory, sockets, HTTP services, etc.)
stream-file and directory apis.
string apis (uppercase, lowercase, etc.).
communications with browsers (forms, cookies, query-string parameters,
environment variables, etc.).
communications with Twilio.
communications with Google web services.
encoding (base64, encryption, etc.).
data-type validations (integers, dates, times, time-stamps, etc.).
SQL cursor apis.
data-conversion apis.
date apis.
edit-code apis.
email apis.
JSON apis.
linked-list apis.
message apis.
authority-checking apis.
EDI apis.
etc.




On Tue, May 16, 2017 at 12:51 PM, Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx>
wrote:

How is the inventory of Service Program functions documented? How does a
programmer navigate through the dozens of service programs and find the one
that is exactly right?

1. Good Naming Conventions
2. Group the procedures according their functionality into Modules/Members
3. Include the member name in the procedure/function name e.g.
ItemNo_GetDescription, DateTime_CvtNumToDate etc.
4. Include a description for each Procedure and Prototype
5. Group the prototypes in an different source file in members with the
same
name as the Module/Service Program
6. I've written UDTFs based on the QBNL... APIs with which I can search for
the members

BTW these UDTFs can be used for free - if you download and install our
WOPiXX Tool http://www.wopixx.com/en
Even if you won't use WOPiXX for your web development you can use the UDTFs
and in the administration tool there are already programs for searching
Modules/ServicePrograms and Programs)

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
„Train people well enough so they can leave, treat them well enough so they
don't want to.“ (Richard Branson)


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Booth
Martin
Sent: Dienstag, 16. Mai 2017 19:45
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Service programs: navigation

This leads to another point that has bothered me. How is the inventory of
Service Program functions documented? How does a programmer navigate
through the dozens of service programs and find the one that is exactly
right? Or, not finding one exactly right, does s/he write a new one,
modify
an existing one, or copy and change an existing one? In early days that
would seem like not much of a task, but after 8 years and 15 different
programmers involved, it must become a bird's nest?


On 5/16/2017 9:17 AM, Bradley Stone wrote:

Or this to really confuse some;)
useLargeTrailer = (ibeamWeight(material: length: width: height:
webThickness:flangeThickness) > smallTrailerWeightLimit);

I prefer this but it can make debugging a little hard (even with your
example) since you won't ever see the value ibeamWeight() returns.

Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any
Cloud Provider!

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link:
http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD