Practical Approach to the Stored Compiled Macro Facility
Page 1 of 1
Practical Approach to the Stored Compiled Macro Facility
WHAT IS THE STORED COMPILED MACRO FACILITY?
The stored compiled macro facility (SCMF) is a repository for complied macros. Source code for the macros can be stored in various locations separate from the complied macros. The source code needs to be complied only once and then the complied version can be permanently stored in the SCMF. This differs from an autocall library or other
macros, which must be complied during every SAS session. Permanent compilation is a feature of the stored compiled macro facility. Programs in the SCMF can be run and viewed by multiple users, even if they users have read only access.
Creating a permanent SASMACR catalog saves time in daily production. The compiled macro is in one location, while the source code can be stored anywhere. To ease maintenance, storing source code in one central location is recommended. The source code can be saved in the same directory as compiled macros or in another directory if complete control of the source code is required. The compiled macro and source code are different file types to SAS® so having them in the same directory is not confusing.
ADVANTAGES AND DISADVANTAGES OF THE STORED COMPILED MACRO FACILITY
Advantages:
• No repeated compiling of macro programs that are repeatedly used
• Possibility of displaying the entries in a catalog containing compiled macros saving macro compiling time
• There is no need to save and maintain the source for the macro definition in a different location
• Keeping track of macros is easy
• Storing more then one macro per file
• Compile and Store is faster because there is a decrease in time for searching, %including, compiling and storing in the WORK.SASMACR catalog.
Disadvantage:
• Cannot be moved directly to other operating systems.
• Must be saved and recompiled under new OS at any new location.
Read the entire article in detail in link given below
http://analytics.ncsu.edu/sesug/2006/AP10_06.PDF
The stored compiled macro facility (SCMF) is a repository for complied macros. Source code for the macros can be stored in various locations separate from the complied macros. The source code needs to be complied only once and then the complied version can be permanently stored in the SCMF. This differs from an autocall library or other
macros, which must be complied during every SAS session. Permanent compilation is a feature of the stored compiled macro facility. Programs in the SCMF can be run and viewed by multiple users, even if they users have read only access.
Creating a permanent SASMACR catalog saves time in daily production. The compiled macro is in one location, while the source code can be stored anywhere. To ease maintenance, storing source code in one central location is recommended. The source code can be saved in the same directory as compiled macros or in another directory if complete control of the source code is required. The compiled macro and source code are different file types to SAS® so having them in the same directory is not confusing.
ADVANTAGES AND DISADVANTAGES OF THE STORED COMPILED MACRO FACILITY
Advantages:
• No repeated compiling of macro programs that are repeatedly used
• Possibility of displaying the entries in a catalog containing compiled macros saving macro compiling time
• There is no need to save and maintain the source for the macro definition in a different location
• Keeping track of macros is easy
• Storing more then one macro per file
• Compile and Store is faster because there is a decrease in time for searching, %including, compiling and storing in the WORK.SASMACR catalog.
Disadvantage:
• Cannot be moved directly to other operating systems.
• Must be saved and recompiled under new OS at any new location.
Read the entire article in detail in link given below
http://analytics.ncsu.edu/sesug/2006/AP10_06.PDF
pallav- Posts : 98
Join date : 2012-03-14
Location : Ahmedabad
Similar topics
» SAS Macro: Convert numbers (e.g., 1000) to names (e.g., One thousand)
» Building and Using Macro Libraries
» General SAS Macro Interview Questions
» SAS EG and Stored Processes: 3 Tips for Using Options
» Which SAS procedure changes the name of a permanent format for a variable stored in a SAS data set?
» Building and Using Macro Libraries
» General SAS Macro Interview Questions
» SAS EG and Stored Processes: 3 Tips for Using Options
» Which SAS procedure changes the name of a permanent format for a variable stored in a SAS data set?
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|
Mon Jun 10, 2013 2:57 pm by Admin
» SAS Enterprise Guide: Explore Data before you start Analysing
Mon Jun 10, 2013 2:53 pm by Admin
» Predictive Analytics
Fri May 31, 2013 3:30 pm by Admin
» Creating Frequency Report and Creating User Defined styles in SAS Add-In for Microsoft Office
Tue Oct 23, 2012 2:11 pm by pallav
» Prompted Reports in BI Dashboard
Thu Oct 11, 2012 4:54 pm by kushal
» Free SAS Webinar : Getting Started with SAS Hash Object
Wed Oct 10, 2012 6:08 pm by pallav
» Which SAS procedure changes the name of a permanent format for a variable stored in a SAS data set?
Tue Oct 02, 2012 12:47 am by rajin_kumar@yahoo.com
» What is written to SAS Log?
Tue Oct 02, 2012 12:39 am by rajin_kumar@yahoo.com
» SAS Portal and BI Dashboard: Customizing the Tabs
Tue Oct 02, 2012 12:33 am by kushal