HOME
QUICK SEARCH
AUTHORS
KEYWORDS
HELP
BUGSSCSUG 1999 Papers - Index
30 papers. Source: SCSUG (South-Central SAS Users Group) conference proceedings.
| # | Title× | Authors× | Abstract× | Keywords× | Extras | Pages |
|---|---|---|---|---|---|---|
| 1 | 40,153,273,652 | Charles Hopf, H. W. Barry Merrill |
40,153,273,652 is a/arge number to most people (even congressmen.) If it is the number of bytes of SMF data produced by a single complex in a single day, it can be frightening to think about processing. How long will it take and are there ways to reduce the time? | elapsed time, cpu time, macro variable, data step, dataset, if-then-else | 18 | |
| 2 | Advanced Features of PROC TABULATE | Thomas J. Winn Jr. | The goal of this paper is to provide participants with pl'll.clical information regarding some advanced features of PROC TABULATE. It will include a review of the basic syntax for PROC TABULATE. The paper also will cover methods for customizing the appearance of tables generated by PROC TABULATE (fonnatting, modifying table outlining charactars, removing separator lines, changing headings, end changing the width of cells), for using PROC TABULATE to compute and to display percentages and other quotients, and for using PROC TABULATE for displaying statistical results |
proc tabulate, proc step, class variable, proc freq, missing value, proc means, if-then-else | 6 | |
| 3 | Advanced Macro Processing | Destiny Corporation (a company) | macro variable, call symput, proc step, symbol table, dataset, macro loop, macro definition, proc append, proc sql, if-then-else, %if-%then-%else | 9 | ||
| 4 | An Introduction to Gibbs Sampling | Scott Burk | "Computer-intensive algorithms, such as the Gibbs sampler, have become increasingly popular statistical tools, both in applied and theoretical work." (Casella and George) (1992). The presentation was based upon two papers on Gibbs sampling. The presentation included a basic example of what the Gibbs sampler does and why, with a computer illustration done in SAS/IML. The Gibbs sampler is an iterative technique to compute a marginal based on the conditionals. A sample point from the marginal can be obtained without knowing the marginal itself by sequencing through the conditionals of the distribution. This cycling is a Markov process and requires convergence. This cycling was shown to converge (for the discrete case) using Markov chains. What is Gibbs sampling? Gibbs Sampling is an iterative technique that computes sample points from an unknown marginal distribution. The algorithm is very computer intensive and thus with the advent of high speed computers is gaining a large following |
sample, markov chain, binomial distribution | 9 | |
| 5 | Basic Macro Processing | Destiny Corporation (a company) | macro variable, macro facility, macro call, macro definition, macro put, proc step, &variable, symbol table, keyword parameter, macro parameter, %macro parameters, macro quoting function | 6 | ||
| 6 | Basic PROC TABULATE | Destiny Corporation (a company) | proc tabulate, proc step, label statement | 21 | ||
| 7 | Basic SQL Processing | Destiny Corporation (a company) | proc step, order by, select, proc sql, proc print, where statement, proc sort | 5 | ||
| 8 | But Our Office Isn't Paperless ... Can I Get All Those Nifty Styles Too?, or Using ODS to Create High-Quality Hardcopy in SAS Version 8 | Brian T. Schellenberger | proc step, proc report, output delivery system, proc template, proc standard, proc tabulate | 10 | ||
| 9 | Capacity and Policy Planning Using a Simulation Model | George Tompkins | Discrete event simulation models coupled with statistical analysiS allow you to select a system design or resource configuration with a high degree of certainty. This paper Introduces discrete event simulation and demonstrates the use of response surtace methodology to select a resource configuration. The example system Is kept intentionally generic to emphasize the applicability of this methodology in meny different industries | regression analysis, proc means | 4 | |
| 10 | Data Manipulation and Report Writing Techniques | Julie Wallace | SAS provides a variety of procedures for producing standard reports. Alternatively, SAS provides the flexibility to allow a programmer full control in order to construct tailored reports. This paper illustrates a program that starts with a SAS dataset, manipulates the data to form a file with the appropriate variables and summary levels, and ends with a null DATA STEP which writes a report. The program applies SAS techniques such as arrays, macro variables, dataset indexing, nested do loops, and various PUT statement arguments. The FORMAT, SQL, TRANSPOSE, and REPORT procedures are also used |
proc report, proc step, dataset, data step, do loop, macro variable, put statement, if-then-else, class variable, sample, by group processing, proc sql | 10 | |
| 11 | Debugging SAS Macros, Revised | Thomas J. Winn Jr. | The SAS macro facility Is a powerful tool which greaUy enhances the functionality and flexibility of the SAS programming language. However, the complexity of programming code which uIIlizes SAS macro language statements sometimes also makes it difficult to debug. The SAS System includes some programming statements and options which can be used in the process of correcting code that is not working properly. This Morial will describe a strategy for using the MPRINT, MLOGIC and SYMBOLGEN options, as well as %PUT statements, for debugging purposes, Including examples of the interpretation of diagnostic messages pertaining to the macro facility. It is a 1999 revision of a paper which appeared In the 1994 SCSUG Conference Proceedings, and also in the (1995) SUGI 20 Conference proceedings |
macro variable, sas log, macro facility, options statement, proc step, macro call, error message, macro definition, &variable, put statement, macro put, macro debugging | 7 | |
| 12 | Defining Test Data Using Population Analysis | Clarence W. Jackson | Defining test data that provides complete test case coverage requires the tester to accumulate data that will satisfy all of the test cases in the requirements. Having access to production data eases the accumulation somewhat, but then any smart tester knows that testing should not be done in the production data. The next best situation is to completely copy production data, but this can be expensive depending on the size of the files and the amount of testing being committed. Another option would be to build test data based on the requirements, which mayor may not match the varied data found in production data. This paper proposes using population analysis of production data as a tool to defining test data coverage. The tools available to provide statistical analysis, such as frequency of data element values and percentages to the total population, will provide measurable verification of the test data to the production data, ensuring better results of testing scenarios | proc freq, proc step | 5 | |
| 13 | Functions in SAS | Destiny Corporation (a company) | index, character functions, sum, proc step, sample | 3 | ||
| 14 | Grab Your Tokens, Here Comes the Macro Train | Mark MacMullen | Do you know the four classes of tokens recognized by the SAS word scanner? Do you understand how SAS handles tokenization of program text with the Word ScanneJ? Do you know what tokens trigger the Macro Processor to begin I1l11lling? This paper will address the process of compilation and execution of SAS programs frOD,1 the Input Stack to the Compiler and the role of the Macro Processor and the Symbol Table plays for macro processing in conjunction with tokenization. SAS users beginning to exploit the power of macros need to understand the tokenization that takes place during SAS execution. Comprehension of how the SAS Word Scanner divides program text into essential units called tokens helps to simplify writing and deciphering macro code. Whether you're starting out writing macrocode or supporting an existing application, this presentation will be of assistance to you | macro facility, macro variable, symbol table, macro definition | 4 | |
| 15 | How to Use the DATA Step Debugger | S. David Riba | All SASe programmers, no matter if they are beginners or experienced gurus, share the need to debug their programs. Many techniques have been suggested over the years to solve the problem of debugging DATA STEP logic. Until now SAS programmers have never been able to interactively watch the DATA STEP execute and debug their logic as it executes. Introduced in Release 6.11 of SAS, the DATA STEP Debugger is part of Base SAS software. It is an interactive tool that allows the SAS user the ability to watch and control DATA STEP execution. The DATA STEP Debugger can be used to: :. watch program logic execute .:. examine variable values as they change .:. repeat program statements .:. jump to other sections of the DATA STEP .:. modify DO loops interactively .:. test for "dead" code .:. give commands :. observe the results interactively The DATA STEP Debugger is a very useful tool, whether you are a Beginning SAS Programmer or a SAS veteran |
sas log, sas base, options statement, macro variable, end | 9 | |
| 16 | Introduction to Using PROC SQL | Thomas J. Winn Jr. | This Morial presentation will explain the basic syntax of the SOL Procedure. PROC SOL is the SAS System's implementation of Structured Ouery Language, which is used for retrieving and updating data in relational tables and databases. PROC SOL also has substantial data manipulation and summarization capabilities. PROC SOL statements could be used to replace much traditional SAS code (DATA STEP, PROC SORT, and PROC MEANS steps), resulting in less programming time and greater computer efficiency. Most of the illustrative examples in this presentation pertain to DB2 tables which are used for tax administration purposes at the author's agency. The principles underlying each example should transfer readily to other settings |
proc step, order by, proc sql, where statement, group by, relational database, select, dataset, inner join, full join, create table, create view, right join, view | 7 | |
| 17 | Leveraging Your Mainframe Investment: Web-Enable Your Mainframe Applications Using New Features of Versions 7 and 8 | Kevin Bestelmeyer, David Crow, Denise M. Poll |
Kevin Bestelmeyer, David Crow, and Denise Poll, SAS Institute Inc., Cary, NC The Web is here. Mainframe applications that were designed as batch applications, or for display on 3270 terminals may seem a long way from being Web enabled, but in many cases, a smaIl effort can pay huge dividends in both the appearance and the utility of these mission-critical applications. This paper looks at some ways to use new features of SAS Versions 7 and 8 to achieve this goal | output delivery system, if-then-else, sas output, proc step | 12 | |
| 18 | Longitudinal Data Techniques | Ronald P. Cody | proc step, proc freq, by group processing, lag function, longitudinal data, retain, set statement, proc means | 6 | ||
| 19 | Normalization of Peak Demand for an Electric Utility Using PROC Model | J. Mark Harris, Jeff Brown, Mark Gilbert |
Mark Harris, Jeff Brown, and Mark Gilbert* Central and South West Services, Inc. Tulsa, Oklahoma This paper discusses the isolation of abnormal events and corresponding impact on annual peak: electricity demand, termed peak normalization in the electric utility industry. The primary drivers of peak electricity demand are weather and its effect on customer heating and cooling units. With tools such as SASIINSIGHT@ and PROC MODEL, an econometric model is defined and incorporated in a Monte Carlo simulation to normalize peak electricity demand in a representative and unbiased manner |
normalization, proc model, monte carlo, proc step, binary variable, covariance | 7 | |
| 20 | ODS for Data Analysis: Output As-You-Like-It in Version 7 | Christopher R. Olinger, Randall D. Tobias |
This paper discusses advances made in the output generated by all Version 7 SAS Software procedures. New features provided by the Output Delivery System (ODS) include automatic rendering of procedure output in HTMl for the web, rich-text, Postscript or PCl format, output data sets from any printed output, and the ability to edit the look and feel of most output. ODS also supporls all legacy line-mode printing and supports a document feature to allow post-procedure replaying of output. This talk introduces ODS features to be delivered in Version 7 and provides some concrete examples of how data analysts and statisticians can take advantage of the feature set provided by ODS. Motivation Every SAS user knows and loves the listing file, the vehicle for all printed SAS output for more than two decades. While familiar, the listing file has its limitations. For starters, output is restricted to monospace fonts only |
20 | ||
| 21 | Programming with the Output Delivery System in Version 7 | Destiny Corporation (a company) | output delivery system, proc step, proc template, proc freq, ods html | 6 | ||
| 22 | Running SAS Applications on the Web | Destiny Corporation (a company) | sample | 4 | ||
| 23 | So Many PROCs, So Little Time: A Primer of Efficient Report Writing in Base SAS | Debbie Buck | Almost any report can be generated in at least two ways using SAS software, and almost every report can be written using the DATA STEP report writing capabilities (using the FILE-PRINT mode), but why reinvent the wheel if a PROC already exists that will give you the desired report with a minimal amount of effort? This presentation will explore various common types of reports and what factors you should consider in deciding which procedure is best suited to your needs. It is not meant to be a detailed guide about PROC statement coding, but rather a guide on how to decide which procedure fits the needs of a given situation. Examples will be presented of differing types of reports with |
proc step, proc print, proc report, sas base, if-then-else | 9 | |
| 24 | Statistics Without DATA _NULLS_ | Michael C. Palmer, Cecilia A. Hale |
Analysts attracted to SAS for its statistical capabilities no longer have to settle for its clumsy publishing capabilities. Instead, they can take advantage of the Output Delivery System (ODS) in version 7.0, SAS's data warehouse and data processing capabilities, and a new open-source, non-proprietary software technology, and literally never use a DATA_NULL_, PROC REPORT, or PROC TABULATE again. An analyst working with publishing software and exploiting its layout and styling flexibility creates a terse sample table. The sample, via SAS programs, directs the retrieval of data from a warehouse and the creation of publishable markup. The publishing software renders the markup publication ready without re-typing, cutting-and-pasting, or format conversion of SAS output. The new, platform independent software technology is eXtensible Markup Language (XML). Statistical analysts and their organizations will better exploit the strengths of SAS and publishing software by coupling the two via |
proc tabulate, sample, data science | 6 | |
| 25 | Taming the Chaos: Managing Large SAS/AF Applications Using Programming Standards and the Source Control Manager of Version 7 of the SAS System | C. Michael Whitney | The use of programming teams offers both advantages and disadvantages when compared with individual programming efforts. The team approach allows a wide range of programming skills and problem-solving perspectives to be applied to a project, and may shorten development time. On the other hand, team developed projects are often marred by differences in programming styles among developers, resulting in inconsistencies in the use of variable names, levels of documentation, and user interface design. Further, without some form of code management, the risk of inadvertently overwriting the work of other team members is always present. All of potential problems can make development and maintanance a chaotic and frustrating experience. This paper will discuss how these problems can be minimized, If not eliminated, by applying some besic programming standards, and by making use of the new Source Code Management system that has been released with SAS version 7 | macro variable, sample | 8 | |
| 26 | UML - The Unified Model Language: What is it, and How can it help the Object-Oriented SAS Developer? | Willy Waks | 10 | |||
| 27 | Using JMP for Technical Analysis of Stocks in Highly Volatile Markets | William R. Gjertsen | We live in a world of high uncertainty. Internet related stocks that appreCiate 300% with no earnings to report have, in some instances,lost 25% in value in the morning and rebound to positive ground before the close! Some day traders are having a field day and are saving the airfare to Las Vegas! Others of us need some sensible rules of when to sell and when to buy. Technical Analysis (I.e. trend lines and OSCillators) when properly tuned can help us establish sensible trading rules. This paper shows how you can generate and test your own trading rules with JMP | moving average, excel | 7 | |
| 28 | Web Publishing of Reports and Graphs | Destiny Corporation (a company) | 7 | |||
| 29 | Y2K Windowed Two Digit Years and When to Use YEARCUTOFF | Clarence W. Jackson | The Y2K situation has caused Information Services Professionals world wide to react to using two digit,years in implied representation of the century. Raw data files in general did not include the full fOur digit representation of the year, programs reading the data would have defective results. Several program and raw data remediation methods have been developed and deployed to correct the problem. Such methods include full expansion of the year data to include the century, and window logic to work around the two digit year data. Full expansion, while the best method that provides the best solutions, is an expensive process, 50 most shops have used window logic to provide the solution. Window logiC allows the raw data to remain in two digit form. Raw data from processes using window logic requires the SAS programmer to use the YEARCUTOFF= option to reliably read the data | raw data, sysdate9 | 4 | |
| 30 | Year 2000 Triage For Your SAS Applications | Mike Kalt | You had every Intention of finishing all of your Year 2000 testing and remediation early and spending January 1 , 2000 lying on the beach. But It's Just a few months before the millennium and you stili haven't tested your SAS applicationsl Even If you don1 have time to do complete testing of all of your SAS applications there are a number of things you can do to find and eliminate potential problems. This paper will discuss the most effective techniques for evaluating your SAS applications and making them compliant in the shortest amount of time. Some of the topics to be covered include: Tools to locate potential problems in your SAS applications What to look for when testing your SAS applications Testing your applications in a Year 2000 environment Using the YEARCUTOFF= option to handle two-digit years | date variable, sysdate9, proc step, dataset, raw data, character variable, excel, data cleaning, proc sql | 7 |
This site serves as a convenient hosting location and does not work as a publisher. All copyrights belong to their respective owners.
The information on this site is provided for general reference purposes only. Whilst every effort is made to ensure that the site is up to date and accurate, no warrant, nor any responsibility or liability for, the accuracy or completeness of the content or for any loss which may arise from reliance on information contained in this site is provided. Links to other sites are provided for your convenience but no responsibility or liability for the content of those sites or of any external site which links to this site is accepted. References to any specific commercial product, process, service, or corporation are also for information only, and do not constitute endorsement, recommendation or favoring.
SAS is a registered trademark of SAS Institute Inc. SAS, Statistical Analysis System, and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration.