HDTenEightyP/NetNews huggingface dataset:
Newsgroups: bit.listserv.sas-l
Date:         Thu, 16 Apr 1992 15:35:54 EDT
Reply-To:     Howard Schreier <HIS@NIHCU.BITNET>
From:         Howard Schreier <HIS@NIHCU.BITNET>
Subject: Re: LAGging arrays

> From:         Mikelis Bickis <BICKIS@SASK.USASK.CA>
>
> The LAG function does not actually 'LAG' observations, but just
> creates a queue, giving on each call the value of the argument on the
> last call.  If the argument is an array, then 'each array element is
> lagged separately'.

The last sentence  is  nearly  verbatim  from  the  V.6  SAS
Language Reference.  I don't understand it.

> However, I can't get the above to work.  If my argument is a subscripted
> array, then the lagging is done as if the all the array elements were
> one long list.  If the argument is an unsubscripted array name, I get
> a syntax error.  Is there some way of lagging array elements separately?

There is one queue or stack for each  instance  of  the  LAG
function  in  the  source  language.   So, if the LAG on the
subscripted array name is inside a DO loop,  there  is  just
one.  If you go with repetition

   LASTX(1) = LAG(X(1));
   LASTX(2) = LAG(X(2));

and so forth, you  get  independent  queues  for  each  such
source  statement.  Macros can of course be used to generate
the statements.

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\   Howard Schreier, U.S. Dept. of Commerce, Washington    /
|    (Using Versions 5.18 & 6.07 under IBM OS MVS/ESA)     |
/   BITNET: HIS@NIHCU          INTERNET: HIS@CU.NIH.GOV    \
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Thu, 9 Apr 1992 10:29:09 EST
Reply-To:     Steve Marcus <SCM@HARVARDA.BITNET>
From:         Steve Marcus <SCM@HARVARDA.BITNET>
Subject:      soundex

there was discussion a while back about the soundex function that is
documented in the changes and enhancements for v6.07. i am trying to
use that function on 6.07.02 for unix and am getting the error that
the function does not exist.

any guesses?

thanks!
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Mon, 13 Apr 1992 14:41:15 EDT
Reply-To:     Howard Schreier <HIS@NIHCU.BITNET>
From:         Howard Schreier <HIS@NIHCU.BITNET>
Subject:      Passwords

Warning:  Flames Ahead.

The  other  day,  I  had  occasion  to   research   password
protection  for  SAS data sets under MVS Version 6.  I found
nothing under data set  options  or  anywhere  else  in  the
Language  Reference  (1st  Ed.).  On  a hunch, I checked the
Procedures Guide (3rd Ed.), although that is not the logical
place  for the subject to be addressed.  However, under PROC
V5TOV6, on p. 644, I found (quote from book):

     As of Release 6.06, Version 6 of  the  SAS  System
     does not support password protection.

In this context (dealing with  Version  5  passwords),  this
reads as a statement of termination.

Of course, what was meant was (my words):

     We were anxious to ship Release 6.06 to users, and
     didn't have time to implement password protection.
     It should be back in a later release.

Indeed,  SAS  Communications,  91Q3  p.  5,  announced  6.07
password protection.

I am disturbed about this for two reasons.  The first is the
development  path  itself.   It seems to me that the *first*
step in building Version X is  to  match  the  features  and
performance  of  Version  X-1.   So,  6.06  should  have had
password protection, even if data set compression,  or  some
other new feature, would have been delayed as a consequence.
Of course, new features sometimes render  existing  features
impractical or irrelevant, but that was not the case here.

My second concern is that the glossy manuals, which will  be
with   us   for  some  time,  are  inadequate  at  best  and
counterproductive at worst.  The only statement on passwords
is  in an obscure location, which is perhaps fortunate since
it is utterly misleading.

I  am  used  to  relying  on  Tech.    Reports   as   manual
supplements.  It's not wonderful, but I accept it for things
like new functions and  added  options.   The  situation  is
different with regard to passwords; the development path and
the original editing decisions have left the primary manuals
seriously  deficient.   Is  this an isolated instance, or is
the problem more general?  Does something need to be done?

