The SASEFAME Interface Engine
- Overview
-
Getting Started
-
Syntax
-
Details
-
Examples
Converting an Entire Fame Database Reading Time Series from the Fame Database Writing Time Series to the SAS Data Set Limiting the Time Range of Data Creating a View Using the SQL Procedure and SASEFAME Reading Other Fame Data Objects with the FAMEOUT= Option Remote Fame Access Using Fame CHLI Selecting Time Series Using CROSSLIST= Option and KEEP Statement Selecting Time Series Using CROSSLIST= Option and Fame Namelist Selecting Time Series Using CROSSLIST= Option and WHERE=TICK Selecting Boolean Case Series with the FAMEOUT= Option Selecting Numeric Case Series with the FAMEOUT= Option Selecting Date Case Series with the FAMEOUT= Option Selecting String Case Series with the FAMEOUT= Option Extracting Source for Formulas Reading Time Series by Defining Fame Expression Groups in the INSET= Option with the KEEP= Clause Optimizing Cache Sizes with the TUNEFAME= and TUNECHLI= Options
- References
Syntax: SASEFAME Interface Engine
The SASEFAME engine uses standard engine syntax. Table 40.1 summarizes the options used by SASEFAME.
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 Work data base in the SAS log |
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 |