1828630 Members
6622 Online
109983 Solutions
New Discussion

Privs

 
vmsserbo
Super Advisor

Privs

getting an ACP no priv when I try and copy over some code from our TSTSTG to other servers, like TEAM07,08 or 09.

What do I do to fix this?

They are Vax servers running Openvms 7.3
6 REPLIES 6
Robert Gezelter
Honored Contributor

Re: Privs

Miles,

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
Chinraj Rajasekaran
Frequent Advisor

Re: Privs

Miles,

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
Arch_Muthiah
Honored Contributor

Re: Privs

Miles,

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
Regards
Archie
vmsserbo
Super Advisor

Re: Privs

That is correct!
Problem was resolved due to proxy setting

Thanks all!
Arch_Muthiah
Honored Contributor

Re: Privs

Miles,

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
Regards
Archie
John Gillings
Honored Contributor

Re: Privs

Miles,

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.
A crucible of informative mistakes