Re: Secuer copy (scp) issue

When you say "the output from scp -v", am I to infer that you mean the stuff normally printed to the screen (stdout/stderr)? If so, the problem is clearly on your end.

Could this be a CCSID problem? Could it be that the { or } characters are being mis-translated when the script is run, but not when you view the source?


On 8/14/2013 11:50 AM, John McKee wrote:

Script on my side has scp -v as last line. That is what I am
referring to. The script cleaqrly has white space between the source
and destination parameters on scp. But, log shows no space between
them.

I just received yet another email from the remote site. Again, he is
focused on replacing the variable SERV for an explicit destination.
Despite the fact that the output from scp -v clearly shows a
connection has been established with his system. I have asked him to
check the old server, if it is available for how it is configured.

Earlier, I tried replacing one of the four spaces with a backslash,
hoping it was the defined escape character. It wasn't. Still
scrunched the two parameters into one.

The original scp command in this mess isthis:

scp -v ${PEDID}@${SERV}:${PATHE|$1 ${PATHO}

The output from scp -v shows no space at all between $1 and ${PATHO}

Why he feels that replacing $SERV with the specific name id beyond me.

John McKee



On Wed, Aug 14, 2013 at 11:31 AM, Scott Klement
<midrange-l@xxxxxxxxxxxxxxxx> wrote:

Hi John,

Sorry if you've already explained this, but... which log are you
referring to?

I've never heard of it combining parameters like that, before. The only
thing I can think of is a bug in the program/script that is launching
scp. Unless, this is happening on the server side, which would make
sense, considering that you say that the server is what changed... but,
if this is happening on the server side, I would think there's nothing
you can do to fix it on the client side.

-SK



On 8/14/2013 10:37 AM, John McKee wrote:

There was a single space between the two parameters. The log shows no
apce at all, thuse instead of scp a b, log shows scp ab. In trying
scp a \ b. the result was still scp ab.

The four spaces was at the insistence from the guy on the other end.
Between that and his focusing on the SERV variable, which he is
positive is the problem, I am at a wall. The SERV variable isn't the
issue. Log clearly shows connect. But, the blank between the the two
scp parameters gets dropped. He wanted even more blanks.

The whole point is to copy a file from that system to the i on my
site. Which worked nicely on the old server.

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