The SASEHAVR Interface Engine

Suppose you see the following warnings in your SAS log:

   libname kgs2 sasehavr "%sysget(HAVER_DATA)"
           start= 19550101 end=19600105
           keep="FCSEED, FCSEEI, FCSEEM, BGSX, BGSM, FXDUSBC"
           group="I01, F56, M02, R30"
           source="JPM,CEN,OMB" ;

   NOTE: Libref KGS2 was successfully assigned as follows: 
         Engine:        SASEHAVR 
         Physical Name: C:\haver
         
   data kgse9;
      set kgs2.haver;
   NOTE: Defaulting to MONTHLY frequency.
   WARNING: Start date (19550101) is not a valid date. 
            Engine is ignoring your start date and using 
            default. Setting the default Haver start date to 7001.
   WARNING: End date (19600105) is not a valid date. 
            Engine is ignoring your end date and using 
            default. Setting the default Haver end date to 10103.
   run;

   NOTE: There were 375 observations read from the data set KGS2.HAVER.
   NOTE: The data set WORK.KGSE9 has 375 observations and 4 variables.

The important diagnostic to note here is the warning message that tells you that the data starts in January of 1970 (Haver date 7001), and ends in March, 2001 (Haver date 10103). Since the specified range falls outside the range of data, no observations are in range. So, the engine uses the default range stated in the warning messages. Change the START= and END= options to overlap the results in data that span from JAN1970 to MAR2001. To view the entire range of selected data, remove the START= and END= options from the LIBNAME statement:

   libname kgs sasehavr "%sysget(HAVER_DATA)"
           keep="FCSEED, FCSEEI, FCSEEM, BGSX, BGSM, FXDUSBC"
           group="I01, F56, M02, R30"
           source="JPM,CEN,OMB" ;

   NOTE: Libref KGS was successfully assigned as follows: 
         Engine:        SASEHAVR 
         Physical Name: C:\haver
         
   data kgse5;
      set kgs.haver;
   NOTE: Defaulting to MONTHLY frequency.
      run;

   NOTE: There were 375 observations read from the data set KGS.HAVER.
   NOTE: The data set WORK.KGSE5 has 375 observations and 4 variables.

In this example, an error about an invalid range is issued:

libname lib1 sasehavr "%sysget(HAVER_DATA)"  freq=Weekly
   start=20060301 end=20060531;
NOTE: Libref LIB1 was successfully assigned as follows: 
      Engine:        SASEHAVR 
      Physical Name: C:\haver
libname lib2 "\\dntsrc\usrtmp\saskff" ;
NOTE: Libref LIB2 was successfully assigned as follows: 
      Engine:        V9 
      Physical Name: \\dntsrc\usrtmp\saskff         
data lib2.wweek;
   set lib1.intwkly;
ERROR: No observations found inside RANGE.
       The valid range for HAVER dates is (610104-1050318).
ERROR: No observations found in specified range.
            keep date m11: ;
         run;

WARNING: The variable date in the DROP, KEEP, or RENAME list 
         has never been referenced.
WARNING: The variable m11: in the DROP, KEEP, or RENAME list 
         has never been referenced.
NOTE: The SAS System stopped processing this step because of errors.
WARNING: The data set LIB2.WWEEK may be incomplete.  
         When this step was stopped there were 0 
         observations and 0 variables.
WARNING: Data set LIB2.WWEEK was not replaced because this step was stopped.

The important diagnostic message is the first error statement which tells you that the range of Haver dates is not valid for the specified frequency. A valid range is one that overlaps the dates (610104–1050318). Removing the range altogether causes the engine to output the entire range of data.

libname lib1 sasehavr "%sysget(HAVER_DATA)"  freq=Weekly;
  
NOTE: Libref LIB1 was successfully assigned as follows: 
      Engine:        SASEHAVR 
      Physical Name: C:\haver

libname lib2 "\\dntsrc\usrtmp\saskff" ;
NOTE: Libref LIB2 was successfully assigned as follows: 
      Engine:        V9 
      Physical Name: \\dntsrc\usrtmp\saskff
         
data lib2.wweek;
   set lib1.intwkly;
   keep date m11: ;
run;

NOTE: There were 2307 observations read from the data set LIB1.INTWKLY.
NOTE: The data set LIB2.WWEEK has 2307 observations and 35 variables.

Since the START= and END= options give day-based dates, it is important to use dates that correspond to the FREQ= option when giving a range of dates, especially with weekly frequencies such as WEEK.1–WEEK.7. Since FREQ=WEEK.4 selects weeks that begin on Wednesday, the start and end dates need to be specified as Wednesday dates.

libname lib1 sasehavr "%sysget(HAVER_DATA)"  freq=Week.4
   start=20050302 end=20050309;
NOTE: Libref LIB1 was successfully assigned as follows: 
      Engine:        SASEHAVR 
      Physical Name: \\tappan\crsp1\haver
title2 'Weekly dataset with freq=week.4 range is small';
libname lib2 "\\dntsrc\usrtmp\saskff" ;
NOTE: Libref LIB2 was successfully assigned as follows: 
      Engine:        V9 
      Physical Name: \\dntsrc\usrtmp\saskff
         
data lib2.wweek;
   set lib1.intwkly;
   keep date m11: ;
run;

NOTE: There were 2 observations read from the data set LIB1.INTWKLY.
NOTE: The data set LIB2.WWEEK has 2 observations and 25 variables.

Giving bad dates (for example, Tuesday dates) for a Wednesday FREQ=WEEK.4 results in the following error:

ERROR: Fatal error in GetDate routine. 
       Remove the range statement or change the START= date to 
       be consistent with the freq=option.
ERROR: No observations found in specified range.

In the next example, six time series are selected by the KEEP= option. Their frequencies are annual, monthly, and quarterly, so when the FREQ=WEEKLY and FORCE=FREQ options are used, a diagnostic appears in the log stating that the engine is forcing the frequency to QUARTERLY for better date alignment of observations. The first selected variable is BALO, which is a quarterly time series and causes the default choice of FREQ to be quarterly.

title1 '***HAVKWC.SAS: KEEP= option tests with wildcards***';

%setup( ets );

 /*----------------*/
 /* Wildcard: *    */
 /*----------------*/

title2 "keep=B*, G*, I*";
title3 "6 valid variables are: BALO BGSM BGSX BPBCA G IUM";
libname lib1 sasehavr 'C:\haver\' keep="B*, G*, I*"
   freq=weekly force=freq;
NOTE: Libref LIB1 was successfully assigned as follows: 
      Engine:        SASEHAVR 
      Physical Name: C:\haver\

data wc;
   set lib1.haver;
WARNING: Earliest Start Date in DLX Database matches QUARTERLY frequency
         better than the specified WEEKLY frequency.
         Engine is forcing the frequency to QUARTERLY for better date
         alignment of observations.
run;

NOTE: There were 221 observations read from the data set LIB1.HAVER.
NOTE: The data set WORK.WC has 221 observations and 7 variables.

Note that the time series IUM is an annual frequency. The attempt to convert to a quarterly frequency produces all missing values in the output range because aggregation produces only missing values when forced to go from a lower frequency to a higher frequency.