<?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: Initializing SAS Environment Manager Service Architecture Framework for SAS 9.4M3 in Architecture</title>
    <link>https://communities.sas.com/t5/Architecture/Initializing-SAS-Environment-Manager-Service-Architecture/m-p/438584#M36</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/112075"&gt;@Sangavi&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I never had that problem before, it could be maintenance 3 specific. Perhaps one of the SAS Technical Support colleagues can help you better with the question.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyway, during most of unix-based maintenance/upgrades, that script must be run.&amp;nbsp;Hence, just follow the manual steps defined in the manual, and, if needed, you can still run that script. Is it a big problem in your organization?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 20 Feb 2018 09:36:22 GMT</pubDate>
    <dc:creator>JuanS_OCS</dc:creator>
    <dc:date>2018-02-20T09:36:22Z</dc:date>
    <item>
      <title>Initializing SAS Environment Manager Service Architecture Framework for SAS 9.4M3</title>
      <link>https://communities.sas.com/t5/Architecture/Initializing-SAS-Environment-Manager-Service-Architecture/m-p/428762#M35</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I followed the steps in the attached document for initializing SAS EVM Architecture framework on SAS 9.4M3.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I restart the Metadata Server, Object Spawner and Connect Spawner to load the new configurations,&amp;nbsp;&lt;/P&gt;&lt;P&gt;it is resetting the permissions of 'elssrv' , 'sasauth', 'sasperm' to 'sas'&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then I had to run setuid.sh under root to reset the permissions as root.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there anyway to avoid this permission change from 'root' to 'sas' from happening ?&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2018 12:30:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Architecture/Initializing-SAS-Environment-Manager-Service-Architecture/m-p/428762#M35</guid>
      <dc:creator>Sangavi</dc:creator>
      <dc:date>2018-01-18T12:30:11Z</dc:date>
    </item>
    <item>
      <title>Re: Initializing SAS Environment Manager Service Architecture Framework for SAS 9.4M3</title>
      <link>https://communities.sas.com/t5/Architecture/Initializing-SAS-Environment-Manager-Service-Architecture/m-p/438584#M36</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/112075"&gt;@Sangavi&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I never had that problem before, it could be maintenance 3 specific. Perhaps one of the SAS Technical Support colleagues can help you better with the question.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyway, during most of unix-based maintenance/upgrades, that script must be run.&amp;nbsp;Hence, just follow the manual steps defined in the manual, and, if needed, you can still run that script. Is it a big problem in your organization?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2018 09:36:22 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Architecture/Initializing-SAS-Environment-Manager-Service-Architecture/m-p/438584#M36</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2018-02-20T09:36:22Z</dc:date>
    </item>
  </channel>
</rss>

