• Subject: Re: Procedures
  • From: "Wayne Achenbaum" <wache@xxxxxxxxxxx>
  • Date: Thu, 29 Jul 1999 13:55:37 -0400

Scott, I would suggest you do some reading on the differences in binding by
copy vs binding by reference and the ramifications on performance vs.
maintainability vs. disk usage.

1. Binding by Copy meaning every pgm that uses a module must include that
module on the module list on the crtpgm command which means all those
modules are copied in at create program time and become part of the the pgm
being created. This method means every time a module changes, all programs
must be recreated or an update program must be done to all pgms that use
this module.

2. Binding by reference meaning that a service pgm has been created from a
single or group of modules. When you want a pgm to access something that
resides inside that service pgm (a module or a procedure) on the crtpgm you
would include the service pgm. This is nice because changes are only done to
the service pgm. The pgms that have the service pgm bound to it do not have
to be recompiled (most of the time) as long as you dont change the
communication (parameters) between the *PGM and the entity within the
Service Program or the amount of modules or procedures that make up the
Service Program . Even if you add modules/procedures you can use binder
language to do your creating (CRTSRVPGM) therefore create a signature for
the generation of the service pgm to match with the pgm that was bound to.

 The answer to your question on module or bound pgm or service pgm is it
depends.

1. How many programs are going to use these procedure(s).  If the answer is
many then definitely create module(s). One or many modules depends on how
much flexibilty you want in maintaining these procedures. On the create
service program specify the module(s) that you want included in the service
program.

Note:

        1:  A Module can consist of one or more procedures
         2: A Service program can consist of one or more modules and or
service pgms
         3: A Program can consist of one or more modules and or service pgms

Hope this helps.
Wayne Achenbaum
Slomin's Inc.

----- Original Message -----
From: Scott Swaim <scott@qualitycorps.com>
To: <MIDRANGE-L@midrange.com>
Sent: Thursday, July 29, 1999 11:35 AM
Subject: Re: Procedures


> Maybe I did not make myself clear enough.  I have figured out how to writ
> the code for procedures.
> I don't know where to go from there.
>
> Do I create a module or bound program?
> do I need a Binding directory?
> How do I compile the module into the binding directory?
> Do I make it a service program?
> etc.
>
> Scott Swaim
> scott71@hpnc.com
> > Looking at other people's procedures is a big help. The technical
> > aspect of doing procedures is not really that difficult. I've learned
> > a lot about using procedures from others, not from the technical
> > aspect of how you code them, but rather from the creative side
> > of how you can use them. Look at some of the sites where you
> > can download code (e.g. Bob Cozzi's site or Brad Stone's site to
> > name a couple. I wonder if Jon Paris has a site with all of his code
> > examples?).
> >
> >
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---

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


This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2019 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 here. If you have questions about this, please contact [javascript protected email address].