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


  • Subject: Design question re: SrvPgm Modules & Procedures
  • From: "Paul Jackson" <pauljackson@xxxxxxxxxxxxxxxx>
  • Date: Tue, 15 Feb 2000 21:39:49 -0800

Hello,

I will soon be writing a set of procedures to do Scrambling/Descrambling of
data. This will be available by two procedures Scramble & Unscramble which
will be able to be embedded within Eval statements.

Both Scramble & Unscramble will be calling Procedure A twice and Procedure B
once to do their necessary processing.

I plan to have all of these procedures in the same service program, let's
say srvpgm=SCRAMSRV

So within SCRAMSRV I will have the following procedures:

Scramble -- available outside srvpgm
Unscramble -- available outside srvpgm
ProcA
ProcB

My question is: Should I have these procedures in separate source members
and compile as separate modules or should I throw everything into one source
member?

Advantages/Disadvantages of either method?

I am fairly new to ILE and so could do with a few pointers here.

Thanks in advance for any advice.

-Paul Jackson 

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.