Password change and schduler issue

[Amarnadh]

Dear Team,

My client is SAS CI 6.4 , would like to know the impact of below change procedures

1. Password change procedure (internal & external users)

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.

1. Scheduler issue

After scheduling the campaign in platform process management, the campaigns are fail with exit code1, is any one have solution for this same

 Amarnadh

[JuanS_OCS]

Hello @Amarnadh,

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. 

http://support.sas.com/documentation/cdl/en/mcsecug/63190/HTML/default/viewer.htm#n1kxhdu1ams2rzn180...

http://documentation.sas.com/?docsetId=bisecag&docsetTarget=p0kb2gtnuyjnrnn1hduu5by88u4f.htm&docsetV...

http://support.sas.com/documentation/cdl/en/mcsecug/69854/HTML/default/viewer.htm#aboutum.htm

For third party software:

- LSF https://www.google.nl/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwjJ5oGIq97XA...

- other third party software: please check at the vendor's documentation

Now, for the second question, which is a more specific one, It think you should know that exit code 1 means exit with warnings,  in any operating system ( http://support.sas.com/documentation/cdl/en/hostwin/69955/HTML/default/viewer.htm#n0d8f2zgsbjtqwn1f3... ), as general rule. However, not always ( https://communities.sas.com/t5/Administration-and-Deployment/LSF-exit-code-in-relation-to-SAS-return... )

A warning may happen due to many reasons, but one of them is that SAS generates warnings that, sometimes are harmless.

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.

in config/Lev1/SASApp/BatchServer/sasbatch.bat

REM remove the REM from the statements below to capture exit=1 (SAS warning) and make it exit=0
set rc=%ERRORLEVEL% 
if %rc%==1 goto makenormalexit 
exit /b %rc% 
:makenormalexit 
exit /b 0