Step 2
|
Migration
Best Practices Migration with PROC MIGRATE: Migrate Files
Special Topic: Migrating ODS Templates
You probably do not want to migrate Output Delivery System (ODS) templates from source to target, because SAS®9 offers updated templates. However, you might need to continue using your user-defined or user-modified templates under a migrated custom SAS application.
To see what templates you have in your source libraries, use the LIST statement. Compare source templates to what is provided in SAS®9 by using the ODS MARKUP utility tagsets NAMEDHTML, STYLE_DISPLAY, and STYLE_POPUP, which help you to see the style settings. You might be able to modify a SAS®9 template instead of recreating the source template in the target environment.
If that is not possible, then you can migrate the source template. The ODS template and the ODS documents registry are examples of an item store. Item stores are covered by PROC MIGRATE with some exceptions. If the exceptions don't apply to you, see the PROC MIGRATE Calculator to find the instructions for your operating environment. If one of the exceptions does apply, you can migrate the template manually. Move the source PROC TEMPLATE code to the target and rerun it. If you no longer have the code, use the SOURCE statement with the FILE= option to save the code to a file:
proc template;
source styles.default / file="default.txt";
run;
Or, after opening the template in the Template Editor window,
you can select File -> Save As. This outputs the code, but nested between
a PROC TEMPLATE statement and a RUN statement.
Be sure to check the log after rerunning PROC TEMPLATE code in the target environment. Also check the formatting that the template creates -- any template that inherits styles from a parent template should now inherit styles from the SAS®9 parent, which might be different from the original parent.
Return to Step 2.
