The SASEFAME Interface Engine
- Overview
-
Getting Started
-
Syntax
-
Details
-
ExamplesConverting an Entire Fame DatabaseReading Time Series from the Fame DatabaseWriting Time Series to the SAS Data SetLimiting the Time Range of DataCreating a View Using the SQL Procedure and SASEFAMEReading Other Fame Data Objects with the FAMEOUT= OptionRemote Fame Access Using Fame CHLISelecting Time Series Using CROSSLIST= Option and KEEP StatementSelecting Time Series Using CROSSLIST= Option and Fame NamelistSelecting Time Series Using CROSSLIST= Option and WHERE=TICKSelecting Boolean Case Series with the FAMEOUT= OptionSelecting Numeric Case Series with the FAMEOUT= OptionSelecting Date Case Series with the FAMEOUT= OptionSelecting String Case Series with the FAMEOUT= OptionExtracting Source for FormulasReading Time Series by Defining Fame Expression Groups in the INSET= Option with the KEEP= ClauseOptimizing Cache Sizes with the TUNEFAME= and TUNECHLI= Options
- References
The SASEFAME engine uses standard engine syntax. Table 41.1 summarizes the options used by SASEFAME.
Table 41.1: Summary of LIBNAME libref SASEFAME Statement
|
Option |
Description |
|---|---|
|
CONVERT= |
Specifies the Fame frequency and the Fame technique |
|
WILDCARD= |
Specifies a Fame wildcard to match data object series names within the Fame database |
|
RANGE= |
Specifies the range of data to keep in format ’ddmmmyyy’d – ’ddmmmyyyy’d |
|
INSET= |
Uses a SAS data set named setname and KEEPLIST= fame_expression_group as selection input variables or WHERE= Fame fame_bygroup as selection input for BY variables |
|
CROSSLIST= |
Specifies a Fame crosslist fame_namelist to perform selection based on the crossproduct of two Fame namelists |
|
FAMEOUT= |
Specifies the Fame data object class/type you want output to the SAS data set |
|
DBVERSION= |
Echoes the present version number of the Fame |
|
TUNEFAME= |
Tunes the FAME database engine’s use of memory to reduce I/O in favor of a bigger virtual memory for caching database objects |
|
TUNECHLI= |
Tunes the CHLI database engine’s use of memory to reduce I/O in favor of a bigger virtual memory for caching database objects |