× 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 recognize the things you say - and also see what I was told by the support person - that if certain conditions obtain, it is probably OK.

Reason to do it? It's a simple call when there is not an API to do the task.

So ones mileage will vary, and Dennis also speaks of choices one makes. Still, it seems an option for someone.

And now off to get some Thai food - medium heat only please! Can't even think of trying the Challenging!
Vern

Scott Klement wrote:
hi Vern,

Vern Hamberg wrote:
"If your utility program uses the ILE/C or ILE/C++ standard files for I/O, you can run your utility from either the qsh command line or the QCMD command line."

I think you're reading an awful lot into this very simple statement. I think this is saying nothing more than the obvious: That it's possible for you to write code that'll work in either environment. (That's PAINFULLY obvious to me.)

Nowhere does it say that IBM's included QShell utilities are meant to be run from both environments.

Surely you understand the distinction between "you can design for more than one environment" and "everything will work from both places"?!


So I'm thinking that if IBM's utilities do the same, we can run them as I suggested.

That's a big *if*, and why would you want to? Calling the MV program via the CALL command is roughly equivalent to calling the CPP for the MOV command directly. Why would you want to do that?



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.