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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Using an Operating <strong>System</strong> Scheduling Server R How Operating <strong>System</strong> Scheduling Works on UNIX <strong>System</strong>s 215<br />

3 Execute the generated script flowname.bat. The file is located in the following<br />

path:<br />

outdir\XMLFlowDef-name\flow-name<br />

Either double-click the filename in Windows Explorer, or execute it from a<br />

command prompt.<br />

3 Use the Windows Task Scheduler to manually schedule the script. To access the<br />

Task Scheduler, select Scheduled Tasks on the Control Panel. On XP and newer<br />

systems, you can also use the schtasks command line interface to surface many<br />

functions of the Task Scheduler.<br />

3 Use the at command to manually schedule the script. The capabilities of this<br />

command are more limited than those of the Task Scheduler. See your operating<br />

system documentation for details.<br />

Canceling a Scheduled Flow on a Windows Operating <strong>System</strong><br />

Scheduling Server<br />

If you need to cancel a flow that has been scheduled on Windows, you can do either of<br />

the following:<br />

3 Use the Windows Task Scheduler to cancel the job.<br />

3 Use the /del option of the at command. You can use this method only if the job<br />

was submitted with the at command.<br />

After a scheduled flow has been canceled, you can remove the script that was created<br />

for the flow.<br />

Using Operating <strong>System</strong> Scheduling on UNIX <strong>System</strong>s<br />

Limitations of UNIX Operating <strong>System</strong> Scheduling Servers<br />

On UNIX operating system scheduling servers, <strong>SAS</strong> <strong>9.1.3</strong> Service Pack 3 supports<br />

the scheduling of flows that have a single time event as a trigger. Flows can contain<br />

multiple jobs, but the individual jobs cannot have dependencies. The jobs in a flow are<br />

executed serially.<br />

If you schedule a flow to run on a date and time that has already passed, Schedule<br />

Manager creates a script. However, the script is not submitted for execution, and an<br />

error message similar to the following is written to the log:<br />

One or more flows were not successfully scheduled.<br />

NOTE: The <strong>SAS</strong> <strong>System</strong> stopped processing this step<br />

because of errors.<br />

This behavior is consistent with UNIX operating system scheduling.<br />

How Operating <strong>System</strong> Scheduling Works on UNIX <strong>System</strong>s<br />

When you schedule a flow using a UNIX operating system scheduling server,<br />

Schedule Manager creates the following files:<br />

3 a flow command script called flowname.sh<br />

3 a log for the submitted script, called flowname.log

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

Saved successfully!

Ooh no, something went wrong!