In the third quarter of 2016, a new appendix entitled "Macro Examples" was added to the SAS 9.4 Macro Laguage: Reference document. There are 17 programs with descriptions for you to use. You can view the new appendix online at support.sas.com/documentation.   Here's a list of what you'll find:   Example 1: Import All CSV Files That Exist within a Directory Example 2: List All Files within a Directory Including Subdirectories Example 3: How to Increment a Macro DO Loop by a Non-integer Value Example 4: How to Use Character Values on a Macro %DO Loop Example 5: Place All SAS Data Set Variables into a Macro Variable Example 6: How to Retrieve the Program Name That Is Currently Running in Batch Mode or Interactively Example 7: Using a Macro to Create New Variable Names from Variable Values Example 8: Dynamically Determine the Number of Observations and Variables in a SAS Data Set Example 9: Use Macro Logic to Determine If an External File Is Empty Example 10: Retrieve Each Word from a Macro Variable List Example 11: Loop through Dates Using a Macro %DO Loop Example 12: Using Macro Variables within a CARDS or DATALINES Statement Example 13: Print Information to the Output Window If a Data Set Is Empty Example 14: Create a Quoted List Separated by Spaces Example 15: Delete a File on UNIX or Windows If It Exists Example 16: Retrieve the File Size, Create Time, and Last Modified Date of an External File Example 17: Delete All User-defined Macro Variables ... View more

An error was reported in the SAS/ACESS 9.4 Interface to PC Files: Reference. The error is in the GETNAMES= definition on page 73 in the current PDF. To correct the error, the following change will be in the next document release.   GETNAMES=YES | NO   determines whether to generate SAS variable names from the data values in the first row of the imported file. If the data value in the first row is read and it contains characters that are not valid in a SAS name (such as a blank), SAS converts the character to an underscore.   For example, the data value Occupancy Code becomes Occupancy_Code.     ... View more

An error was reported in the “INTO Clause” dictionary entry in the SAS Macro Language: Reference. In the following example, the log output should have quotation marks:   Example 3: Storing Values of All Rows in One Macro Variable   This example stores all values of the column (variable) STYLE in the macro variable TYPES and separates the values with a comma and a blank.   proc sql;    select distinct quote(style)       into :types separated by ', '       from sasuser.houses; %put Types of houses=&types.;   When this program executes, this line is written to the SAS log:   Types of houses=CONDO, RANCH, SPLIT, TWOSTORY   The log output should have quotation marks:   Types of houses="CONDO   ", "RANCH   ", "SPLIT   ", "TWOSTORY"   The documentation will be corrected in the next SAS software release.     ... View more

If a macro language element is created for a specific product, it will not be documented in the SAS Macro Language Reference or supported by the SAS Macro Facility. Lately, the %TSLIT macro function has been discussed in the SAS Communities because the documentation refers the customer to the SAS Macro Language Reference. The %TSLIT macro function was created for the DS2 and FEDSQL procedures. Beginning in SAS 9.4m3, documentation for %TSLIT will be located in the SAS 9.4 FedSQL Language Reference, and SAS 9.4 DS2 Language Reference. ... View more