<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Privs in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837232#M78135</link>
    <description>Miles,&lt;BR /&gt;&lt;BR /&gt;Could you please provide the actual error message?, little confusion as you have another similar thread.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Archunan</description>
    <pubDate>Fri, 04 Aug 2006 10:42:17 GMT</pubDate>
    <dc:creator>Arch_Muthiah</dc:creator>
    <dc:date>2006-08-04T10:42:17Z</dc:date>
    <item>
      <title>Privs</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837229#M78132</link>
      <description>getting an ACP no priv when I try and copy over some code from our TSTSTG to other servers, like  TEAM07,08 or 09. &lt;BR /&gt;&lt;BR /&gt;What do I do to fix this?&lt;BR /&gt;&lt;BR /&gt;They are Vax servers running Openvms 7.3</description>
      <pubDate>Fri, 04 Aug 2006 06:58:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837229#M78132</guid>
      <dc:creator>vmsserbo</dc:creator>
      <dc:date>2006-08-04T06:58:22Z</dc:date>
    </item>
    <item>
      <title>Re: Privs</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837230#M78133</link>
      <description>Miles,&lt;BR /&gt;&lt;BR /&gt;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).&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Fri, 04 Aug 2006 07:00:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837230#M78133</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2006-08-04T07:00:56Z</dc:date>
    </item>
    <item>
      <title>Re: Privs</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837231#M78134</link>
      <description>Miles,&lt;BR /&gt;&lt;BR /&gt;If you want to copy files from node TSTSTG to other nodes, you need to have proxy access.&lt;BR /&gt;&lt;BR /&gt;for example:&lt;BR /&gt;&lt;BR /&gt;user1 - account from TSTSTG&lt;BR /&gt;user2 - account on team08&lt;BR /&gt;user3 - account on team09&lt;BR /&gt;&lt;BR /&gt;1. grant network access&lt;BR /&gt;2. add proxy for the account from TSTSTG&lt;BR /&gt;&lt;BR /&gt;On the server team08&lt;BR /&gt;$ mc authorize&lt;BR /&gt;$ mod user2 /network&lt;BR /&gt;$ add/proxy TSTSTG::user1 user2 /default&lt;BR /&gt;$ exit&lt;BR /&gt;&lt;BR /&gt;same way you need to configure on other servers as well.&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;Raj&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Aug 2006 08:36:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837231#M78134</guid>
      <dc:creator>Chinraj Rajasekaran</dc:creator>
      <dc:date>2006-08-04T08:36:08Z</dc:date>
    </item>
    <item>
      <title>Re: Privs</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837232#M78135</link>
      <description>Miles,&lt;BR /&gt;&lt;BR /&gt;Could you please provide the actual error message?, little confusion as you have another similar thread.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Archunan</description>
      <pubDate>Fri, 04 Aug 2006 10:42:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837232#M78135</guid>
      <dc:creator>Arch_Muthiah</dc:creator>
      <dc:date>2006-08-04T10:42:17Z</dc:date>
    </item>
    <item>
      <title>Re: Privs</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837233#M78136</link>
      <description>That is correct! &lt;BR /&gt;Problem was resolved due to proxy setting&lt;BR /&gt;&lt;BR /&gt;Thanks all!&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Aug 2006 10:46:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837233#M78136</guid>
      <dc:creator>vmsserbo</dc:creator>
      <dc:date>2006-08-04T10:46:30Z</dc:date>
    </item>
    <item>
      <title>Re: Privs</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837234#M78137</link>
      <description>Miles,&lt;BR /&gt;&lt;BR /&gt;test the protections and security setting for the dire and user&lt;BR /&gt;$ dire /prot disk:[xxxxxx]target.dir&lt;BR /&gt;$ dire /security&lt;BR /&gt;$ sh protection  ! from the user wants to do copy&lt;BR /&gt;&lt;BR /&gt;then look into these command to set the protection&lt;BR /&gt;$ set protec=(g:erwd,w:erwd)/default&lt;BR /&gt;$ set file /owner_uic [nn,nn] dire_name&lt;BR /&gt;$ set file /prot = (s:, o:, g:, w) dire_name&lt;BR /&gt;&lt;BR /&gt;Note: I need urgently one help, so I am going to start one thread now.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Archunan &lt;BR /&gt;</description>
      <pubDate>Fri, 04 Aug 2006 10:56:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837234#M78137</guid>
      <dc:creator>Arch_Muthiah</dc:creator>
      <dc:date>2006-08-04T10:56:17Z</dc:date>
    </item>
    <item>
      <title>Re: Privs</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837235#M78138</link>
      <description>Miles,&lt;BR /&gt;&lt;BR /&gt;  On the source node TSTSTG, enable auditing of file access failures. Usually an alarm will suffice:&lt;BR /&gt;&lt;BR /&gt;$ REPLY/ENABLE=SECURITY&lt;BR /&gt;$ SET AUDIT/ALARM/ENABLE=FILE=FAIL=ALL&lt;BR /&gt;&lt;BR /&gt;  Now repeat your failing command. You should see an audit alarm which identifies the precise reason for the failure.</description>
      <pubDate>Sun, 06 Aug 2006 17:36:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/privs/m-p/3837235#M78138</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2006-08-06T17:36:33Z</dc:date>
    </item>
  </channel>
</rss>

