<?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 Password change and schduler issue in SAS Customer Intelligence</title>
    <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/Password-change-and-schduler-issue/m-p/416262#M687</link>
    <description>&lt;P&gt;Dear Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My client is SAS CI 6.4 , would like to know the impact of below change procedures&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Password change procedure (internal &amp;amp; external users)&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;My client change the password for internal and external users every 2 months once, is it going to hamper the system. If yes Let me know the alternative procedure.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Scheduler issue&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;After scheduling the campaign in platform process management, the campaigns are fail with exit code1, is any one have solution for this same&lt;/P&gt;&lt;P&gt;&amp;nbsp;Amarnadh&lt;/P&gt;</description>
    <pubDate>Mon, 27 Nov 2017 07:00:34 GMT</pubDate>
    <dc:creator>Amarnadh</dc:creator>
    <dc:date>2017-11-27T07:00:34Z</dc:date>
    <item>
      <title>Password change and schduler issue</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/Password-change-and-schduler-issue/m-p/416262#M687</link>
      <description>&lt;P&gt;Dear Team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My client is SAS CI 6.4 , would like to know the impact of below change procedures&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Password change procedure (internal &amp;amp; external users)&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;My client change the password for internal and external users every 2 months once, is it going to hamper the system. If yes Let me know the alternative procedure.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Scheduler issue&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;After scheduling the campaign in platform process management, the campaigns are fail with exit code1, is any one have solution for this same&lt;/P&gt;&lt;P&gt;&amp;nbsp;Amarnadh&lt;/P&gt;</description>
      <pubDate>Mon, 27 Nov 2017 07:00:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/Password-change-and-schduler-issue/m-p/416262#M687</guid>
      <dc:creator>Amarnadh</dc:creator>
      <dc:date>2017-11-27T07:00:34Z</dc:date>
    </item>
    <item>
      <title>Re: Password change and schduler issue</title>
      <link>https://communities.sas.com/t5/SAS-Customer-Intelligence/Password-change-and-schduler-issue/m-p/416271#M688</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/160607"&gt;@Amarnadh&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;for the first question, regarding SAS users (system accounts and interactive accounts) I think you would rather get the SAS Platform Administration training, since it is a very basic question, or, at least, spend some time reading the documentation that is available.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/mcsecug/63190/HTML/default/viewer.htm#n1kxhdu1ams2rzn180hnad7xwzm1.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/mcsecug/63190/HTML/default/viewer.htm#n1kxhdu1ams2rzn180hnad7xwzm1.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://documentation.sas.com/?docsetId=bisecag&amp;amp;docsetTarget=p0kb2gtnuyjnrnn1hduu5by88u4f.htm&amp;amp;docsetVersion=9.4&amp;amp;locale=en" target="_blank"&gt;http://documentation.sas.com/?docsetId=bisecag&amp;amp;docsetTarget=p0kb2gtnuyjnrnn1hduu5by88u4f.htm&amp;amp;docsetVersion=9.4&amp;amp;locale=en&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/mcsecug/69854/HTML/default/viewer.htm#aboutum.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/mcsecug/69854/HTML/default/viewer.htm#aboutum.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For third party software:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- LSF&amp;nbsp;&lt;A href="https://www.google.nl/url?sa=t&amp;amp;rct=j&amp;amp;q=&amp;amp;esrc=s&amp;amp;source=web&amp;amp;cd=1&amp;amp;cad=rja&amp;amp;uact=8&amp;amp;ved=0ahUKEwjJ5oGIq97XAhVMzaQKHfoRBZEQFggnMAA&amp;amp;url=https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2Fen%2FSSETD4_9.1.3%2Flsf_command_ref%2Flspasswd.1.html&amp;amp;usg=AOvVaw1d3LLcLcZWyZCGPpkXfuNa" target="_blank"&gt;https://www.google.nl/url?sa=t&amp;amp;rct=j&amp;amp;q=&amp;amp;esrc=s&amp;amp;source=web&amp;amp;cd=1&amp;amp;cad=rja&amp;amp;uact=8&amp;amp;ved=0ahUKEwjJ5oGIq97XAhVMzaQKHfoRBZEQFggnMAA&amp;amp;url=https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2Fen%2FSSETD4_9.1.3%2Flsf_command_ref%2Flspasswd.1.html&amp;amp;usg=AOvVaw1d3LLcLcZWyZCGPpkXfuNa&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;- other third party software: please check at the vendor's documentation&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Now, for the second question, which is a more specific one, It think you should know that exit code 1 means exit with warnings,&amp;nbsp; in any operating system ( &lt;A href="http://support.sas.com/documentation/cdl/en/hostwin/69955/HTML/default/viewer.htm#n0d8f2zgsbjtqwn1f384lia2nlbm.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/hostwin/69955/HTML/default/viewer.htm#n0d8f2zgsbjtqwn1f384lia2nlbm.htm&lt;/A&gt; ), as general rule. However, not always (&amp;nbsp;&lt;A href="https://communities.sas.com/t5/Administration-and-Deployment/LSF-exit-code-in-relation-to-SAS-return-code/td-p/205784" target="_blank"&gt;https://communities.sas.com/t5/Administration-and-Deployment/LSF-exit-code-in-relation-to-SAS-return-code/td-p/205784&lt;/A&gt; )&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A warning may happen due to many reasons, but one of them is that SAS generates warnings that, sometimes are harmless.&lt;/P&gt;
&lt;P&gt;By default, the BatchServer will only exit successfully if the return code is 0, however, it is a general practice to force the Batch Server to change exit codes 1 to 0, precisely to avoid that behaviour on LSF.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;in config/Lev1/SASApp/BatchServer/sasbatch.bat&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;&lt;STRONG&gt;REM remove the REM from the statements below to capture exit=1 (SAS warning) and make it exit=0&lt;/STRONG&gt;
set rc=%ERRORLEVEL% 
if %rc%==1 goto makenormalexit 
exit /b %rc% 
:makenormalexit 
exit /b 0 &lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 27 Nov 2017 08:36:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Customer-Intelligence/Password-change-and-schduler-issue/m-p/416271#M688</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2017-11-27T08:36:09Z</dc:date>
    </item>
  </channel>
</rss>

