Re: Procedures/SubProcedures

["Joe Teff" <joeteff@xxxxxxxxxxxxx>]

>> The only difference I see is where they are located. Seems like
>> splitting hairs. All procedures residing in the same source member
>> have access to the global variables in that module (srcmbr).

>Subprocedures cannot have H, F or O specs that I know of, which a slightly
>larger difference than a hair <G>.


So you must be defining the mainline as a procedure and then any other
procedures  as subprocedures. That is not what I understood the original
post as. He was questioning why the two names were being used
interchangeably. In my experience, they are interchangeable. Maybe the
correct definition for a procedure is the main procedure and all others
are subprocedures. Nobody that I know uses this definition. If hear
either procedure or subprocedure, they are referring to the same thing.

In my response, I was guessing that he was trying to distinguish the
location of the subprocedure based on whether it resided in the same
module as the main module or in a bound module (either 'bound by
copy' or 'bound by reference'). They cannot have their own H, F or O
specs regardless if they are in the main module or in a bound module.

Joe Teff

+---
| 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
+---