《SAS入门宝典》：轻松学习SAS软件基础

需积分: 10 183 浏览量更新于2024-07-25 收藏 13.77MB PDF 举报

"SAS经典教材：THE LITTLE SAS BOOK，一本适合初学者的SAS编程指南，涵盖了SAS软件最常用的特性，包括Output Delivery System的概念、PRINT、REPORT和TABULATE过程中的STYLE=选项，以及ODS HTML、RTF、Printer和Output目的地等内容。" 《THE LITTLE SAS BOOK》是SAS编程的入门级教材，由Lora D. Delwiche和Susan J. Slaughter撰写。这本书以其友好的阅读体验和简洁易懂的方式，引导读者逐步了解SAS软件的核心功能。第四版在原有的基础上增加了对SAS最新特性的介绍，如Output Delivery System（输出传递系统），这是一个用于管理和格式化SAS程序输出的重要工具，使得用户可以自定义报告样式和输出格式。书中深入浅出地讲解了如何使用PRINT、REPORT和TABULATE等过程，这些过程在数据处理和报表生成中极为常见。特别是STYLE=选项的介绍，它允许用户在这些过程中自定义输出的样式，如字体、颜色、布局等，极大地提升了报告的专业性和可读性。此外，书中还涵盖了ODS（Output Delivery System）的不同目的地，如HTML、RTF、Printer和Output。ODS系统使得SAS输出能以不同的格式保存或打印，例如HTML适合网页分享，RTF支持丰富的文本格式，而Printer则直接对应打印机输出。这些特性让SAS用户能够灵活地根据需求选择合适的输出方式。书中的内容不仅限于基础的编程语法，还包括了版权信息、使用条款以及对美国政府用户的特定限制。尽管这些部分不涉及具体的技术知识，但它们是理解合法使用该教材和SAS软件的重要组成部分。《THE LITTLE SAS BOOK》是一本全面且实用的SAS学习资料，尤其适合初次接触SAS的读者。通过本书，读者可以迅速掌握SAS的基本操作，并为进一步深入学习和应用SAS打下坚实的基础。无论是在学术研究、数据分析还是企业项目中，SAS都是一种强大的工具，而这本书正是开启SAS之旅的理想伙伴。

Introduction xv

6.2, 6.4 Name prefix and numbered range data set lists for specifying lists of data set

names in SET or MERGE statements

9.2, 9.4 Support for JMP, Paradox, Stata, and SPSS files in the Export Wizard and PROC

EXPORT

10.9 PUTLOG statement writes to the SAS log even if a FILE statement is in the

DATA step

Also new with this edition

Section Feature

2.8 ANYDTDTE. informat allows for reading data with mixed date styles in a single

variable

2.16 DATAROWS= statement for delimited files in PROC IMPORT tells which row

in the file contains the first data row

2.16 GUESSINGROWS= statement for delimited files in PROC IMPORT tells how

many rows to use to determine variable types

2.17 RANGE= statement for Microsoft Excel files in PROC IMPORT specifies what

part of the sheet contains the data

2.22 LABEL= data set option specifies a label for the data set

3.3 ANYALNUM, ANYALPHA, ANYDIGIT, ANYSPACE, CAT, CATS, CATX,

COMPRESS, INDEX, PROPCASE, and TRANWRD character functions

3.4 N and NMISS numeric functions and WEEKDAY, YEAR, and YRDIF date

functions

3.12 Name prefix variable lists for specifying lists of variable names all starting with

the same characters

4.3 DUPOUT= option in PROC SORT specifies a data set to contain the duplicate

observations eliminated when the data are sorted

4.22 Compute blocks in PROC REPORT for calculating new variables to appear in

PROC REPORT output

4.23 Grouping data in procedures with user-defined formats

5.4, 5.5, 5.6 ODS NOPROCTITLE statement tells SAS not to include procedure titles in ODS

output

5.5, 5.6 ODS STARTPAGE= option controls where page breaks are added to ODS

output

6.13 WHERE= data set option to control which observations are processed when

reading or writing data sets

10.6 ?? format modifier suppresses the invalid data message in the SAS log if SAS

encounters invalid data for the variable

The Little SAS Book

1.1 The SAS Language

Many software applications are either menu driven, or command driven (enter a command⎯see

the result). SAS is neither. With SAS, you use statements to write a series of instructions called a

SAS program. The program communicates what you want to do and is written using the SAS

language. There are some menu-driven front ends to SAS, for example SAS Enterprise Guide

software, which make SAS appear like a point-and-click program. However, these front ends still

use the SAS language to write programs for you. You will have much more flexibility using SAS

if you learn to write your own programs using the SAS language. Maybe learning a new

language is the last thing you want to do, but be assured that although there are parallels

between SAS and languages you know (be they English or JAVA), SAS is much easier to learn.

SAS programs

A SAS program is a sequence of statements executed in order. A statement

gives information or instructions to SAS and must be appropriately placed in the program. An

everyday analogy to a SAS program is a trip to the bank. You enter your bank, stand in line, and

when you finally reach the teller’s window, you say what you want to do. The statements you

give can be written down in the form of a program:

I would like to make a withdrawal.

My account number is 0937.

I would like $200.

Give me five 20s and two 50s.

Note that you first say what you want to do, then give all the information the teller needs to

carry out your request. The order of the subsequent statements may not be important, but you

must start with the general statement of what you want to do. You would not, for example, go

up to a bank teller and say, “Give me five 20s and two 50s.” This is not only bad form, but would

probably make the teller’s heart skip a beat or two. You must also make sure that all the

subsequent statements belong with the first. You would not say, “I want the largest box you

have” when making a withdrawal from your checking account. That statement belongs with “I

would like to open a safe deposit box.” A SAS program is an ordered set of SAS statements like

the ordered set of instructions you use when you go to the bank.

SAS statements

As with any language, there are a few rules to follow when writing SAS

programs. Fortunately for us, the rules for writing SAS programs are much fewer and simpler

than those for English.

The most important rule is

Every SAS statement ends with a semicolon.

This sounds simple enough. But while children generally outgrow the habit of forgetting the

period at the end of a sentence, SAS programmers never seem to outgrow forgetting the

semicolon at the end of a SAS statement. Even the most experienced SAS programmer will at

least occasionally forget the semicolon. You will be two steps ahead if you remember this simple

rule.

Chapter 1: Getting Started Using SAS Software 3

Layout of SAS programs

There really aren’t any rules about how to format your SAS

program. While it is helpful to have a neat looking program with each statement on a line by itself

and indentions to show the various parts of the program, it isn’t necessary.

♦ SAS statements can be in upper- or lowercase.

♦ Statements can continue on the next line (as long as you don’t split words in two).

♦ Statements can be on the same line as other statements.

♦ Statements can start in any column.

So you see, SAS is so flexible that it is possible to write programs so disorganized that no one can

read them, not even you. (Of course, we don’t recommend this.)

Comments

To make your programs more understandable, you can insert comments into your

programs. It doesn’t matter what you put in your comments⎯SAS doesn’t look at it. You could put

your favorite cookie recipe in there if you want. However, comments are usually used to annotate

the program, making it easier for someone to read your program and understand what you have

done and why.

There are two styles of comments you can use: one starts with an asterisk (*) and ends with a

semicolon (;). The other style starts with a slash asterisk (/*) and ends with an asterisk slash (*/).

The following SAS program shows the use of both of these style comments:

* Read animals’ weights from file;

DATA animals;

INFILE ’c:\MyRawData\Zoo.dat’;

INPUT Lions Tigers;

PROC PRINT DATA = animals; /* Print the results */

RUN;

Since some operating environments interpret a slash asterisk (/*) in the first column as the end of a

job, be careful when using this style of comment not to place it in the first column. For this reason,

we chose the asterisk-semicolon style of comment for this book.

Programming tips

People who are just learning a programming language often get frustrated

because their programs do not work correctly the first time they write them. Writing programs

should be done in small steps. Don’t try to tackle a long complicated program all at once. If you

start small, build on what works, and always check your results along the way, you will increase

your programming efficiency. Sometimes programs that do not produce errors are still incorrect.

This is why it is vital to check your results as you go even when there are no errors. If you do get

errors, don’t worry. Most programs simply don’t work the first time, if for no other reason than

you are human. You forget a semicolon, misspell a word, have your fingers in the wrong place on

the keyboard. It happens. Often one small mistake can generate a whole list of errors. If you build

your programs piece by piece, programs are much easier to correct when something goes wrong.

剩余351页未读，继续阅读

kaiKdk

粉丝: 0
资源: 2

《SAS入门宝典》：轻松学习SAS软件基础

The-little-SAS-book(中文版).pdf

The Little SAS Book (Fourth Edition)

SAS软件入门：The Little SAS Book 学习笔记

SAS编程入门：The Little SAS Book 中文指南

SAS初学者指南：The Little SAS Book第三版简介

SAS编程基础：《The Little SAS Book》中文版概览

SAS 经典教程 MIT 统计课程推荐 the little sas book

The little sas book

The little Sas Book

the little SAS book

最新资源