(1)
Overview: SAS programmers, particularly consultants, joke about creating job security by creating SAS programs and applications that require long, ongoing maintenance. In all seriousness, though, most people would prefer not to have the ""Security"" of mundane, ongoing maintenance tasks, preferring instead to move on to new development opportunities. While certain ongoing maintenance cannot be avoided, there are techniques that can be utilized to help limit it. This paper describes a number of these techniques, including the use of SAS metadata and dictionary tables, simple and more advanced user input before and during program execution, plus dynamic library and filename referencing
Best Practices for Migrating from Lotus Notes to Microsoft Exchange and SharePoint
Is your business planning a migration from IBM Lotus Notes to Microsoft Exchange and SharePoint? Many companies are...
IDC Complex Event Processing Excerpt
This paper seeks to explain what events are, why they are important to your business, and what the options are for processing and managing these events (depending on their type and volume).
|
