During the development and maintenance (life-cycle) process of SAS macros, especially while they are already used for production purposes, it is very much recommended to keep a history of changes, additions and bug fixes along with the macro version number. Archiving of the production SAS program code should include the applied macro version or at least the applied macro version number. That way the code can be used for reproduction purposes. Newer versions of a macro should be as much as possible backwards compatible. Then a newer version may replace an older version when running reproduction SAS programs.
Did you find this white paper useful?
9 out of 19 users found this white paper useful
Related white papers
Introduction to the FileConnection API
This paper describes the FileConnection API. It also includes a brief description of the example MIDlet that is included in this package and additional details about the API implementation in...
2007 Comparative Assessment Methodology Process for BPEL
By following the BPEL standard, the choice of which BPEL engine to use should not affect interoperability of the orchestrated services or the reuse of the BPEL models or designs....
Setting Up and Using Bluetooth Hardware With Development Tools
The purpose of this paper is to describe how to set up the Bluetooth testing environment for the C++ emulators of Software Development Kits (SDK), such as the Series 60...
Building a Robust Linux Kernel Piggybacking the Linux Test Project
The Linux kernel is growing at a rapid rate and runs across many architectures and platforms; ensuring that the kernel is reliable, robust and stable is very critical. The Linux...
MSDN Webcast: Unit Testing for Mobile Devices (Level 300)
With Microsoft Visual Studio 2008, unit testing is now available for mobile device developers as well. The presenter of this webcast explores unit testing for devices. The attendee will learn...
Introduction to Dependency Injection With Microsoft Enterprise Library Unity Application Block
This webcast introduces the Microsoft Enterprise Library Unity Application Block - a lightweight, extensible dependency injection container with support for constructor, property, and method call injection. Dependency injection is a...
Taking Advantage of Microsoft Enterprise Library 4.0 for Visual Studio 2008
Microsoft Enterprise Library is a collection of reusable software components (application blocks) designed to assist software developers with common enterprise development challenges (such as logging, validation, exception handling, and many...
