RE: CRTSRVPGM

Hi,

EXPORT(*SRCFILE) or better the binder source file is not just for manageing which procedure are accessible from the outside but also manages the signature (which is valueable if you don't want to compile everything because a procedure has been added)

If your service program is made up of several modules and you want a procedure to be accessable by these modules, you would "export" this procedure. But perhaps you don't want this procedure to be accessable to the outside world then you don't add an export entry for this one in the binder source file. By this way it is accessible inside the service program but not accessible from the outside.

Regards

Mihael

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Tuesday, December 14, 2010 2:12 PM
To: Midrange Systems Technical Discussion
Subject: CRTSRVPGM

Hi,
On the commande CRTSRVPGM our default settings are EXPORT(*SRCFILE). I know that using a *SRCFILE will enable me to restrict the use of certain subprocedures, but why wouldn't I just make the subprocedures non exportable in the module, ie leave off the EXPORT keyword? Is the idea so that more than one service program can be made from the same module?