HDTenEightyP/NetNews huggingface dataset:
Organization: U. Alabama School of Nursing
Newsgroups: bit.listserv.sas-l
Date:         Fri, 24 Jul 1992 17:15:24 CDT
Reply-To:     "Michael T. Weaver, RN Ph.D." <NURS036@UABDPO.DPO.UAB.EDU>
From:         "Michael T. Weaver, RN Ph.D." <NURS036@UABDPO.DPO.UAB.EDU>
Subject:      Summary: Disk Partitions & Performance
Comments: To: SAS Discussion List <SAS-L@ohstvma.acs.ohio-state.edu>

CONTENT:  Summary
SUMMARY:  Effects of PC Hard Disk Partitions on Performance
REL/PLTF: ALL / PC: DOS, WINDOWS, OS-2
E-ADDR:   nurs036@uabdpo.dpo.uab.edu
NAME:     Michael T. Weaver RN Ph.D.
PH/ADDR:  (205) 934-6913/ UAB Station, Birmingham, AL 35294-1210


First, my thanks to: Joe Walsh <jwalsh@umdacc.umd.edu>, Rodney Sparapini
<sparap@sophie.mscs.mu.edu> and Nelson Pardee <sasmaint@suvm> for their
ideas.

The consensus was that there would be no performance advantage (and, even,
there may be a slight degradation) in breaking a large hard drive into
several smaller partitions.

As a result, it was suggested to partition the drive based on how it was
used (e.g.: small boot partition, partition for stable programs, partition
for volatile data, etc.) if divided into smaller partitions.

Biggest performance gains may be realized by use of a good disk caching pgm
and keeping the drive defragmented.

Thanks again for your ideas.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Michael T. Weaver, RN Ph.D.
U. of Alabama at Birmingham       Internet: nurs036@uabdpo.dpo.uab.edu
School of Nursing                 Bitnet  : nurs036@uabdpo
UAB Station                       Radio   : kg8h
Birmingham, AL  35294-1210        Phone   : (205) 934-6913
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Wed, 22 Jul 1992 20:39:38 CDT
Reply-To:     David Nasser <NASSER@UMSLVMA.BITNET>
From:         David Nasser <NASSER@UMSLVMA.BITNET>
Subject:      **Re: multiple identical id vars problem

On Wed, 22 Jul 1992 11:38:22 EDT <EDSCC@CUNYVM> said:
>Hi,

>ID           CODE  TERM  DATE
>
>002162706    292  901   900309
>002162706    292  901   900403
>002254401    299  891   890201
>002254401    299  901   900303
>002254401    276  901   900405
>
>ID         CODE TERM DATE  CODE2 TERM2 DATE2  CODE3 TERM3 DATE3
>
>002162706  292  901 900309 299   901   900403
>002254401  299  891 890201 299   901   900303  299   901  900405
>
>Can this be done?  If it can, how?
>

I've seen 2 solutions to this problem on this list so far. I find
fault with neither of them.

If memory serves me well, I once posted a PROC TRANSPOSE solution
(similar to Gibes) to this list, tho TRANSPOSE and I usually avoid
one another.

