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



Hello. I've tried this, and now I get my error.log file and also the screen
displaying the error message.  The log file actually contains this:

Usage: cp [-fhip] [-r|-R] [-E{force|ignore|warn}] [--] src target
  or: cp [-fhip] [-r|-R] [-E{force|ignore|warn}] [--] src1 ... srcN
directory

This implies that you're issuing a copy (cp) command with the wrong syntax. I think it's a good thing that it's telling you about this, because now you can fix it.

Why have a cp command if you don't care whether it worked or not?


How can I stop the screen from appearing?  I'm using QP2SHELL to do this,
and I did not expect a terminal window to open at all.

It'll display anything from stderr or stdout to your screen. It's not really a terminal like QP2TERM is, it's just a screen where it can show the output.

One way to completely eliminate it would be to use Qp2RunPase() instead of QP2SHELL -- but that'll require an HLL, since you have to be able to pass arrays of pointers for the parameters and environment variables.

I have an example pf Qp2RunPase() that's written in ILE RPG if you're interested, let me know.

I've also tried the -B and -q options on the SCP command (batch mode and
'quiet' mode) with no luck.

The error message that you quoted pertains to the CP (not SCP!) command.

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.