07.08.2013 Views

SAS 9.1.3 Intelligence Platform: System Administration Guide

SAS 9.1.3 Intelligence Platform: System Administration Guide

SAS 9.1.3 Intelligence Platform: System Administration Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

204 Further Resources R Chapter 20<br />

Further Resources<br />

<strong>SAS</strong>-config-dir\Lev1\<strong>SAS</strong>Main\BatchServer\sasbatch<br />

As a default, jobs that are deployed from <strong>SAS</strong> Data Integration Studio are run using<br />

this script.<br />

If you are not using this script, then the <strong>Platform</strong> scheduling server will report your<br />

<strong>SAS</strong> jobs as completing with a status of Exit instead of Done. This occurs because<br />

<strong>Platform</strong> scheduling servers treat any non-zero exit code as Exit instead of Done.<br />

To resolve this issue, you can use the sasbatch script that was created by the <strong>SAS</strong><br />

Configuration Wizard. If you are using a different script, you can modify the script so<br />

that it uses a job starter. A job starter is similar to an automatic job wrapper and is<br />

responsible for starting the task.<br />

To use a job starter on Windows installations, modify your script as follows:<br />

call sas.bat %*%<br />

set rc=%ERRORLEVEL%<br />

if %rc==1 goto makenormalexit<br />

exit %rc<br />

:makenormalexit<br />

exit 0<br />

To use a job starter on UNIX installations, modify your script as follow:<br />

sas $*<br />

rc=$?<br />

if [ $rc -eq 1 ]; then<br />

exit 0<br />

else<br />

exit $rc<br />

fi<br />

For additional information about managing job submissions, see the white paper<br />

Implementing Site Policies for <strong>SAS</strong> ® Scheduling with <strong>Platform</strong> JobScheduler at http:/<br />

/support.sas.com/documentation/whitepaper/technical/JobScheduler.pdf.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!