Scp to Solarise node (475 Views)
Reply
Regular Advisor
Kumar_Sanjay
Posts: 75
Registered: ‎03-26-2007
Message 1 of 13 (475 Views)

Scp to Solarise node

We are sending some SCP file from VMS to SUN node.
we are able to do SCP sucessfully but unable to put file in Upper case. looks like my syntex is work.. any one please help me,

scp "EXTRACT.CSV" userid1@sunsystem1.cop.net:"/app/tei1/BKP/INPUTS/AP/""TEST.CSV"

We can able to transfer the file.. but remort end we are receiveing the file with "
Exam "TEST.CSV

could any one please tell me how to remove " ?
Please use plain text.
Honored Contributor
Steven Schweda
Posts: 9,084
Registered: ‎02-23-2005
Message 2 of 13 (475 Views)

Re: Scp to Solarise node

> could any one please tell me how to remove " ?

Did you try removing the "" before
'TEST.CSV'?

scp "EXTRACT.CSV" userid1@sunsystem1.cop.net:"/app/tei1/BKP/INPUTS/AP/TEST.CSV"

DCL thinks that "AB""CD" is really
AB"CD
Please use plain text.
Regular Advisor
Kumar_Sanjay
Posts: 75
Registered: ‎03-26-2007
Message 3 of 13 (475 Views)

Re: Scp to Solarise node

Steven, How i can remove the "
so it will be ABCD
Please use plain text.
Honored Contributor
Joseph Huber_1
Posts: 1,082
Registered: ‎02-03-2004
Message 4 of 13 (475 Views)

Re: Scp to Solarise node

[How i can remove the "]

First of all remove the double "" from the scp command.

If the question is how to remove the " on the Unix side:
mv '"TEST.CSV' TEST.CSV
http://www.mpp.mpg.de/~huber
Please use plain text.
Regular Advisor
Kumar_Sanjay
Posts: 75
Registered: ‎03-26-2007
Message 5 of 13 (475 Views)

Re: Scp to Solarise node

Did you try removing the "" before
'TEST.CSV'?
This method is transferring file name as 'TEST.CSV

scp "EXTRACT.CSV" userid1@sunsystem1.cop.net:"/app/tei1/BKP/INPUTS/AP/TEST.CSV"
I tested before, it will recognize entire path as directory and hence transfer fail
Please use plain text.
Regular Advisor
Kumar_Sanjay
Posts: 75
Registered: ‎03-26-2007
Message 6 of 13 (475 Views)

Re: Scp to Solarise node

Joseph,

1) The Path is case sensative so i must put " "
otherwise it say invalid path.

userid1@sunsystem1.cop.net:"/app/tei1/BKP/INPUTS/AP/"TEST.CSV


if i transfer, it is sucessfull but lowercase file name in Unix system.


Now i want to trasnfer the file as upper case as well.


Please use plain text.
Regular Advisor
Kumar_Sanjay
Posts: 75
Registered: ‎03-26-2007
Message 7 of 13 (475 Views)

Re: Scp to Solarise node

Joseph,

1) The Path is case sensitive so i must put " "
otherwise it say invalid path.

userid1@sunsystem1.cop.net:"/app/tei1/BKP/INPUTS/AP/"TEST.CSV


if I transfer, it is successful but lowercase file name in Unix system.


Now I want to transfer the file as upper case as well."
Please use plain text.
Honored Contributor
Steven Schweda
Posts: 9,084
Registered: ‎02-23-2005
Message 8 of 13 (475 Views)

Re: Scp to Solarise node

> [...] from VMS to SUN node.

What, exactly, are we dealing with here?

tcpip show version

uname -a
ssh -V

> I tested before, it will recognize entire
> path as directory and hence transfer fail

What, exactly, does that mean? As usual,
showing actual commands with their actual
output can be more helpful than vague
descriptions or interpretations.

Around here:

alp $ dire wd.c;

Directory ALP$DKC0:[SMS.ITRC]

wd.c;20

Total of 1 file.

alp $ scp wd.c sms@sol:"/usr/users/sms/UC_DIR/WD.C"
wd.c | 1.1kB | 1.1 kB/s | TOC: 00:00:01 | 100%

alp $ ssh -l sms sol "ls -l /usr/users/sms/UC_DIR"
Authentication successful.

total 4
-rwxr-xr-- 1 sms users 1141 Jun 8 01:57 WD.C

alp $ tcpip show version

HP TCP/IP Services for OpenVMS Alpha Version V5.6 - ECO 5
on a COMPAQ Professional Workstation XP1000 running OpenVMS V8.3

sol# uname -a
SunOS sol 5.10 Generic_141444-09 sun4u sparc sun4u

sol# ssh -V
Sun_SSH_1.1.2, SSH protocols 1.5/2.0, OpenSSL 0x0090704f
Please use plain text.
Honored Contributor
Joseph Huber_1
Posts: 1,082
Registered: ‎02-03-2004
Message 9 of 13 (475 Views)

Re: Scp to Solarise node

Sanjay,
I think reading the VMS user and DCL dictionary manual may help to understand, what double double quotes within a quoted string mean.

The simple fact -what Stevens example shows- is:
put the whole remote file specification in string quotes, not only the path.
OR, if Your parse_stayle is EXTENDED, just specify the output path , leaving off the file-name, then the output name will be identical to the local one:

scp EXTRACT.CSV userid1@sunsystem1.cop.net:"/app/tei1/BKP/INPUTS/AP/"
http://www.mpp.mpg.de/~huber
Please use plain text.
Honored Contributor
Joseph Huber_1
Posts: 1,082
Registered: ‎02-03-2004
Message 10 of 13 (475 Views)

Re: Scp to Solarise node

And by the way, in my environment there is no need to put anything in string quotes at all:

MPIW10_HUB>scp Test.CSV pclhec01:tmp/
Test.CSV | 5B | 0.0 kB/s | TOC: 00:00:01 | 100%

MPIW10_HUB>
MPIW10_HUB>ssh pclhec01 ls tmp/Test.CSV
Authentication successful.
tmp/Test.CSV

My environment:
Parse Style: Extended
VMS 7.3-1 , TCPIP 5.4

(and don't know if it is important, the DECC$ feature logicals are set as if DECC$UNIX_LEVEL=30 in later versions of VMS.)
http://www.mpp.mpg.de/~huber
Please use plain text.
Honored Contributor
Steven Schweda
Posts: 9,084
Registered: ‎02-23-2005
Message 11 of 13 (474 Views)

Re: Scp to Solarise node

> And by the way, in my environment there is
> no need to put anything in string quotes at
> all:

Around here:

alp $ show proc /parse
[...]
Parse Style: Extended

alp $ scp wd.c sms@sol:/usr/users/sms/UC_DIR/WD.c
tcpip$ssh_scp2.exe: warning: open: /usr/users/sms/uc_dir/wd.c (dst): no such file (server msg: 'No such file')

%TCPIP-E-SSH_FC_ERR_NO_S, file doesn't exist


> (and don't know if it is important, the
> DECC$ feature logicals are set as if
> DECC$UNIX_LEVEL=30 in later versions of
> VMS.)

I assume that "are set" means that _you_ set
them. And yes, that's probably _very_
important in a case like this. Unlike some
programs I could name, the TCPIP SSH-related
utilities seem not to set any appropriate
DECC$feature logical names themselves, so
SET PROCESS /PARSE_STYLE, by itself, doesn't
do much.

Do you really leave these DECC$feature names
set all the time? To me, that sounds
dangerous. I have Parse Style: Extended set
in my LOGIN.COM, but I don't dare define any
DECC$feature logical names for general use.
As it says in the HELP (CRTL
Feature_Logical_Names):

[...]
o Do not set C RTL feature logical names for the system.
Set them only for the applications that need them,
because other applications including OpenVMS components
depend on the default behavior of these logical names.
[...]
Please use plain text.
Honored Contributor
Joseph Huber_1
Posts: 1,082
Registered: ‎02-03-2004
Message 12 of 13 (474 Views)

Re: Scp to Solarise node

"my environment" means my process environment, not system settings, every user follows its own taste, but most interactive work is done on Linux systems.

decc$feature logicals: probably a YMMV case.
I am mainly working on/programming for Unix systems, and doing system management for the remaining VMS systems, but still prefer to do much editing etc. on VMS. So for me it is more convenient not to put string quotes everywhere.
I almost never have problems with that - but maybe I seldom do complicated things on VMS requiring strict VMS behaviour.
http://www.mpp.mpg.de/~huber
Please use plain text.
Honored Contributor
Joseph Huber_1
Posts: 1,082
Registered: ‎02-03-2004
Message 13 of 13 (474 Views)

Re: Scp to Solarise node


and for ssh and scp, the only one DECC$ feature necessary is (probably)
define DECC$ARGV_PARSE_STYLE "ENABLE"
together with parse_style=extended.
http://www.mpp.mpg.de/~huber
Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation