14.01.2013 Views

SAS 9.3 Guide to Software Updates

SAS 9.3 Guide to Software Updates

SAS 9.3 Guide to Software Updates

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

138 Chapter 21 / <strong>SAS</strong> Data Integration Studio<br />

file will not be moved during the standard migration process. If you execute the job after<br />

migration, an error will appear in the <strong>SAS</strong> log, saying that the transformation could not<br />

access the source code file. To fix the problem, use the operating system <strong>to</strong>ols <strong>to</strong> copy<br />

the source code file <strong>to</strong> the target computer, preserving the direc<strong>to</strong>ry structure, if<br />

possible. Then run the job again. If the transformation fails, review the physical path <strong>to</strong><br />

the file and either change the path on the file system or update the metadata that points<br />

<strong>to</strong> the file.<br />

Similarly, if the metadata for an external file points <strong>to</strong> a file that is s<strong>to</strong>red outside of the<br />

<strong>SAS</strong> configuration direc<strong>to</strong>ry, the file will not be moved during the standard migration<br />

process. If you right-click the metadata for the external file and select Open, a file<br />

does not exist error displays. To fix the problem, manually migrate the file <strong>to</strong> the<br />

target computer and complete the steps described earlier for transformations.<br />

The metadata for a deployed job, such as a job that has been deployed for scheduling,<br />

points <strong>to</strong> a file that contains the code for the job. If you migrate the metadata for a<br />

deployed job, and the metadata is pointing <strong>to</strong> a file that does not exist in the target<br />

environment, then the deployed job will fail. To fix the problem, manually migrate the file<br />

<strong>to</strong> the target computer and complete the steps described earlier for transformations.<br />

However, if the path <strong>to</strong> the source code files in the target environment cannot be the<br />

same as the path was in the old environment, you must update the direc<strong>to</strong>ry definition in<br />

the target environment, and then reschedule all flows that include jobs that use the<br />

updated deployment direc<strong>to</strong>ry definition.<br />

To update direc<strong>to</strong>ry definitions in the target environment:<br />

1 In <strong>SAS</strong> Management Console, right-click Schedule Manager and select<br />

Deployment Direc<strong>to</strong>ries.<br />

2 Edit any outdated deployment direc<strong>to</strong>ry definitions so that they point <strong>to</strong> the location<br />

where you moved the source code files.<br />

To identify jobs that use an updated deployment direc<strong>to</strong>ry definition:<br />

1 In <strong>SAS</strong> Management Console, right-click Schedule Manager and select Manage<br />

Deployed Jobs.<br />

2 In the Manage Deployed Jobs window, right-click the job and select Properties.

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

Saved successfully!

Ooh no, something went wrong!