Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
08-03-2006 11:58 PM
08-03-2006 11:58 PM
Privs
What do I do to fix this?
They are Vax servers running Openvms 7.3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2006 12:00 AM
08-04-2006 12:00 AM
Re: Privs
Check the account that you are using on the the servers to transfer the files. Also check the security settings on the target directories (do a DIRECTORY/SECURITY on the directory files).
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2006 01:36 AM
08-04-2006 01:36 AM
Re: Privs
If you want to copy files from node TSTSTG to other nodes, you need to have proxy access.
for example:
user1 - account from TSTSTG
user2 - account on team08
user3 - account on team09
1. grant network access
2. add proxy for the account from TSTSTG
On the server team08
$ mc authorize
$ mod user2 /network
$ add/proxy TSTSTG::user1 user2 /default
$ exit
same way you need to configure on other servers as well.
regards
Raj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2006 03:42 AM
08-04-2006 03:42 AM
Re: Privs
Could you please provide the actual error message?, little confusion as you have another similar thread.
I understand from your previous posting you might have setup the proxy corectly, in that case as Mr.Bob said, it may due the protoection setting on the destination directories, so check the protection of the destination directories.
Archunan
Archie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2006 03:46 AM
08-04-2006 03:46 AM
Re: Privs
Problem was resolved due to proxy setting
Thanks all!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2006 03:56 AM
08-04-2006 03:56 AM
Re: Privs
test the protections and security setting for the dire and user
$ dire /prot disk:[xxxxxx]target.dir
$ dire /security
$ sh protection ! from the user wants to do copy
then look into these command to set the protection
$ set protec=(g:erwd,w:erwd)/default
$ set file /owner_uic [nn,nn] dire_name
$ set file /prot = (s:, o:, g:, w) dire_name
Note: I need urgently one help, so I am going to start one thread now.
Archunan
Archie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2006 10:36 AM
08-06-2006 10:36 AM
Re: Privs
On the source node TSTSTG, enable auditing of file access failures. Usually an alarm will suffice:
$ REPLY/ENABLE=SECURITY
$ SET AUDIT/ALARM/ENABLE=FILE=FAIL=ALL
Now repeat your failing command. You should see an audit alarm which identifies the precise reason for the failure.