13.07.2015 Views

SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

824 Publishing <strong>SAS</strong> Formats 4 Chapter 28Interaction: If ACTION=CREATE or ACTION=DROP is specified, messages arewritten to the <strong>SAS</strong> log that indicate the success or failure of the table creationor drop.ACTION=CREATE | REPLACE | DROPspecifies that the macro per<strong>for</strong>ms one of these actions:CREATEcreates a new <strong>SAS</strong>_PUT( ) function.REPLACEoverwrites the current <strong>SAS</strong>_PUT( ) function, if a <strong>SAS</strong>_PUT( ) function isalready registered or creates a new <strong>SAS</strong>_PUT( ) function if one is notregistered.DROPcauses the <strong>SAS</strong>_PUT( ) function to be dropped from the Teradata database.Interaction: If FMTTABLE= is specified, both the <strong>SAS</strong>_PUT( ) function andthe <strong>for</strong>mat table are dropped. If the table name cannot be found or isincorrect, only the <strong>SAS</strong>_PUT( ) function is dropped.Default: CREATE.Tip: If the <strong>SAS</strong>_PUT( ) function was defined previously and you specifyACTION=CREATE, you receive warning messages from Teradata. If the<strong>SAS</strong>_PUT( ) function was defined previously and you specifyACTION=REPLACE, a message is written to the <strong>SAS</strong> log indicating that the<strong>SAS</strong>_PUT( ) function has been replaced.MODE=PROTECTED | UNPROTECTEDspecifies whether the running code is isolated in a separate process in theTeradata database so that a program fault does not cause the database to stop.Default: PROTECTEDTip: Once the <strong>SAS</strong> <strong>for</strong>mats are validated in PROTECTED mode, you canrepublish them in UNPROTECTED mode <strong>for</strong> a per<strong>for</strong>mance gain.OUTDIR=diagnostic-output-directoryspecifies a directory that contains diagnostic files.Files that are produced include an event log that contains detailed in<strong>for</strong>mationabout the success or failure of the publishing process.See: “Special Characters in Directory Names” on page 825Tips <strong>for</strong> Using the %INDTD_PUBLISH_FORMATS Macro3 Use the ACTION=CREATE option only the first time that you run the%INDTD_PUBLISH_FORMATS macro. After that, use ACTION=REPLACE orACTION=DROP.3 The %INDTD_PUBLISH_FORMATS macro does not require a <strong>for</strong>mat catalog. Topublish only the <strong>for</strong>mats that <strong>SAS</strong> supplies, you need to have either no <strong>for</strong>matcatalog or an empty <strong>for</strong>mat catalog. You can use this code to create an empty<strong>for</strong>mat catalog in your WORK directory be<strong>for</strong>e you publish the PUT function andthe <strong>for</strong>mats that <strong>SAS</strong> supplies:proc <strong>for</strong>mat;run;3 If you modify any PROC FORMAT entries in the source catalog, you mustrepublish the entire catalog.

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

Saved successfully!

Ooh no, something went wrong!