× 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.



I really don't understand this insistence on not using CL for what it is good for - running commands. One problem with QCMDEXC is that it does not log things the same way as running a command in CL does. Another is, you have no prompting when writing the code.

Basic principle - use each language for what it is good for. CL is best for doing commands - it does stand for "Command Language" after all - and RPG is best for database processing and display/printing. Don't try to make CL into a database machine, and don't make RPG do overrides.

In the world of ILE, write the separate modules in whatever language is appropriate, then link them into one program. CL is also an ILE language.

JMHO
Vern

At 01:49 AM 9/14/2005, you wrote:

Hi Terry,

Like Scott wrote, you are not limited to do the OPNQRYF action in CL.
If you are not ready now for embedded SQL, and want to keep using the
OPNQRYF command, you can fire it from your RPGLE program by using
QCMDEXC. Define your file as usropn and do the work in the RPG program.
I put an example on http://code.midrange.com/index.php?id=7d862e284a

HTH, Arco Simonse


Terry wrote:

> A.) create an OPNQRYF over the history file in a CL and chain
> to it or
>

Scott wrote:

> >
> > Huh?
> >
> > a) You don't need CL to use OPNQRYF.
> >
DISCLAIMER:
This message contains information that may be privileged or confidential and is the property of the sender. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy,disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

This footnote also confirms that this email message has been swept for the presence of computer viruses


--
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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.