Re: CRTSRVPGM

- if you are binding multiple modules to one SRVPGM, you could have 3 levels of scope: local to a module, local to the SRVPGM, global.
- using binder language you could avoid some rebinds by providing more than one signature for the same SRVPGM
- in all other cases (including your example) it doesn't make any sense to use binder language

D*B

--------------------------------------------------
From: "David FOXWELL" <David.FOXWELL@xxxxxxxxx>
Sent: Tuesday, December 14, 2010 2:11 PM
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
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?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.