Following CMS SASLOG may be somewhat redundant, but this is not the
sort of thing that's *terribly difficult* to do with a few DATA steps.

 NOTE: SAS (r) Proprietary Software Release 6.06.01
 NOTE: Running on IBM Model 3090 Serial Number X

 1          DATA A;
 2            INPUT ID           CODE  TERM  DATE ;
 3          CARDS;

 NOTE: The data set WORK.A has 5 observations and 4 variables.

 9          ;
 10         OPTIONS SYMBOLGEN;
 11         DATA _NULL_;    *** GET THE MAX NUMBER OF OBS FOR ANY ID VALUE ***;
 12          SET A(KEEP=ID) END=E1;
 13           BY ID;
 14           RETAIN MAX 0;
 15           IF FIRST.ID THEN CT=0;
 16           CT+1;
 17           IF LAST.ID THEN IF CT>MAX THEN MAX=CT;
 18            IF E1 THEN CALL SYMPUT('MAXID',COMPRESS(PUT(MAX,5.)));
 19          RUN;


 20         DATA A; SET A;   *** GENERATE THE DESIRED SAS DATASET ***;
 21          BY ID;
 22           ARRAY C(&MAXID) CODE1-CODE&MAXID;
 SYMBOLGEN:  Macro variable MAXID resolves to 3
 23           ARRAY T(&MAXID) TERM1-TERM&MAXID;
 24           ARRAY D(&MAXID) DATE1-DATE&MAXID;
 25          RETAIN;
 26           IF FIRST.ID THEN CT=0;
 27           CT+1;
 28           C(CT)=CODE;
 29           T(CT)=TERM;
 30           D(CT)=DATE;
 31           IF LAST.ID THEN OUTPUT;
 32          DROP CT CODE TERM DATE;


 NOTE: SAS Institute Inc., SAS Circle, PO Box 8000, Cary, NC 27512-8000
 NOTE: The data set WORK.A has 2 observations and 10 variables.

 33         DATA _NULL_;          *** TAKE A PEEK AT THE DATA ***;
 34          SET A;
 35           PUT _ALL_;

 ID=2162706 CODE1=292 CODE2=292 CODE3=. TERM1=901 TERM2=901 TERM3=.
 DATE1=900309 DATE2=900403 DATE3=. _ERROR_=0 _N_=1

 ID=2254401 CODE1=299 CODE2=299 CODE3=276 TERM1=891 TERM2=901 TERM3=901
 DATE1=890201 DATE2=900303 DATE3=900405 _ERROR_=0 _N_=2

 NOTE: SAS Institute Inc., SAS Circle, PO Box 8000, Cary, NC 27512-8000

Hope this is of some use ....

   Salut,
   David

David Nasser                              NASSER@UMSLVMA
St. Louis, Mo                             NASSER@UMSLVMA.UMSL.EDU

"People dancin'
 Round a golden calf,
 Those who have none
 And those who have ... "
   From "World In Motion" , Roebuck Staples
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Tue, 21 Jul 1992 09:02:37 EDT
Reply-To:     "Lawrence H. Muhlbaier" <lhm@BIOSTAT.MC.DUKE.EDU>
From:         "Lawrence H. Muhlbaier" <lhm@BIOSTAT.MC.DUKE.EDU>
Subject:      Re: missing data analysis
Comments: To: sas-l%vtvm2.BITNET@ncsuvm.ncsu.edu

From an unidentified requestor on the SAS-L list:

> From DEMPO@mc.duke.edu Mon Jul 20 15:47:24 1992
 >
> has anybody out there had any experience doing analysis on missing data?
>
> our dataset will have the following characteristics:
>
> 1) multiple observations per subject
> 2) subjects nested within a large number of groups
> 3) some variables measured on the subjects some measured on the groups
>    (a group would be something like a census tract)
>
> data are missing when:
>
> 1) a subject lacks one or more variable measurements
> 2) a group is lacking the required number of subjects
> 3) a group is lacking one or more variable measurements
>
> has anyone used or developed routines that will estimate the missing
> values (perhaps EM algorithm). BMDP has some routines for missing data
> but don't seem to handle all our types of missingness.
>

I am unaware of actual routines that can directly handle the questions
that you are raising.  There are, however, some techniques that may have
some promise.  I am wrestling with some significant missing data problems
myself, so this advice reflects my current study, rather than definitive
answers.

I would first look at Don Rubin's book on Multiple Imputation.  It has
some ideas that should work for variables that are missing (in either
cases or groups).

Imputing enitre observations is more difficult.  I don't have any ideas
there except to look at this idea of 'hierarchical modeling' that is
an empirical Bayes technique.

One final note:  I have had some experience with the EM algorithm
that was not entirely positive -- it would converge to local maxima,
and the only way that I could tell it was 'local' was by using
different starting points and converging to other answers.  It
would  not provide any other indication that there were convergence
problems.

