CL Module Question.

A little while ago I had cause to use the CALLPRC command in a CL
program. Simon Coulter (bless his little white socks), pointed me in the
right direction with regards to a variable length parameter set up from
the CL to the ILE procedure interface. Now I have a CL module and I am
able to create a program out of it(CRTPGM) or CRTBNDCL directly from the
module source.
I'm now curious about the differences between RPG & CL modules.

An RPG module may have one or more procedures, but the CL module doesn't
seem to fit the RPG procedure template - no prototype, no internal
procedure declarations. So the question is - what can I do with a CL
module other than create a module? I have to create a module because of
the reference to CALLPRC, but is there any other intrinsic reason for
using CL as a module?

I thought I might be able to reference it from a CALLPRC in another CL,
but since there's no 'procedure' construct, what else can I do with it? 

While I'm at it:

If the entire module is copied into a referencing module/program/service
program, then there seems to be a propensity to possibly create very
large programs by the time an executable is created as the tip of a
possibly very large pyramid of module references. 

It almost seems as if the best solution is to use a service program in
almost all instances, regardless of the slight overhead of the initial
reference.

Mike Pantzopoulos

EIG-Ansvar Limited
Tel  : 61 (3) 8630 3193
Fax:


*********************************************************************************************************
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you are not the intended recipient, any use, disclosure or copying of this 
message is unauthorised. If you have received this message in error, please 
reply using the sender's email address. 

This footnote confirms that this email message has been scanned for computer 
viruses. EIG-Ansvar Limited does not accept liability for any loss or damage, 
whether caused by our own negligence or not, that results from a computer virus 
or defect in the transmission of this email or any attached file. 

EIG-Ansvar Limited - Australia (A.B.N. 21 007 216 506)
Email : insure@xxxxxxxxxxxxxxxx

Eig-Ansvar Limited - New Zealand
Email : insure@xxxxxxxxxxxxxxxx

*********************************************************************************************************