<?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: while sas code running in batch/Scheduler can we submit same sas code again in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/while-sas-code-running-in-batch-Scheduler-can-we-submit-same-sas/m-p/911119#M27837</link>
    <description>&lt;P data-unlink="true"&gt;Since your RSUBMITs are followed immediately by SIGNOFFs, the CONNECT servers may be torn down before your code completes. You need to add &lt;A href="https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.3/connref/n08d4h35p7cygvn1wkicvremmi3d.htm" target="_blank" rel="noopener"&gt;WAITFOR statements&lt;/A&gt; to&amp;nbsp;cause the SIGNOFFs to wait until the RSUBMIT code blocks complete.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I will agree with Patrick that having Tivoli just schedule all three jobs at the proper time seems like a easier approach.&lt;/P&gt;</description>
    <pubDate>Wed, 10 Jan 2024 12:57:40 GMT</pubDate>
    <dc:creator>doug_sas</dc:creator>
    <dc:date>2024-01-10T12:57:40Z</dc:date>
    <item>
      <title>while sas code running in batch/Scheduler can we submit same sas code again</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/while-sas-code-running-in-batch-Scheduler-can-we-submit-same-sas/m-p/911055#M27834</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Below is SAS code, which is scheduled in Tivoli. it is scheduled for every 5 minutes (1 hour actual time).&lt;BR /&gt;based on time, below code will trigger another codes by rsubmit.&lt;/P&gt;