My suggestion (seriously) is that SAS Institute should print
and  distribute  self-adhesive  stickers to be placed in the
margins of specific pages of the glossy manuals,  announcing
major changes and enhancements and giving Tech.  Report page
citations.

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\   Howard Schreier, U.S. Dept. of Commerce, Washington    /
|    (Using Versions 5.18 & 6.07 under IBM OS MVS/ESA)     |
/   BITNET: HIS@NIHCU          INTERNET: HIS@CU.NIH.GOV    \
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-Path: <phil@wubios>
X-Mailer: ELM [version 2.3 PL11]
Newsgroups: bit.listserv.sas-l
Date:         Wed, 8 Apr 1992 14:21:14 CDT
Reply-To:     "J. Philip Miller" <phil@WUBIOS.WUSTL.EDU>
From:         "J. Philip Miller" <phil@WUBIOS.WUSTL.EDU>
Subject:      ANCOVA and LSMEANS (fwd)
Comments: To: SAS Mailing List <SAS-L@ohstvma.ircc.ohio-state.edu>

> I am concerned about this because a loose reading of the SAS manual would
> lead on to think that LSMEANS is just an easy way to get classical adjusted
> means in ANCOVA. It is for simple designs. For more complex designs it
> appears to do more than that.
>
Yes, it gives you the results you would have if you had run a totally balanced
experiment.  The argument is that what you are estimating is not a function of
how many are in each cell.  Many researchers do not understand that mean
(raw) income of statisticians is different if you take a random sample of
statisticians or if you take samples of equal size of men and women.

-phil

--
     J. Philip Miller, Professor, Division of Biostatistics, Box 8067
	 Washington University Medical School, St. Louis MO 63110
     phil@wubios.WUstl.edu - Internet  (314) 362-3617 [362-2694(FAX)]
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Tue, 14 Apr 1992 14:21:43 -0400
Reply-To:     multiple@MSHRI.UTORONTO.CA
From:         multiple@MSHRI.UTORONTO.CA
Subject:      SAS...what's that means?
Comments: To: sas-l@vm.utcs.utoronto.ca@grind.utcs.utoronto.ca

SAS users:

I have been using SAS for 1.5 years, but I still don't know what does SAS
stand for or why they have this name.  Could someone tell me?

Thanks.

Kenneth
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Mon, 13 Apr 1992 14:26:27 EST
Reply-To:     Durpee McNeir <ITOG400@INDYCMS.BITNET>
From:         Durpee McNeir <ITOG400@INDYCMS.BITNET>
Subject:      Supplemental libraries in 5.18 to 6.06

We use several of the procedures in the supplemental
libraries in sas 5.18.  In moving to 6.06 we loose the
supplemental libraries.  Does anyone know what would
replace PHREG?


Thanks,

Dupree
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Mon, 6 Apr 1992 18:35:36 EST
Reply-To:     Philip Tejera <TEJERA@BARUCH.BITNET>
From:         Philip Tejera <TEJERA@BARUCH.BITNET>
Subject:      Re: TRANWRD Function

Tranwrd is documented in Technical Report P-222, Changes and Enhancements
to Base SAS Software Release 6.07.

You do not say whether you tried the SAS Help facility, but I find that
Tranwrd is not under character functions in SAS 6.07 under CMS. However,
the function itself works.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Mon, 13 Apr 1992 10:33:00 GMT
Reply-To:     Michael Davis <0002395748@MCIMAIL.COM>
From:         Michael Davis <0002395748@MCIMAIL.COM>
Subject:      Good News From Paradise
Comments: To: Multiple Recipients of List SAS-L <sas-l@uga.cc.uga.edu>

Aloha,

Just a quick note from paradise but I though you fellow SAS-Lers would like
to know that Tech Support announced at the opening session that they will begin
support problem submission and tracking via e-mail.  I hope to find out more
about the restrictions tommorrow.  SI also will use LISTSERV to distribute
notices about problems.

Michael Davis
Paradise (temporarily)
0002395748@mcimail.com
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Delivery-Notice:  SMTP MAIL FROM does not correspond to sender.
X-Envelope-to: sas-l@uga.BITNET
X-VMS-To: IN%"sas-l@uga"
Newsgroups: bit.listserv.sas-l
Date:         Wed, 15 Apr 1992 12:43:00 EST
Reply-To:     KITTY <LOSSMAN@NIEHS.BITNET>
From:         KITTY <LOSSMAN@NIEHS.BITNET>
Subject:      phone number