Lawrence H. ('Doc') Muhlbaier		muhlb001@mc.duke.edu
Assistant Research Professor		muhlb001@dukemc
Duke University Medical Center		919-286-3322 (office)
DUMC 3865 				919-286-9534 (home)
Durham, NC 27710-7510			919-286-2947 (FAX)
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Wed, 22 Jul 1992 10:20:30 PDT
Reply-To:     Melvin Klassen <KLASSEN@UVVM.BITNET>
Comments:     Warning -- original Sender: tag was NETNEWS@UVVM.UVIC.CA
From:         Melvin Klassen <KLASSEN@UVVM.BITNET>
Subject:      Re: LIMDEP on IBM

Walter Davis <WDAVIS@UNCVM1> writes:
>  this has nothing to do with SAS, but there are enough users
>of LIMDEP and IBM systems types on the list that I thought I
>would forward these notes, especially since they don't seem
>to be in wide circulation (I got them from STAT-L).
>There appears to be a problem running the new version of LIMDEP
>on IBM systems.  The notes below explain the problem and,
>hopefully, provide some fixes.
>
All these problems with FORTRAN and LIMDEP can easily be solved
if the user of LIMDEP is using the current release of IBM's VS FORTRAN
Program Product.  Just specify the "NOCNVIOERR" run-time option
(as documented on page 92 of "VS FORTRAN Version 2, Programming Guide
for CMS and MVS, Release 5").  Then, FORTRAN error 212 (end-of-record)
**will** be intercepted by the 'ERR=' option.  As an alternate solution,
the user can turn to page 96, and specify the "RECPAD" run-time option.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
From: b128781@hp9000.csc.cuhk.hk (LAI Emil Vicky)
Subject: Graphical Output to WordPerfect or PageMaker
Organization: The Chinese University of Hong Kong
Date: Tue, 28 Jul 1992 06:36:06 GMT

I am running SAS Release 6.07.02 in the Silicon Graphics with IRIX Release
4.0.3 System V..

I have generated the graphical stream file from the SAS/GRAPH. But I can't
import the graphical stream file to WordPerfect or PageMaker. I have
generated in different format before, e.g the encapsulated Postscript
file, CGM, CGMWP, PS. But these files still can't be imported to the word
processor. Does anybody know the solution? Thanks for your kind attention.

/@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@\
|                                                                          |
|  Emil Mok, Computer Service Centre, The Chinese University of Hong Kong  |
|		   Internet : b128781@hp9000.csc.cuhk.hk                   |
|                                                                          |
|  		   Everything I do, I do it for you.                       |
|                                                                          |
\@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@/
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer: ELM [version 2.2 PL16]
Newsgroups: bit.listserv.sas-l
Date:         Fri, 24 Jul 1992 09:18:17 CDT
Reply-To:     "R. Snyder" <rsnyder@LOBBY.TI.COM>
From:         "R. Snyder" <rsnyder@LOBBY.TI.COM>
Subject:      Re: Using SAS for CPE - related question
Comments: To: MJF@IBM-B.RUTHERFORD.AC.UK
Comments: cc: sas-l@uga.cc.uga.edu
              92 2:28 pm

>                  o-o-o-o-o-o-o-o-o-o-o-o
>
> I am concerned about our current techniques for presenting
> statistics on batch job turnround information for our mainframe
> services. Currently we take a fairly simple approach and quote
> things like:
>
>   average time spent waiting in queues by job class
>   average expansion factors (that is, runtime/cpu)
>   80th percentiles for queue, run times
>      (ie 80% of total CPU was done by jobs having an expansion factor <=6)
>
> The advantage of such numbers are that they are easy to quote and understand
> to our management and users.
>
> The disadvantage is that they can also be very misleading, averages
> are simple but do not give indications to variability in the underlying
> data. A suggestion made is to parameterise the data and follow trends
> based on these statistics.
>
> My question is: can anyone pass on useful techiques that they use to
> report on their job turnround or give pointers to references on the topic.
>
> For the record, our performance data for our mainframe services
> is in SAS under VM/CMS
>
> Any suggestions greatly appreciated.
>
> Mike Froggatt, Marketing Services Group
> Rutherford Appleton Laboratory
> Didcot, Oxford, England
>

Mike,

I don't know much about CPE but if you can get your data into SAS data sets
you should be able to use the Shewhart procedure in SAS/QC to present your
data in an understandable way while showing variation and its significance.

Bob Snyder, Texas Instruments, Sherman, TX
From: sparap@jim.mscs.mu.edu (Rodney Sparapani)
Newsgroups: bit.listserv.sas-l
Subject: L-statistics?
Date: 27 Jul 92 21:10:07 GMT
Article-I.D.: spool.3645
Organization: Marquette University - Department MSCS

Does anyone know if SAS computes L-statistics?  I looked through 
PROC UNIVARIATE, but I couldn't find anything.  Just thought that
I would ask before I started coding.
Rodney
--
WARNING:  Contents of this message could be hazardous to your health.
Newsgroups: bit.listserv.sas-l
From: F1.DAO@isumvs.iastate.edu (David Oesper)
Subject: DROP variables which are always MISSING?
Organization: Iowa State University, Ames IA
Date: Thu, 30 Jul 1992 23:33:05 GMT

Is there any easy way to drop all variables whose values are ALWAYS
missing in a SAS data step?  There are times when doing a PROC
PRINT, for example, that you only want to look at the variables
which have values and ignore all the rest, rather than explicitly
coding each variable in the VAR statement.  Is there any way to
conditionally drop variables?
Organization: University of Minnesota - Computer & Information Services
Date: Wednesday, 29 Jul 1992 10:26:55 CST
From: <HAKOMAKI@UMINN1.BITNET>
Newsgroups: bit.listserv.sas-l
Subject: Suppression of SASLOG

Additional info:

To supress SASLOG on CMS when you invoke SAS issue a filedef beforehand

filedef xxxx dummy

SAS filename


Note: DON'T issue the parameter disk after the fileref (xxxx) or you will
get the SASLOG wriiten to your 191 disk. Strange.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-VMS-To: IN%"sas-l@uga.bitnet"
Newsgroups: bit.listserv.sas-l
Date:         Mon, 27 Jul 1992 13:55:00 CDT
Reply-To:     BOKERSON@MEMSTVX1.BITNET
From:         BOKERSON@MEMSTVX1.BITNET
Subject:      re: all possible combinations join

A special thanks to Howard Schreier for suggesting an outer join with Proc SQL.
The following code solved my problem:

proc sql;
    create table tot as
    select *
    from beh full join inm
    on beh.pond=inm.pond;

Thanks also to Ben Conner, Tom Abernathy and Kernon Gibes for suggesting SQL.
As one who learned SAS before the advent of Proc SQL, I keep trying to do
everything with data steps, even with SQL is more appropriate because of the
radical differences in syntax.  I have now resolved to learn Proc SQL.

-------------------------------------------------------------------------------

Barbara Okerson                     BOKERSON@MEMSTVX1 (bitnet)
SAS Consultant                      BOKERSON@MSUVX1.MEMST.EDU (internet)
Academic Computer Services          (901)678-3682 (voice)
Memphis State University
Memphis, TN  38152
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Wed, 29 Jul 1992 17:32:44 EDT
Reply-To:     Andy Norton <76350.1604@COMPUSERVE.COM>
From:         Andy Norton <76350.1604@COMPUSERVE.COM>
Subject:      File date in SAS 6.07 VMS
Comments: To: SAS-L <SAS-L@AWIIMC12.IMC.UNIVIE.AC.AT>

----------------------------------------------------------------------
CONTENT:   Response
SUMMARY:   Response to Mark Shaffer (obtaining sas dataset creation)
           Use version 6.07 SQL Dictionary Views
REL/PLTF:  6.07.01/CMS, 6.04/PC-DOS
E-ADDR:    76350.1604@compuserve.com
NAME:      Andy Norton
ADDRESS:   Trilogy Consulting, 5822 Lovers Lane, Kalamazoo MI 49002
PHONE:     (616) 344-2191
----------------------------------------------------------------------
Marc Schaeffer  (mschaeff@PILOT.NJIN.NET) asked
>  Is there a macro, like &sysdate, which I can use to insert the
>  filedate (i.e., the date the file was last refreshed) in a footer
>  in my reports?

On page 289 of Technical Report P-222 ("Changes and Enhancements to
BASE SAS Software, Release 6.07")  it describes SQL dictionary views.
These let you get at internal dataset header information that was
previously only printed on PROC CONTENTS listings.

Using SQL,
   proc sql noprint;
     select CRDATE
     into   :CRDATE
     from   DICTIONARY.TABLES
     where      LIBNAME = 'WHATEVER'
            and MEMNAME = 'WHATELSE';
   quit;
   proc print data=WHATEVER.WHATELSE;
     footnote "Created on &CRDATE";
   run;

Note that CRDATE yields a formatted DATETIME value.  You might want to
use the DATEPART function to get a DATE value.

You can also do it without PROC SQL (no particular advantage):

   data _null_;
     set SASHELP.VTABLE;
       where LIBNAME='WHATEVER' and MEMNAME='WHATELSE';
     call symput ('CRDATE', put(CRDATE, DATETIME.));
   run;

Note:  SASHELP.VTABLE is a built-in kludge allowing you to access
Dictionary views from outside of SQL (after all, DICTIONARY is an
invalid libname).  See page 290 of Tech Rpt P-222.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: sas-l@UALTAVM.BITNET
Newsgroups: bit.listserv.sas-l
Date:         Mon, 20 Jul 1992 11:00:23 -0400
Reply-To:     Anami Bhargava <bhargava@MCMAIL.CIS.MCMASTER.CA>
From:         Anami Bhargava <bhargava@MCMAIL.CIS.MCMASTER.CA>
Subject:      SASLOAD FOR SAS 6.04 (DOS/MSDOS) and a 486 with SCSI disk

Hi Group;

I encountered a problem when installing sas/pc on a customer's
GATEWAY2000 486bx2/50 MSDOS 5 with SCSI disk of 340Mg capacity. I
inserted the Installation Disk in B: drive and entered -

b:\sasload -from b:

As few minutes passed by and nothing seems to happen accept drive
B:'s light was lit green all the time I got suspicious and turned
power off. After re-booting the machine I try to see the contents
of the SAS directory. What I found was that the root directory of
the machine was copied into the SAS directory and it was propagated
several times. McAfee scan could not detect any virus on my SAS
Installation disk but the customer thinks that the SASLOAD program has
some problem with the SCSI disks. Has any one encountered such problem
recently. Any comments and suggestions would be appreciated.

Currently I am not subscribed to the list and would appreciate if
the reply is e-mailed directly to bhargava@mcmaster.ca .

=========================================================================
                                         bhargava@mcmaster  , or
Anami Bhargava                           bhargava@mcmail.cis.mcmaster.ca
Application Software Specialist          TEL (416) 525-9140 Ext. 4162
Computing Information Services           FAX (416) 527-0100
McMaster University, KTH-328                 (416) 528-3773
1280 Main Street West, Hamilton,
Canada, L8S 4M4
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Via: uk.ac.leicester; Thu, 30 Jul 1992 13:30:47 +0100
Site: University of Leicester, Leicester, U.K.
Phone: +44 533 523259 (direct line)
Organisation: University of Leicester Department of Psychiatry.
X-Name: Simon Dunkley,
X-Address: Dept of Psychiatry, Clinical Sciences Building,
X-Address: Leicester Royal Infirmary, P.O.Box 65,
X-Address: LEICESTER. LE2 7LX. United Kingdom.
X-Phone: +44 533 523259 (direct line)
X-Fax: +44 533 523293
X-Mailer: ELM [version 2.3 PL0 (LUT)]
Newsgroups: bit.listserv.sas-l
Date:         Thu, 30 Jul 1992 13:27:08 BST
Reply-To:     sdd@leicester.ac.uk
From:         Simon Dunkley <sdd@LEICESTER.AC.UK>
Subject:      Re: Comma delimited output file from SAS on MVS/ESA
Comments: To: "SAS(r) Distribution list" <sas-l@vtvm2.cc.vt.edu>

Kevin Nechodom <knechod@EDU.UTAH.MED.STACC> writes:
> Finally, to voice an old complaint, it would be nice if the standard
> implementation of SAS included 'standard' (in quotes in deference to
> those who actually measure and evaluate such standards) file formats,
> like CSV, DBF, DIF, etc.  With the proliferation of UN*X workstations
> and the migratation of DOS programs like dBase to those workstations,
> the need is becoming greater!
>
    What about proc dbf and proc dif?

    Simon

      00 0 O o o...
     0     ___         _________________ _________________ _________________
    ][_n_i_|(  ooo___  | Simon Dunkley | |    sdd@le     | |  sdd@le.ac.uk |
   (  _____| | |     | | Department of | | University of | |      +44      |
   _||_____|_|_|_____|_|__Psychiatry___|_|___Leicester___|_|__533__523259__|
     0--0--0    o o o    o-o       o-o     o-o       o-o     o-o       o-o
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Acknowledge-To: <RICHARD@U.WASHINGTON.EDU>
Newsgroups: bit.listserv.sas-l
Date:         Thu, 30 Jul 1992 13:34:10 PDT
Reply-To:     Richard Leickly <RICHARD@U.WASHINGTON.EDU>
Comments:     Warning -- original Sender: tag was
              RICHARD@UWAVM.U.WASHINGTON.EDU
From:         Richard Leickly <RICHARD@U.WASHINGTON.EDU>
Subject:      COMPARING DISTRIBUTIONS

I've looked in <SAS procedures> and <SAS/STAT> but I can't find a test
to decide if two distributions are significantly different from each other
(not from a normal distribution).  Does anyone know if SAS has such a test?

[PC-SAS, version 6.04, DOS 5.0]

+---------------------------------+-----------------------------------+
| Richard Leickly                 | Internet: richard@u.washington.edu|
| Northwest Lipid Research Clinic | University of Washington          |
| Seattle, Washington   98195     | Mailstop: ZA-36  Ph:206-223-6267  |
+---------------------------------+-----------------------------------+
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Fri, 31 Jul 1992 00:20:59 IST
Reply-To:     OSCAR ZIMERMAN <ZIMERMAN@TAUNIVM.BITNET>
From:         OSCAR ZIMERMAN <ZIMERMAN@TAUNIVM.BITNET>
Subject:      FSEDIT delete observation

Hello SASlers ...

> My question is very simple :
>      In an FSEDIT Application, I want to lock the option
>      DELETE.
>      This means, that the user will be able to add or update
>      a record, but never delete any observation.
>
> I am sure that I am not the first one to need something like
> that.
>
> Please,send the possible answers directly to me. I will resume
> to all of you
>
> Plataform : CMS    Version 6.06


Solution :

There is no way to do that under Version 6.06.
On the other hand, under Version 6.07, there is more that one
option to acomplish this task.
The best one is as follow :

            INIT:
            CONTROL ALLCMDS;
            RETURN;
            MAIN:
              CMD=LASTCMD();
              IF CMD='DELETE' THEN DO;
                  ... more commands....
                   CALL NEXTWORD();
              END;
            TERM:
            RETURN;

Using this method, you have full control of any action
from the command line.


                                 Thank you for all of you
                                 who help me to solve this
                                 problem.


                                 Natan Galkowicz
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU