<?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: batch submit SAS code in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/batch-submit-SAS-code/m-p/549036#M152297</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/10531"&gt;@GeorgeSAS&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A call direct to sas.exe would give you a "raw" SAS without the -config or autoexec settings defined in the EG workspace server, so you will be on your own and have to include these informations in your call.&amp;nbsp;Using sasbatch.sh might not be a good idea either, as it might be modified for daily batch processing.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So talk to your administrator. It seems that she has a relaxed approach to server operation, since you have terminal access to the server and not only FTP, and she might be willing to tailor a special command for you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I was your administrator and you came with convincing reasons, I would make a userbatch.sh file using a setup similar to that found in the SAS EG environment, and set it to write -log and -lst files to the same directory as the -sysin file. Then you could just call the command with your program as argument. I would use nohup, so the job would continue when you signed out from your terminal session, and I might add a -termstmt macro to send a SMS to a number supplied as second argument to the command and passed as -sysparm, when the job is complete.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 06 Apr 2019 12:55:13 GMT</pubDate>
    <dc:creator>ErikLund_Jensen</dc:creator>
    <dc:date>2019-04-06T12:55:13Z</dc:date>
    <item>
      <title>batch submit SAS code</title>
      <link>https://communities.sas.com/t5/SAS-Programming/batch-submit-SAS-code/m-p/548835#M152247</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I program on unix SAS from SAS EG.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I working in SAS EG which connect to the unix server. also I use putty which connect to the unix server to manage my SAS files( SAS programs, SAS logs and SAS datasets etc) in that server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My question is how I can use batch mode to submit SAS program from putty(or any other &lt;SPAN&gt;terminal&lt;/SPAN&gt;) instead of from SAS EG?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Fri, 05 Apr 2019 17:04:52 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/batch-submit-SAS-code/m-p/548835#M152247</guid>
      <dc:creator>GeorgeSAS</dc:creator>
      <dc:date>2019-04-05T17:04:52Z</dc:date>
    </item>
    <item>
      <title>Re: batch submit SAS code</title>
      <link>https://communities.sas.com/t5/SAS-Programming/batch-submit-SAS-code/m-p/548851#M152252</link>
      <description>&lt;P&gt;Check out sasbatch.sh in your &amp;lt;ConfigDir&amp;gt;\Lev1\SASApp\BatchServer directory.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can use that and pass in -sysin &amp;lt;mySASProgram&amp;gt; -log &amp;lt;writeMyLogHere&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Apr 2019 17:37:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/batch-submit-SAS-code/m-p/548851#M152252</guid>
      <dc:creator>JerryV</dc:creator>
      <dc:date>2019-04-05T17:37:43Z</dc:date>
    </item>
    <item>
      <title>Re: batch submit SAS code</title>
      <link>https://communities.sas.com/t5/SAS-Programming/batch-submit-SAS-code/m-p/548860#M152254</link>
      <description>On the unix server, modify your  .profile so it "knows" where to look to execute the "sas" command.  Then from the unix folder that holds the program, enter the command:&lt;BR /&gt;&lt;BR /&gt;sas programname&lt;BR /&gt;&lt;BR /&gt;You will likely need help setting up the path command within your profile.</description>
      <pubDate>Fri, 05 Apr 2019 18:05:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/batch-submit-SAS-code/m-p/548860#M152254</guid>
      <dc:creator>Astounding</dc:creator>
      <dc:date>2019-04-05T18:05:58Z</dc:date>
    </item>
    <item>
      <title>Re: batch submit SAS code</title>
      <link>https://communities.sas.com/t5/SAS-Programming/batch-submit-SAS-code/m-p/548994#M152280</link>
      <description>&lt;P&gt;If you have the SAS client tool SAS Management Console available you can run batch jobs via the Schedule Manager - no command line stuff is required.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Apr 2019 23:06:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/batch-submit-SAS-code/m-p/548994#M152280</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2019-04-05T23:06:20Z</dc:date>
    </item>
    <item>
      <title>Re: batch submit SAS code</title>
      <link>https://communities.sas.com/t5/SAS-Programming/batch-submit-SAS-code/m-p/549015#M152289</link>
      <description>&lt;P&gt;Have you talked to the server-administrator? If not do it before you try anything else. The admin might not be that happy if you schedule jobs outside of business-hours interfering maintenance-jobs.&lt;/P&gt;</description>
      <pubDate>Sat, 06 Apr 2019 05:10:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/batch-submit-SAS-code/m-p/549015#M152289</guid>
      <dc:creator>andreas_lds</dc:creator>
      <dc:date>2019-04-06T05:10:59Z</dc:date>
    </item>
    <item>
      <title>Re: batch submit SAS code</title>
      <link>https://communities.sas.com/t5/SAS-Programming/batch-submit-SAS-code/m-p/549036#M152297</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/10531"&gt;@GeorgeSAS&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A call direct to sas.exe would give you a "raw" SAS without the -config or autoexec settings defined in the EG workspace server, so you will be on your own and have to include these informations in your call.&amp;nbsp;Using sasbatch.sh might not be a good idea either, as it might be modified for daily batch processing.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So talk to your administrator. It seems that she has a relaxed approach to server operation, since you have terminal access to the server and not only FTP, and she might be willing to tailor a special command for you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I was your administrator and you came with convincing reasons, I would make a userbatch.sh file using a setup similar to that found in the SAS EG environment, and set it to write -log and -lst files to the same directory as the -sysin file. Then you could just call the command with your program as argument. I would use nohup, so the job would continue when you signed out from your terminal session, and I might add a -termstmt macro to send a SMS to a number supplied as second argument to the command and passed as -sysparm, when the job is complete.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 06 Apr 2019 12:55:13 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/batch-submit-SAS-code/m-p/549036#M152297</guid>
      <dc:creator>ErikLund_Jensen</dc:creator>
      <dc:date>2019-04-06T12:55:13Z</dc:date>
    </item>
  </channel>
</rss>