sorry to send out mail to all.  would vinnie delgobbo please send me
mail or call me (541-2332) or someone who does know his phone number
send it to me.  thanks, grace lossman
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Acknowledge-To: <LEJUS@CUVMB>
Newsgroups: bit.listserv.sas-l
Date:         Tue, 7 Apr 1992 09:49:55 EDT
Reply-To:     lynn jacobsen <LEJUS@CUVMB.BITNET>
From:         lynn jacobsen <LEJUS@CUVMB.BITNET>
Subject:      Re: SAS/GRAPH & PostScript: a fix
Comments: To: "salvatore" <SALUS@CUVMB.BITNET>

thanks for the info.  that is relevant.  sometime back we had figured
out the gprolog stuff (although i use gprolog='2521'x), but i hadn't
quite realized all that grey stuff.

lynn
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Tue, 7 Apr 1992 08:37:30 MST
Reply-To:     BABB@TUCVM8.VNET.IBM.COM
From:         BABB@TUCVM8.VNET.IBM.COM
Subject:      Macro window mystery
Comments: To: sas-l@uga.cc.uga.edu

Jim Stuka asked why his window name with an underscore won't work
under CMS.  This sounds a little like something I've been bitten by in
the past but I'm not sure of the connection.

CMS uses certain special characters for things like character-delete,
line-delete, etc. This goes back to the days of low-function Teletype
terminals and is essentially useless these days but it still exists.
I can't see how CMS could have gotten its hooks into SAS language
parsing but it's possible.

The settings for these special characters can be viewed with the CMS
command QUERY TERMINAL.  The SET or SET TERM command is used to change
the settings.  Note that the settings for XEDIT are different from
those for the CMS virtual machine.

This is just a gut-feel guess but it may be worth checking out.

Bill Babb           \|/
SAS Consultant     --O-- Arizona.
IBM ADSTAR Tucson   /|\
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Office of University Computing
Newsgroups: bit.listserv.sas-l
Date:         Mon, 6 Apr 1992 19:44:23 EST
Reply-To:     "Jim S." <JSTUKAS@IRISHVMA.BITNET>
From:         "Jim S." <JSTUKAS@IRISHVMA.BITNET>
Subject:      Re: Macro Window Mystery - Solved, sort of

Thanks to Linda Neden and Daryl Hoffman, I have gotten my macro window
program working.  The solution/workaround was simply to remove the
underscore from the window name, that is, change add_name to addname.
   Now, can anyone in net world explain WHY this is, and only seemingly
in CMS, but not in TSOland or NeXTworld????


                                           Jim

    Jim Stukas
    User Services                JSTUKAS@IRISHVMA (BITNET)
    University of Notre Dame     jstukas@vma.cc.nd.edu (Internet)
    (219) 239-8292               NeXT mail: stukas@mbolo.cc.nd.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-Path: <phil@wubios>
X-Mailer: ELM [version 2.3 PL11]
Newsgroups: bit.listserv.sas-l
Date:         Wed, 15 Apr 1992 22:13:04 CDT
Reply-To:     "J. Philip Miller" <phil@WUBIOS.WUSTL.EDU>
From:         "J. Philip Miller" <phil@WUBIOS.WUSTL.EDU>
Subject:      e-mail tech support
Comments: To: SAS Mailing List <SAS-L@ohstvma.ircc.ohio-state.edu>

John Sims, the SI staff person who implemented the tech support via e-mail is
taking a well deserved vacation and will not return for a couple of weeks.
Tech support has requested that it not go live with EMITS until John is
around to fix things (he is not a fool like me who still signs on and takes
care of business while on vacation).  When we looked earlier today there
were over 100 requests for registering - he will take care of them when he
returns to Cary.

Sorry for the confusion.

-phil
--
     J. Philip Miller, Professor, Division of Biostatistics, Box 8067
	 Washington University Medical School, St. Louis MO 63110
     phil@wubios.WUstl.edu - Internet  (314) 362-3617 [362-2694(FAX)]
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Queen's University at Kingston
Date: Wednesday, 15 Apr 1992 15:41:53 EDT
From: Jeff Boyd <BOYDJ@QUCDN.QueensU.CA>
Newsgroups: bit.listserv.sas-l
Subject: SUMMARY: SAS 6.07 transport files to DBMSCOPY


