× 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: RPG/COBOL with embedded CL
  • From: email@xxxxxxxxxxxxxxxxxxx (James W Kilgore)
  • Date: Tue, 16 Mar 1999 03:07:14 -0800
  • Organization: Progressive Data Systems, Inc.

Colin,

You've hit upon a programming "nerve" if you will.

You are correct in that QCMDEXC is not a clean solution and a CL wrapper
is just another source member to manage.

let me throw out a couple of choices:
1) make the call to a CL wrapper a /COPY member.  Debug once, use
everywhere.
2) whatever you are going to QCMDEXC, call whatever the command calls
instead.

If DLTF command calls DLTFCCP program, then from your program call
DLTFCCP directly.

Personally, option 2, by program call, API, or bound procedure might as
well be a /COPY interface.

In the structure of the AS/400, monolithic programming is not the model.
Component binding in the solution de jour.



Colin Williams wrote:
> 
> What do you mean. Do you mean that I can now create a CLLE module,
> because that to me is just another source member that has to be managed!
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.