- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Scp to Solarise node
Operating System - OpenVMS
1748134
Members
3543
Online
108758
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2011 06:16 AM
тАО06-08-2011 06:16 AM
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.
[...]
> 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.
[...]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2011 06:39 AM
тАО06-08-2011 06:39 AM
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.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2011 07:00 AM
тАО06-08-2011 07:00 AM
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
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP