<?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: LSF time limit of job / flow in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/LSF-time-limit-of-job-flow/m-p/366232#M11048</link>
    <description>&lt;P&gt;It's grayed out.&amp;nbsp; For this server, I don't actually own the flows, so I can't kill them.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The workflow is that I create a DI job, and then deploy the job, then put in a ticket for an admin to create the flow and schedule it.&amp;nbsp; Since I don't own the flow, I can't kill it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The other down side of this approach is that the SAS job doesn't run as me, it runs as some service account they use for scheduling.&amp;nbsp; I can't even trigger a flow.&amp;nbsp; So it's not ideal for me as a developer, but it's not my server.&amp;nbsp; Maybe if I keep putting in enough tickets to kill hung jobs, they'll give me access to the service account. : )&lt;/P&gt;</description>
    <pubDate>Mon, 12 Jun 2017 17:14:16 GMT</pubDate>
    <dc:creator>Quentin</dc:creator>
    <dc:date>2017-06-12T17:14:16Z</dc:date>
    <item>
      <title>LSF time limit of job / flow</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/LSF-time-limit-of-job-flow/m-p/366187#M11045</link>
      <description>&lt;P&gt;On a BI server using SAS Management Console to schedule LSF flows, is it possible to specify a time limit for execution a job or flow?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have some nightly flows that hang on occassion.&amp;nbsp; I don't have a root cause for the hang yet (suspect network problems / remote database connections).&amp;nbsp; I would like to be able to set an option that says "If this job/flow runs for longer than X minutes, kill it."&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Currently when a job hangs it just sits there with a status of running, and the next night's run does not start, and since I can't kill the job myself (sadly I don't have rights), I have to put in a ticket to get an admin to kill it.&amp;nbsp; So life would be easier if when we created the flow they just specified a run time limit which would automatically kill the job.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think it's a stripped down version of LSF that comes with EBI server.&amp;nbsp; Not sure if this is possible?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thx.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jun 2017 15:14:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/LSF-time-limit-of-job-flow/m-p/366187#M11045</guid>
      <dc:creator>Quentin</dc:creator>
      <dc:date>2017-06-12T15:14:23Z</dc:date>
    </item>
    <item>
      <title>Re: LSF time limit of job / flow</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/LSF-time-limit-of-job-flow/m-p/366225#M11047</link>
      <description>&lt;P&gt;The Kill option in LSF Process Manager - is it grayed out for you or does it just not work?&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jun 2017 16:57:56 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/LSF-time-limit-of-job-flow/m-p/366225#M11047</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2017-06-12T16:57:56Z</dc:date>
    </item>
    <item>
      <title>Re: LSF time limit of job / flow</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/LSF-time-limit-of-job-flow/m-p/366232#M11048</link>
      <description>&lt;P&gt;It's grayed out.&amp;nbsp; For this server, I don't actually own the flows, so I can't kill them.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The workflow is that I create a DI job, and then deploy the job, then put in a ticket for an admin to create the flow and schedule it.&amp;nbsp; Since I don't own the flow, I can't kill it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The other down side of this approach is that the SAS job doesn't run as me, it runs as some service account they use for scheduling.&amp;nbsp; I can't even trigger a flow.&amp;nbsp; So it's not ideal for me as a developer, but it's not my server.&amp;nbsp; Maybe if I keep putting in enough tickets to kill hung jobs, they'll give me access to the service account. : )&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jun 2017 17:14:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/LSF-time-limit-of-job-flow/m-p/366232#M11048</guid>
      <dc:creator>Quentin</dc:creator>
      <dc:date>2017-06-12T17:14:16Z</dc:date>
    </item>
    <item>
      <title>Re: LSF time limit of job / flow</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/LSF-time-limit-of-job-flow/m-p/366336#M11051</link>
      <description>&lt;P&gt;My user account is defined as an LSF admin account and I can kill other users jobs. Maybe you could request that.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jun 2017 20:40:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/LSF-time-limit-of-job-flow/m-p/366336#M11051</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2017-06-12T20:40:39Z</dc:date>
    </item>
  </channel>
</rss>