Thanks to all who responded. With the suggestions we received and further
experimentation, we seem to have a working export mechanism.

Under SAS 6.07 for SunOS, the V5 engine is not available and it is not
possible to create a V5 dataset to stick into the transport mechanism.
The available engines are V603 and V607 (V606 also, but SAS doesn't see
any difference between V606 and V607).

DBMSCOPY V2.0 doesn't know about V606 or V607; it pre-dates them. It does
know about V603 and V516, but, oddly, not V518 (no difference, perhaps?).

The export engines XPORT (documented) and SASV5XPT (not documented!!) are
available under SAS 6.07.


The experimental procedure:

1) We created a flat dataset, and made V603 and V607 versions of it. It
   had 5 records and 3 variables (one each of integer, string and real).
   The size was kept small so that the results could be eyeballed.

2) Using the mechanism in [dbmstest2.sas] (see below), we created export
   files using the XPORT engine.

3) We repeated step 2 using the SASV5XPT engine.

4) We fed the files into DBMSCOPY V2.0 and attempted to convert them to
   Paradox files.

[dbmstest2.sas]
*;
%let WorkDir=/disk2/jeff/dbmstest;
libname in603 v603 "&WorkDir.";
libname in607 v607 "&WorkDir.";
*;
libname out603 xport "&WorkDir./trans603.sasport";
libname out607 xport "&WorkDir./trans607.sasport";
run;
*;
proc copy in=in603 out=out603;
proc copy in=in607 out=out607;
*;


The results:

1) None of the 4 export files were recognized by DBMSCOPY as being
   "SAS Version 6". All were recognized as being "SAS Version 5". We
   expected that the XPORT files would be Version 6 (or nothing else)
   and that the SASV5XPT files would be Version 5 (or nothing else).

2) After we told DBMSCOPY to treat them as Version 5, all 4 files were
   successfully converted to Paradox files (Paradox read them without
   complaint, and they passed the eyeball test). Variable types were
   preserved.


We have something that seems to work, but there are questions about how
DBMSCOPY V2.0 is handling SAS version recognition. To anyone using
DBMSCOPY V3.0, does it mirror the behaviour described above?


Marina Djurfeldt and Jeff Boyd
Case Mix Research
Queen's University
Kingston, Ontario, Canada

Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Vmsmail-To: SMTP%"sas-l@uga.uga.edu"
Newsgroups: bit.listserv.sas-l
Date:         Mon, 6 Apr 1992 12:51:31 -0700
Reply-To:     JAMES@UCRAC1.UCR.EDU
From:         JAMES@UCRAC1.UCR.EDU
Subject:      sas-l@uga
Comments: To: sas-l@uga.cc.uga.edu

I wish to thank Jim Stukas,Jerry Arnold,David Nasser,Melvin Klassen,Joe Kelly
and anyone else I may have left out for assistance with the internet address of
sas-l@uga.

also Larry Hoyle provided a useful variation to my solution regarding
 PostScriptfiles in SAS. using proc gdevice is better in that the change is
 permanent and
eliminates the need of having to remember cumbersome hex codes (or mistyping
which may cause wierd results).

james ssemakula.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Mon, 6 Apr 1992 16:42:37 EDT
Reply-To:     todd pukanecz <CCCS@VTVM1.BITNET>
From:         todd pukanecz <CCCS@VTVM1.BITNET>
Subject:      output from PROC DATASETS

I want to get the output of the directory from PROC DATASETS to go to
a SAS dataset instead of or in addition to the log.  I want to process
this dataset to generate macro calls for further processing.  I've
been playing with various combinations of options for PROC DATASETS and
the CONTENTS statement and its options, all to no avail.  I suppose
I could use PROC PRINTTO, but then I still need one more DATA step to
process that output before I can generate my macro calls.

