CRTSRVPGM -- MIDRANGE-L

Subject: CRTSRVPGM
From: David FOXWELL <David.FOXWELL@xxxxxxxxx>
Date: Tue, 14 Dec 2010 14:11:31 +0100
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: CRTSRVPGM , Dennis Lovelady
Re: CRTSRVPGM , dieter.bender
RE: CRTSRVPGM , Schmidt, Mihael
Re: CRTSRVPGM , Scott Klement

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.