<?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: OS scheduler/Schedule Manager by department in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/OS-scheduler-Schedule-Manager-by-department/m-p/479518#M13644</link>
    <description>&lt;P&gt;We have done something similar but with the&amp;nbsp;LSF scheduler. I do not see why this wouldn't work for the OS Scheduler. All departments are associated to a group in metadata. We have set up ACT's for each. Then we created&amp;nbsp;multiple scheduling servers, each with their own authentication domain and protected by an ACT to limit visibility to that one department. Now when one creates a flow the drop-down for scheduling server will only show the one for his or her department.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Using groups we are also able to assign a specific batch user to each department. That batch user has an account specified for the authentication domain belonging to the specific departmental scheduling server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In case one would ask, we have chosen not to employ separate logical server contexts for each department. It's a grid&amp;nbsp;install and grid option sets, constructs as above, ACT's (and corresponding ACL's on file system) allow us to do without.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;/P&gt;
&lt;P&gt;-- Jan.&lt;/P&gt;</description>
    <pubDate>Thu, 19 Jul 2018 14:27:15 GMT</pubDate>
    <dc:creator>jklaverstijn</dc:creator>
    <dc:date>2018-07-19T14:27:15Z</dc:date>
    <item>
      <title>OS scheduler/Schedule Manager by department</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/OS-scheduler-Schedule-Manager-by-department/m-p/479502#M13643</link>
      <description>&lt;P&gt;(Win x64 2012 server, 9.4TS1M5)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it possible to provide OS scheduler server or in Schedule manager (via SMC) to different groups and also keeping underlying physical storage for flows, scheduled jobs separate? If not, seeking ideas&amp;nbsp;as to how folks who support different departments provide this capability?&amp;nbsp; Another thought was to let users use SAS EG scheduler or allow just batch scheduling.&amp;nbsp; Thoughts?&amp;nbsp; (Thank you in advance)&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jul 2018 13:54:14 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/OS-scheduler-Schedule-Manager-by-department/m-p/479502#M13643</guid>
      <dc:creator>shoin</dc:creator>
      <dc:date>2018-07-19T13:54:14Z</dc:date>
    </item>
    <item>
      <title>Re: OS scheduler/Schedule Manager by department</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/OS-scheduler-Schedule-Manager-by-department/m-p/479518#M13644</link>
      <description>&lt;P&gt;We have done something similar but with the&amp;nbsp;LSF scheduler. I do not see why this wouldn't work for the OS Scheduler. All departments are associated to a group in metadata. We have set up ACT's for each. Then we created&amp;nbsp;multiple scheduling servers, each with their own authentication domain and protected by an ACT to limit visibility to that one department. Now when one creates a flow the drop-down for scheduling server will only show the one for his or her department.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Using groups we are also able to assign a specific batch user to each department. That batch user has an account specified for the authentication domain belonging to the specific departmental scheduling server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In case one would ask, we have chosen not to employ separate logical server contexts for each department. It's a grid&amp;nbsp;install and grid option sets, constructs as above, ACT's (and corresponding ACL's on file system) allow us to do without.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps,&lt;/P&gt;
&lt;P&gt;-- Jan.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jul 2018 14:27:15 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/OS-scheduler-Schedule-Manager-by-department/m-p/479518#M13644</guid>
      <dc:creator>jklaverstijn</dc:creator>
      <dc:date>2018-07-19T14:27:15Z</dc:date>
    </item>
  </channel>
</rss>