&lt;P&gt;eg:-at 20:15 this code is triggered in Tivoli where 2 rsubmit code are running(still in progress, it'll take 20 minutes to finish job)&lt;/P&gt;
&lt;P&gt;At 20:20 Tivoli will trigger same sas code again, based on condition given in code, it should trigger another set of sas code as below.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;is this scenario possiable by using Rsubmit. because this functionality is hapenning by call execute.&lt;/P&gt;
&lt;P&gt;we want to convert it into rsubmit due to compliances.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;%let date=%sysfunc(today(), yymmdd6.);&lt;/DIV&gt;
&lt;DIV&gt;%let time=%sysfunc(time(), hhmm); %put &amp;amp;time;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;data _null_;&lt;/DIV&gt;
&lt;DIV&gt;/*time=scan(strip("&amp;amp;time."),1,':');*/&lt;/DIV&gt;
&lt;DIV&gt;time=strip("&amp;amp;time.");&lt;/DIV&gt;
&lt;DIV&gt;call symput('tm',strip(time));&lt;/DIV&gt;
&lt;DIV&gt;call symput('week',strip(weekday(today())));&lt;/DIV&gt;
&lt;DIV&gt;run ;&lt;/DIV&gt;
&lt;DIV&gt;%put x&amp;amp;tm.z a&amp;amp;week.b;&lt;/DIV&gt;
&lt;DIV&gt;%global x y;&lt;/DIV&gt;
&lt;DIV&gt;%let x=Default;&lt;/DIV&gt;
&lt;DIV&gt;%let y=Default;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;filename donef '/sasdata/cro_rte/user_libs/crm_prod/aasbon/systask/rsubmit/sreeni/tes_done';&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;filename mylog1 '/sasdata/cro_rte/user_libs/crm_prod/aasbon/systask/rsubmit/sreeni/tes_a.log';&lt;/DIV&gt;
&lt;DIV&gt;filename mylog2 '/sasdata/cro_rte/user_libs/crm_prod/aasbon/systask/rsubmit/sreeni/tes_b.log';&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;%macro test;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;data _null_;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;%if &amp;amp;tm. = 20:15 or &amp;amp;tm.= 20:15 or &amp;amp;tm. = '20:15' %then %do;&lt;/DIV&gt;
&lt;DIV&gt;options sascmd="sas";&lt;/DIV&gt;
&lt;DIV&gt;SIGNON tes_a ;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;RSUBMIT wait=no log=mylog1 ;&lt;/DIV&gt;
&lt;DIV&gt;%let x=Success1;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt; %include "/sasdata/cro_rte/user_libs/crm_prod/aasbon/systask/rsubmit/sreeni/tes_a.sas";&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;endrsubmit;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;SIGNON tes_b ;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;RSUBMIT wait=no&amp;nbsp; log=mylog2 ;&lt;/DIV&gt;
&lt;DIV&gt;%let x=Success1;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt; %include "/sasdata/cro_rte/user_libs/crm_prod/aasbon/systask/rsubmit/sreeni/tes_b.sas";&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;endrsubmit;&lt;/DIV&gt;
&lt;DIV&gt;signoff _all_;&lt;/DIV&gt;
&lt;DIV&gt;%end;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;%else %if &amp;amp;tm. = 20:20 or &amp;amp;tm.= 20:20 or &amp;amp;tm. = '20:20' %then %do;&lt;/DIV&gt;
&lt;DIV&gt;options sascmd="sas";&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;SIGNON tes_c ;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;RSUBMIT wait=no log=mylog3 ;&lt;/DIV&gt;
&lt;DIV&gt;%let x=Success2;&lt;/DIV&gt;
&lt;DIV&gt;%include "/sasdata/cro_rte/user_libs/crm_prod/aasbon/systask/rsubmit/sreeni/tes_c.sas";&lt;/DIV&gt;
&lt;DIV&gt;endrsubmit;&lt;/DIV&gt;
&lt;DIV&gt;signoff&amp;nbsp; tes_c;&lt;/DIV&gt;
&lt;DIV&gt;%end;&lt;/DIV&gt;
&lt;DIV&gt;
&lt;P&gt;run;&lt;/P&gt;
&lt;P&gt;%mend test;&lt;/P&gt;
&lt;P&gt;%test;&lt;BR /&gt;%put a&amp;amp;x.z;&lt;/P&gt;
&lt;P&gt;data _null_;&lt;BR /&gt;file donef;&lt;BR /&gt;run;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Help is appreciable.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Kenneth.&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Wed, 10 Jan 2024 01:40:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/while-sas-code-running-in-batch-Scheduler-can-we-submit-same-sas/m-p/911055#M27834</guid>
      <dc:creator>Asbon</dc:creator>
      <dc:date>2024-01-10T01:40:37Z</dc:date>
    </item>
    <item>
      <title>Re: while sas code running in batch/Scheduler can we submit same sas code again</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/while-sas-code-running-in-batch-Scheduler-can-we-submit-same-sas/m-p/911062#M27835</link>
      <description>&lt;P&gt;Why do you need this rsubmit blocks at all? Can't you just schedule these jobs separately in Tivoli?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;...and if in your real case the master job needs to pass some parameters to dependent jobs then consider using a control table. With control tables I normally prefer to use a database to avoid any locking issues and allow for concurrency - but it's also possible with SAS tables and libname option filelockwait=&amp;lt;n&amp;gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2024 02:58:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/while-sas-code-running-in-batch-Scheduler-can-we-submit-same-sas/m-p/911062#M27835</guid>
      <dc:creator>Patrick</dc:creator>
      <dc:date>2024-01-10T02:58:29Z</dc:date>
    </item>
    <item>
      <title>Re: while sas code running in batch/Scheduler can we submit same sas code again</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/while-sas-code-running-in-batch-Scheduler-can-we-submit-same-sas/m-p/911119#M27837</link>
      <description>&lt;P data-unlink="true"&gt;Since your RSUBMITs are followed immediately by SIGNOFFs, the CONNECT servers may be torn down before your code completes. You need to add &lt;A href="https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.3/connref/n08d4h35p7cygvn1wkicvremmi3d.htm" target="_blank" rel="noopener"&gt;WAITFOR statements&lt;/A&gt; to&amp;nbsp;cause the SIGNOFFs to wait until the RSUBMIT code blocks complete.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I will agree with Patrick that having Tivoli just schedule all three jobs at the proper time seems like a easier approach.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2024 12:57:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/while-sas-code-running-in-batch-Scheduler-can-we-submit-same-sas/m-p/911119#M27837</guid>
      <dc:creator>doug_sas</dc:creator>
      <dc:date>2024-01-10T12:57:40Z</dc:date>
    </item>
  </channel>
</rss>

