Re: CLLE source compiled as CLP? (was: Huh? PRTCMDUSG doesn't work on ILE CL programs?) -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: CLLE source compiled as CLP? (was: Huh? PRTCMDUSG doesn't work on ILE CL programs?)
From: rob@xxxxxxxxx
Date: Wed, 24 May 2006 12:14:46 -0400
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>

Prior to V5R4 I think there was only one command that would not compile in 
a CLP and that would have been CALLPRC for call procedure.
That being said, however, there were other reasons for compiling to CLLE 
versus CLP.
1 - Creating a module instead of a program.  Then binding that module with 
other modules to make a program or service program.
2 - Not having to run in the default activation group.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 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.