SAS 9.1.3 Intelligence Platform: System Administration Guide

Scheduling Jobs from SAS Data Integration Studio R Troubleshooting the Scheduling of SAS Data Integration Studio Jobs 209
You can click New to define a new trigger event, and then select that event
as the trigger; or you can choose one of the job dependencies that you defined
as the trigger. For example, if you specified a time dependency of Mondays at
3:30 for one of the jobs, then you can schedule the entire flow to be started at
this time. After you have scheduled your flow, you can view the flow in the
Platform Flow Manager.
3 If you are using an operating system scheduling server, then you can choose
Run Once (which runs the job immediately), you can choose to run the job
manually, or you can choose to run the job on a recurring basis based on a
time event.
To create a new time event, select New. In the New Time Event dialog box,
enter the start date and time and select the desired recurrence criteria. After
you create the time event, you can select it as the trigger for the flow.
6 Click OK to exit the Schedule Flow dialog box.
Note: If you use both Foundation and custom repositories, then the following
considerations apply:
3 If you deploy a job while you are connected to a dependent custom repository in
SAS Data Integration Studio, then you must log on to the custom repository in
SAS Management Console in order to schedule the job. The job will not be
available for scheduling if you are connected to the Foundation repository.
3 If you deploy a job while you are connected to the Foundation repository in SAS
Data Integration Studio, then you can log on to either the Foundation repository
or a dependent custom repository in SAS Management Console in order to
schedule the job.
R
Troubleshooting the Scheduling of SAS Data Integration Studio Jobs
User credentials play an important role in the scheduling and execution of SAS Data
Integration Studio jobs. When SAS Data Integration Studio deploys a job for
scheduling, it generates a SAS file as the -sysin value for running SAS in batch mode.
Generated SAS programs often contain LIBNAME statements that specify credentials
for the data sources in the library. If an issue occurs in scheduling or executing a SAS
Data Integration Studio job, check to see if one of the following situations has occurred:
3 Has a user’s password changed? If the password has changed, you will need to
either redeploy the job to update the SAS file with the new credentials, or edit the
generated SAS file to update the credentials.
3 Are the specified credentials valid in the scheduling environment? The user who
generated the job might have credentials that are valid in SAS Data Integration
Studio but not in the scheduling environment. If this is true, you will need to
either redeploy the job with the appropriate credentials, or edit the generated SAS
file to update the credentials.
For additional troubleshooting information, see “Resolving Issues Related to Scheduling
With Platform Product Suite for SAS” on page 201.