My question is, is there a nice way to get a SAS dataset that contains
a list of SAS datasets in a library?
    todddddddddd
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: SAS-L@TCSVM.BITNET
X-VMS-To: IN"SAS-L@TCSVM"
Newsgroups: bit.listserv.sas-l
Date:         Tue, 14 Apr 1992 13:09:00 CDT
Reply-To:     Kevin Calmes <TMIS1692@VEGA.SELU.EDU>
From:         Kevin Calmes <TMIS1692@VEGA.SELU.EDU>
Subject:      Help with VSE/SAS Unlabeled tape creation

I am new to SAS and could use some help in creating an output file on an
unlabeled tape.  We run SAS 5.16 on an IBM 4361 and DOS/VSE/SP 3.1.2.
I am getting errors on the SAS code FILE statement for the output tape.

1. What do the errors mean?
2. How do I correct the errors?

Here is the JCL and part of the SAS code I am trying to run...

* $$ JOB JNM=CATJOB,CLASS=0,DISP=D,PRI=6
* $$ LST CLASS=T,DISP=D,LST=SYSLST
// JOB CATJOB      CREATE NEW TITLES TAPE
// UPSI XX1        NON-LABELED TAPE
// PAUSE MOUNT TAPE #1609 ON 181 WITH A RING
// ASSGN SYS008,181
// MTC REW,SYS008
// MTC WTM,SYS008
// MTC REW,SYS008
// DLBL LISUBHF,'NOTIS.SU.BIB.HOLD.FILE',99/365,VSAM,CAT=UCAT1
// DLBL WORK,'WC768A',0,SD
// EXTENT SYS025,IES003,1,0,391,150000
// ASSGN SYS025,DISK,VOL=IES003,SHR
// ASSGN SYS011,SYSLST                   SAS LOG
// ASSGN SYS006,01E
* $$ LST CLASS=T,DISP=D,LST=SYS011
* $$ LST CLASS=T,DISP=D,LST=SYS006
// EXEC SASVSE,SIZE=(SASVSE,64K),PARM='VSAMLOAD'
/INCLUDE CATTAP                                   (see code below JCL)
/*
// MTC RUN,SYS008
/*
/&
* $$ EOJ


CATTAP: (FROM ICCF LIB)

DATA HOLD1 (stuff)
  INFILE LISUBHF VSAM COLUMN=PTRX LENGTH=RECLEN;
  INPUT (and process the input file)
  .
  .
  .
END;

DATA OCATT08.TITLES;
  RETAIN MONTH;
  SET HOLD1 END=EOF
  FILE OCATT08.TITLES BLKSIZE=17000 LRECL=170 RECFM=FB;
              -------
              539
              536
  (other SAS statements)

 ERROR 539: DDNAME IN USE FOR A SAS DATA LIBRARY
 ERROR 536: OPTION IS NOT RECOGNIZED AS A FILE OPTION
            OR IS NOT VALID FOR THE TYPE OF FILE
 NOTE: NO OUTPUT FILES OPENED DUE TO SYNTAX ERROR
 NOTE: SAS STOPPED PROCESSING THIS STEP BECAUSE OF ERRORS.


What caused these errors?  How do I correct this problem?
Thanks in advance for your help.

I am not a subscriber to the list so please e-mail reply to TMIS1692@SLU or
TMIS1692@SELU.EDU

Thanks, Kevin Calmes - Library Programmer SLU

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+  Kevin Calmes                            Internet: TMIS1692@SELU.EDU      +
+  Library Programmer                      Internet IP#: 147.174.1.5        +
+  Southeastern Louisiana University       Voice :  (504) 549-3645          +
+  Computing Services - MIS                Fax   :  (504) 549-5092          +
+  Box 409, SLU Station                    Bitnet: TMIS1692@SLU             +
+  Hammond, Louisiana  70402  USA                                           +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Newsgroups: bit.listserv.sas-l
From: realliso@unity.ncsu.edu (Robert Allison)
Subject: PRINTing in groups of 5?
Organization: North Carolina State University Project Unity
Date: Mon, 6 Apr 1992 18:33:46 GMT

I would like to be able to put a blank line (or '-----')
after every 5th line of my data when I print it.  Is it
possible to do this with PROC PRINT, or would you recommend
another approach?

My data does not come in any 'logical' groups of 5 that I
could use the GROUP BY option for... I just need to put 
breaks in the output so it will be easier to read.  I'm 
using SAS 6.07 on a DECstation.

Thanks,
Robert A.

|-------- here is my proc print satement -------
|
|proc print data = bls.table9;
|   id year;
|   format _NUMERIC_ 5.;
|   run;
|
|-----------------------------------------------

Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-To: LIU::"sas-l@finhutc.bitnet"
X-Cc: GU_PETERSSON
Newsgroups: bit.listserv.sas-l
Date:         Thu, 16 Apr 1992 14:39:51 +0200
Reply-To:     "Gunnar Petersson, VTI-TD,
              204068" <GU_PETERSSON@VIKING.LIDAC.LIU.SE>
From:         "Gunnar Petersson, VTI-TD,
              204068" <GU_PETERSSON@VIKING.LIDAC.LIU.SE>
Subject:      Colors in SAS/DMS from decwindows

 Good afternoon,

 I am running SAS decwindows interface on a PC with VGA-screen.
 In the file sas$xdefaults.dat on my root-directory I try to change
 the colors in the display manager windows but I am not succesfull.
 Whatever I write SAS starts with the default color setting. It is
 possible to change colors at the command line prompt but I want
 another default color setting at startup. Do anybody know the correct
 syntax for changing defaultcolors in different windows?

 Thank you in advance,

 Gunnar Petersson


-------------------------------------------------------------------------------
 Gunnar Petersson                             Phone:  +46 13 204068
 Swedish Road & Traffic Research Institute            +46 13 204000
 S-581 01 Linkoping                           Fax:    +46 13 204030
 Sweden                                       Bitnet: GPL@SELIUC51.BITNET
 VAX/VMS 5.4 and SAS 6.06
*******************************************************************************
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-From:  <bdperrm1@budget>
Newsgroups: bit.listserv.sas-l
Date:         Tue, 7 Apr 1992 16:36:00 EDT
Reply-To:     bdperrm1%budget@ALBNYDH2.BITNET
From:         bdperrm1%budget@ALBNYDH2.BITNET
Subject:      SAS vs. SPSS

David Alderton warned me that his views on SPSS vs. SAS may be somewhat
dated when I asked him for permission to post his note at 11:45 this
morning and I should have passed on this warning in my posting.

Regardless, Dave's comments and Lary's recent response have done much
to clarify the capabilities of SPSS's modern versions for a whole
generation of old-style SPSS users who have unpleasant memories of
SPSS in the early days.  Others have echoed Lary's comments in private
correspondence.

NYS*NYS*NYS*NYS*NYS*NYS*NYS*NYS*NYS*NYS*NYS*NYS*NYS*NYS*NYS*NYS
                                                    ____
        Michael F. Perry                          /     :
 Sr. Computer Programmer/Analyst           ______/      :
       State of New York                   \          * :Albany
     Division of the Budget               /__________   :
    State Capitol, Room 127-M                        \_/
       Albany, NY  12224  (518)474-6960               -====-

DOB*DOB*DOB*DOB*DOB*DOB*DOB*DOB*DOB*DOB*DOB*DOB*DOB*DOB*DOB*DOB
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Acknowledge-To: <HILL@CMSUVMA>
Newsgroups: bit.listserv.sas-l
Date:         Tue, 7 Apr 1992 09:29:37 CST
Reply-To:     Nancy <HILL@CMSUVMA.BITNET>
From:         Nancy <HILL@CMSUVMA.BITNET>
Subject:      Re: SUGI Shirts

For those who can not attend SUGI, I would suggest attending your annual
regional SAS user group conference. For those who can attend SUGI, I would
suggest attending your annual regional conference, presenting a paper or
tutorial and sharing your SUGI experience with those who did not get to
attend. I have the following regional conferences listed (note you don't
have to be part of the region holding the conference to attend, you can
pick the one closet to you or all of them if you wish).

Pharmaceutical  May 14&15, 1992 at Rockville, MD
Pacific Northwest sometime around June date to be announced Portland, OR
Canadian Sept 13 & 14 Quebec City, Quebec
MidWest Sept 29 through Oct 2, 1992 at Kansas City, Missouri
NorthEast  Oct. 4 through Oct. 6 at Baltimore, MD
SouthCentral Around November date and location to be announced
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU