06-19-2012 03:23 PM
How is output saved from SAS code run in the Process Editor?
There are two modes to run SAS code in the Process Editor
In the Process Editor menu, under Code --> Test, two options are listed:
1. Do Not Save Results (F3) - Program runs and results are not saved in SDD
2. Save Results (Shift + F3) - Program runs and results are saved in SDD
Let’s consider the following code:
libname sddloc "&fldr";
Let’s assume that "&fldr"is defined as FOLDER parameter, the parameter type is OUTPUT and it is referencing a valid location in the SDD instance. (For example "/SDD/SDD
Forum" where SDD and SDD Forum are valid folder names and exists in SDD instance.)
Make sure the Process Editor is the selected Window and submit the above code using Option 1 (Do Not Save Results); the program runs and results are available back in Process Editor. However the dataset mydata is not written to the location referenced by sddloc library.
Run the above code using Option 2 (SaveResults) and the dataset mydata is written to the location referenced by sddloc library.
So if you are trying to execute your code using Option 1 your results, will not be saved in SDD but if you use Option 2 your results will be saved in SDD.
Also, you can save the outputs after a job has been run in “Do Not Save Results” mode by right-clicking the program object in the Results window and selecting “Save Results.”
The automatic parameters in a process (log, lis, sddparms, pgm) are only saved to SDD automatically if a location has been defined for them. This location can be defined by double clicking the parameter name in the Parameter list. Then select “Browse” to select the location in SDD. If a name is not given for the parameter, then the name of the SAS process will be used as the file name for the log, lis, pgm and sddparms files.