HDTenEightyP/NetNews huggingface dataset:
Newsgroups: bit.listserv.sas-l
Date:         Wed, 9 Sep 1992 11:15:58 EDT
Reply-To:     Ekeho <V1354G@TEMPLEVM.BITNET>
From:         Ekeho <V1354G@TEMPLEVM.BITNET>
Subject:      Conversion of BMDP file

Hi Folks:
     I am testing some SAS  programs.  The following program is to
convert BMDP file to SAS data set. My engine is SAS 6.06 on CMS.
I am looking forward to your help.

====================================================================


11                                                          The SAS System

 NOTE: Copyright(c) 1989 by SAS Institute Inc., Cary, NC USA.
 NOTE: SAS (r) Proprietary Software Release 6.06.01
       Licensed to TEMPLE UNIVERSITY COMPUTER ACTIVITY, Site 0003844001.



  Welcome to the new SAS System, Release 6.06.

  This message is seen by users when the NEWS option is specified.
  You can replace this message with your own by editing the NEWS file.

  Changes and enhancements available in SAS Release 6.06 are documented
  in the online Host Help.

 1          FILENAME BMDPFILE 'SAMPLE SAV A';
 2          PROC CONVERT BMDP=BMDPFILE OUT=FROMBMDP;
 3          RUN;

 ERROR: Invalid header on file BMDPFILE._FIRST_.DATA.
+ERROR: Invalid header on file BMDPFILE._FIRST_.DATA.
+ERROR: Invalid header on file BMDPFILE._FIRST_.DATA.
 NOTE: The data set WORK.FROMBMDP has 0 observations and 0 variables.

 4          PROC CONTENTS;
 5              TITLE 'SAS DATA SET CONVERTED FROM BMDP SAVE FILE';
 6          RUN;

 NOTE: The PROCEDURE CONTENTS printed page 1.

 7          PROC PRINT;
 8          RUN;

 NOTE: No variables in data set WORK.FROMBMDP.
 NOTE: The SAS System stopped processing this step because of errors.


 ERROR: Errors printed on page 1.
+ERROR: Errors printed on page 1.
+ERROR: Errors printed on page 1.

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




===============================================================

Ekeho Oh

Internet: V1354G@VM.TEMPLE.EDU     Home: 534 W.Pike St
Bitnet:   V1354G@TEMPLEVM                Philadelhpia, PA 19140
Dep't of Statistics                      215-223-6485
Temple University
Philadelphia, PA 19122
USA

===============================================================
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Fri, 11 Sep 1992 12:46:01 -0400
Reply-To:     "Paul A. Thompson" <pat@po.CWRU.Edu>
From:         "Paul A. Thompson" <pat@PO.CWRU.EDU>
Subject:      Last (??) word on variable lengths
Comments: To: sas-l@vtvm2.cc.vt.edu
Comments: cc: pat@slc10.INS.CWRU.Edu

That is, my last word.

Several years ago, when working on an article involving some
non-linear regression, I used a popular (at that time) FORTRAN
subroutine called STEPIT to do a multivariable, derivative free
minimization.  Being compulsive etc., I tried several different
start values.  Different solutions resulted!!  Really different, at
that.

So, I looked at the algorithm.  It was all written in single precision,
and these values were being used to minimize this complex function.
Essentially, this was the entire problem!  After rewritting the
code to substitute double precision for single, I had no further
convergence difficulties.  Since that point, I have generally erred
on the side of too much precision, rather than the other direction.

Of course, in SAS, all computations are done in long double, or whatever
they are called, variables.

--
Paul Thompson, Ph.D.  |  Department of Psychiatry  |  (216) 844-7463
Case Western Reserve University  | Cleveland, OH  44106
------------------------------------------------------------------------------
When I hear "family values," I reach for my revolver. - paraphrasing Trotsky
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Thu, 10 Sep 1992 19:02:54 -0700
Reply-To:     Peter Kretzman <peterk@MIS.CORP.MCCAW.COM>
From:         Peter Kretzman <peterk@MIS.CORP.MCCAW.COM>
Subject:      RE: numbers in SAS
Comments: To: SAS-L@uga.cc.uga.edu

Paul A. Thompson writes on Thu, 10 Sep 1992 18:18:15


So my conclusion is that consistent lengths produce consistent
results.  The problem is NOT THE PROBLEM OF THE IMPERFECT
REPRESENTATION of decimals in a binary coding - this is a given.  The
real problem is DIFFERING LEVELS of IMPERFECT REPRESENTATION.  If you
use different lengths your imperfect representations will be
different.  If you use the same length all around, your imperfect
representations will be consistent,and USUALLY yield the correct
result.
(end of quoted material)


I think Paul has given an excellent summary of the issue.  The only
thing I would add, given some of the postings on this thread, would
be to stress again the concept that _all_ variables (whereever they
may come from) within the DATA step take on an internal length of 8.
Their assigned length ONLY BECOMES A FACTOR WHEN THEY ARE STORED in
the output data set, at which point shorter length variables are
truncated.  If any subsequent steps retrieve those observations,
these shorter length variables are then padded (internally, in
memory) back to length 8, then are truncated again on output.

Peter Kretzman
McCaw Cellular Communications, Inc.
(206) 828-1344
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Food and Agriculture Organization of the UN
X-Acknowledge-To: <AFCO73@IRMFAO01>
Newsgroups: bit.listserv.sas-l
Date:         Tue, 15 Sep 1992 08:44:45 ITA
Reply-To:     Johnny Hua <AFCO73@IRMFAO01.BITNET>
From:         Johnny Hua <AFCO73@IRMFAO01.BITNET>
Subject:      Benchmark

Good-day,

   Here is my benchmark result on a mainframe and on a DOS/PC:

                             STEP1    STEP2    SORT    REGRESSION

   1. HDS/EX80 MAINFRAME     0.16     0.15     0.22    0.10
      (MVS/XA - SAS 5.18)

   2. DMC NETMATE/SX20       50       23       18      22
      (DOS5 - SAS 6.04)

   We find that it is generally OK using SAS on a PC for a small amount
   of data.  But when the amount of data and number of variables become
   large, PC is painfully slow (even with EMS).  Would anyone know if
   there is any good performance guideline and hint for running SAS on
   PC/DOS.  We thought the Windows version of SAS would help in
   performance, but were tought it will not be released until late this
   year.

   Thanks for any help in this area.

Johnny Hua,
System Programmer,
FAO of the UN,
ROME, ITALY

AFCO73@IRMFAO01
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Subject: (no subject given)
Newsgroups: bit.listserv.sas-l
Date:         Tue, 15 Sep 1992 10:36:53 EDT
Reply-To:     "Sanjay K. Pandey" <SKPWORK@SUVM.BITNET>
From:         "Sanjay K. Pandey" <SKPWORK@SUVM.BITNET>

//      JOB  Echo=No
Database Search DD=Rules
//Rules DD   *
S * in sas-l where subject contains observations
print
/*
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Vers: Weeg cc:Mail/SMTP translation (originally by A. Marshall)
Newsgroups: bit.listserv.sas-l
Date:         Thu, 10 Sep 1992 19:16:00 CST
Reply-To:     Svec@ACT-ACT6-PO.ACT.ORG
From:         Svec@ACT-ACT6-PO.ACT.ORG
Subject:      Benchmark results under OS/2 1.3

I saw the benchmark results that someone posted recently for a big IBM
mainframe, and I couldn't resist running it on my 386 25MHz DX running
SAS 6.06 under OS/2 version 1.3 (no 2.0 yet, sorry).  The machine has
a 330MB SCSI hard drive with a Western Digital 7000 FASST SCSI controller, and
16 MB RAM.  I ran the thing from the command line - running in "intereactive"
mode is slightly slower.

I'd be VERY INTERESTED to see results from this benchmark when run on
other PC configurations (486's, etc, OS/2 2.0 vs. OS/2 1.3, etc)...

Joe Svec
Research Analyst
American College Testing
Iowa City, IA  52245

---

NOTE: Copyright(c) 1989 by SAS Institute Inc., Cary, NC USA.
NOTE: SAS (r) Proprietary Software Release 6.06.03
      Licensed to AMERICAN COLLEGE TESTING, Site 0026417001.

1          filename dataf 'c:\test.sas';
2
3          data _null_;
4             file datf;
5             do a='c', 'b', 'a';
6                do x=1 to 1000;
7                   y=4+3*x+rannor(0); put a x y;
8                end;
9             end;
10         run;

NOTE: The file DATF is:
      FILENAME=C:\sas\DATF.DAT

NOTE: 3000 records were written to the file DATF.
      The minimum record length was 14.
      The maximum record length was 19.
NOTE: The DATA statement used 12.16 seconds.

11
12         data t1;
13            infile datf;
14            length a $ 1;
15            input a x y;
16            x2=x*x;
17            ia=0; ib=0; ic=0;
18            select(a);
19               when('a') ia=1;
20               when('b') ib=1;
21               when('c') ic=1;
22               otherwise;
23            end;
24         run;

NOTE: The infile DATF is:
      FILENAME=C:\sas\DATF.DAT

NOTE: 3000 records were read from the infile DATF.
      The minimum record length was 14.
      The maximum record length was 19.
NOTE: The data set WORK.T1 has 3000 observations and 7 variables.
NOTE: The DATA statement used 6.90 seconds.

25
26         proc sort data=t1;
27            by a;
28         run;

NOTE: SAS sort was used.
NOTE: The data set WORK.T1 has 3000 observations and 7 variables.
NOTE: The PROCEDURE SORT used 4.50 seconds.

29
30         proc reg;
31            model y=x;
32            model y=ia ib ic x x2 /noint;
33         run;

NOTE: 3000 observations read.
      3000 observations used in computations.
NOTE: At least one W.D format was too small for the number to be printed. The de
cimal may be shifted by the "BEST" format.
NOTE: The PROCEDURE REG printed pages 1-2.
NOTE: The PROCEDURE REG used 5.53 seconds.


NOTE: SAS Institute Inc., SAS Circle, PO Box 8000, Cary, NC 27512-8000
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: U. Alabama School of Nursing
Newsgroups: bit.listserv.sas-l
Date:         Tue, 15 Sep 1992 09:51:35 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:      Re: TRANSPORT ENGINE / CPORT
Comments: To: Richard Varron
              <varron%PILOT.NJIN.NET@OHSTVMA.ACS.OHIO-STATE.EDU>,
              SAS Discussion List <SAS-L@ohstvma.acs.ohio-state.edu>

Richard,

I've run into similar problems here.

In our computer support department trying to figure out what was going wrong
(I had no problems transferring to & from an IBM CMS system, or FROM a VAX
system using FTP.), they finally concluded that the problems were caused by
the flavor of TCP/IP / FTP on the VAX (it was Wollongong...);  it did not
recognize the 'bin f 80' command issued within FTP, and so botched the
transfer.

VAX VMS has a recognized problem in creating SAS Transport datasets, in that
it appends CR/LF to each record, which must be stripped.  Hope this provides
some clues; I never could get it to work here.  Let me know if you
receive a solution that works.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
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:         Fri, 11 Sep 1992 11:48:30 EDT
Reply-To:     Andy Norton <76350.1604@COMPUSERVE.COM>
From:         Andy Norton <76350.1604@COMPUSERVE.COM>
Subject:      Response - Creating a long macro variable.
Comments: To: SAS-L <SAS-L@AWIIMC12.IMC.UNIVIE.AC.AT>

----------------------------------------------------------------------
CONTENT:    Response
SUMMARY:   Macro variables can be up to 32767 long
           Tokens within macro variable values cannot exceed 200
           Arguments to CALL SYMPUT cannot exceed 200
REL/PLTF:  6.07.01/CMS, 6.04/PC-DOS
E-ADDR:    76350.1604@compuserve.com
NAME:      Andy Norton
ADDRESS:   Trilogy Consulting, 5228 Lovers Lane, Kalamazoo MI 49002
PHONE:     (616) 344-2191
----------------------------------------------------------------------
Michael Perry states:
> Regarding Kernon Gibe's comments on Bob Snyder's response to the
> looong macro variable question, yes Bob's suggestion does work.  (See
> test below run successfully under VM/CMS.)  According to the SAS
> Guide to Macro Processing V5, Appendix 2, the max length of the macro
> variable is controlled by the MWORK= system option with a default of
> 2k (2048 bytes) and max value of 28k.  I agree with Bob, however,
> that there must be a more elegant solution than concatenating a huge
> macro variable. Regardless, his code works fine.

My notes for VMS 6.07 say that the maximum length of a macro variable
value is 32767, but I can't find the reference.

I just did tests in CMS 6.07 that show that the second argument of CALL
SYMPUT is truncated at 200 characters.  You have to concatenate using
%LET instead.

Also, a really tricky trap (just confirmed by testing CMS 6.07).
Although macro variable values can exceed 200 characters, no token in
that value can exceed 200 characters!
    %let L = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx;
    %let Y = &L &L &L &L &L &L &L &L &L &L &L &L &L &L &L &L;
no problem, but
    %let Z = &L&L&L&L&L&L&L&L&L&L&L&L&L&L&L&L;
gives
    WARNING:  The current word or quoted string has become more than
200 characters long.  You may have unbalanced quotation marks.

Let the programmer beware.

By the way, I agree with others that long macro variables are probably
not the best solution to Helen's original problem.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Thu, 10 Sep 1992 09:25:16 EDT
Reply-To:     Ekeho <V1354G@TEMPLEVM.BITNET>
From:         Ekeho <V1354G@TEMPLEVM.BITNET>
Subject:      BMDP

Hi Folks:
     I am testing a SAS program in Page 185 "SAS Companion for the CMS
Environment".  The following program is to create and to convert
 BMDP file to SAS data set. When I test BMDP1d, it works.
May be there is a linkage problem. Any one has the same problem.
 My engine is SAS 6.06 on CMS.
I am looking forward to your help.
=======================================================================
11                                                          The SAS System

 NOTE: Copyright(c) 1989 by SAS Institute Inc., Cary, NC USA.
 NOTE: SAS (r) Proprietary Software Release 6.06.01
       Licensed to TEMPLE UNIVERSITY COMPUTER ACTIVITY, Site 0003844001.



  Welcome to the new SAS System, Release 6.06.

  This message is seen by users when the NEWS option is specified.
  You can replace this message with your own by editing the NEWS file.

  Changes and enhancements available in SAS Release 6.06 are documented
  in the online Host Help.

 1          DATA TEMP;
 2             INPUT A B C;
 3             CARDS;

 NOTE: The data set WORK.TEMP has 3 observations and 3 variables.

 7          ;
 8          PROC CONTENTS;
 9            TITLE 'CONTENTS OF SAS DATA SET TO BE RUN THROUGH BMDP1D';
 10         RUN;

 NOTE: The PROCEDURE CONTENTS printed page 1.

 11         PROC BMDP PROG=BMDP1D DATA=TEMP UNIT=3;
 12           PARMCARDS;


 ERROR: The BMDP1D program could not be loaded.
+ERROR: The BMDP1D program could not be loaded.
+ERROR: The BMDP1D program could not be loaded.
 NOTE: The SAS System stopped processing this step because of errors.


 18         ;
 19         PROC CONVERT BMDP=FT04F001 OUT=FROMBMDP;
 20         RUN;

 ERROR: Physical file does not exist, FILE     FT04F001 A4.
+ERROR: Physical file does not exist, FILE     FT04F001 A4.
+ERROR: Physical file does not exist, FILE     FT04F001 A4.
 NOTE: The data set WORK.FROMBMDP has 0 observations and 0 variables.

 21         PROC CONTENTS;
 22             TITLE 'SAS DATA SET CONVERTED FROM BMDP SAVE FILE';
 23         RUN;

 NOTE: The PROCEDURE CONTENTS printed page 2.

 24         PROC PRINT;
 25         RUN;

 NOTE: No variables in data set WORK.FROMBMDP.
 NOTE: The SAS System stopped processing this step because of errors.


 ERROR: Errors printed on page 1.
+ERROR: Errors printed on page 1.
+ERROR: Errors printed on page 1.

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

Ekeho Oh

Internet: V1354G@VM.TEMPLE.EDU     Home: 534 W.Pike St
Bitnet:   V1354G@TEMPLEVM                Philadelhpia, PA 19140
Dep't of Statistics                      215-223-6485
Temple University
Philadelphia, PA 19122
USA

===============================================================
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Wed, 9 Sep 1992 13:35:01 -0400
Reply-To:     "Paul A. Thompson" <pat@po.CWRU.Edu>
From:         "Paul A. Thompson" <pat@PO.CWRU.EDU>
Subject:      Re: numbers in SAS
Comments: To: alderton@nprdc.navy.mil
Comments: cc: sas-l@vtvm2.cc.vt.edu

...

>could give me some guidelines on reading/storing numbers I would
>really appreciate it (the manual, Basics p. 157, has some information
>on the largest numbers, but nothing on decimals which most of my
>numbers have).

Length is really quite simple.

1.  Don't attempt to save space with reals.  Real numbers must be
    (IMEVHO) represented in length 8 variables (default).  Shorter
    variables will lead to difficulties down the line.

2.  Integers (where X = floor(x)) are representable correctly using
    shorter values.  Please read about LENGTH statement in book to
    get appropriate length commands for values, but anything bounded by
    abs(256) can use length 2, etc.



--
Paul Thompson, Ph.D.  |  Department of Psychiatry  |  (216) 844-7463
Case Western Reserve University  | Cleveland, OH  44106
------------------------------------------------------------------------------
When I hear "family values," I reach for my revolver. - paraphrasing Trotsky
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: SAS-L@OHSTVMA.BITNET
X-VMS-To: IN%"SAS-L@OHSTVMA.BITNET"
X-VMS-Cc: ADROSEN
Newsgroups: bit.listserv.sas-l
Date:         Fri, 11 Sep 1992 15:43:00 EST
Reply-To:     "Allan D. Rosen (412)624-0418" <ADROSEN@PITTVMS.BITNET>
From:         "Allan D. Rosen (412)624-0418" <ADROSEN@PITTVMS.BITNET>
Subject:      Re: More Benchmarks for SAS under OS/2

-----------------------------------------------------
Content:  Response
SUMMARY:  More Benchmarks for SAS under OS/2
E-ADDR:   ADROSEN@vms.cis.pitt.edu
NAME:     Allan Rosen
ADDR:     University of Pittsburgh
-------------------------------------------------------

>
>could you check again - it does not make any sense for the proc reg run to be
>quicker on DMS than on batch.
>
>
>-phil

Phil is right and wrong.  Proc REG did run in 2.25 seconds in DMS and 3.00
seconds in batch.  However, Phil caught me being careless in my experiment.
I ran Proc REG once before the test in DMS.  This saved about 0.80 seconds
the second time Proc REG was run because it was already loaded.


Allan Rosen
University of Pittsburgh
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Sat, 12 Sep 1992 17:23:18 CDT
Reply-To:     Allen Herzog <U50161@UICVM.BITNET>
Comments:     "U. of Illinois at Chicago"
From:         Allen Herzog <U50161@UICVM.BITNET>
Subject:      StatFair - Wed. Sept. 21, 1992
Comments: To: Allen Herzog <STAT-L@MCGILL1.BITNET>

         For those of you fortunate to be in the Chicago area on
September 23, 1992 the Chicago Chapter of American Statistical
Association is holding a StatFair.  What follows summarizes their
flyer describing the fair:

       Statistical Software for Persoal Computers & Workstations

       Demonstrations and Bargains

       Date - Wednesday, September 23, 1992
       Time - Noon until 6:30 PM
       Place - The Westin Hotel, Chicago
               (909 North Michigan Ave.)
       Cost - With reservations postmarked before Sept. 19
              $ 10.00 Member of the Chicago Chapter, ASA & Students
              $ 20.00 Non-members (or $22. includes Chapter dues)
            - Registration after September 21 - Add $10.00

       5 GOOD REASONS TO ATTEND StatFair

          Demonstrations   of statistical software - a chance to talk
                           to technical experts
          Bargains         A chance to purchase the software at deep
                           discounts only availabe during 6 1/2 hrs
                           of StatFair
          Handouts    -    Lists - of over 400 statistical software
                           packages with addresses and phones, cross
                           referenced by application (now available
                           on computer diskette)

          For more information ... Call Linda Clark at 708/798-0677

    I hope the list will find this information of interest and use.
I attended the last StatFair a couple of years ago and found it very
informative.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Southern Methodist University
Newsgroups: bit.listserv.sas-l
Date:         Wed, 9 Sep 1992 12:13:24 CST
Reply-To:     Morgan Blevins <AP16@SMUVM1.BITNET>
From:         Morgan Blevins <AP16@SMUVM1.BITNET>
Subject:      NEWS RELEASE

Dateline Carey, N.C., Sept. 9, 1992

SAS INSTITUTE is proud to announce a new development.
PROC FSSHUTTLE will allow online communications with
NASA shuttle flights.

The documentation is self-explanatory when you fill out the
online screens.
For informtaion not located in the general manuals, refer to
the SAS documentation for your host system or see your SAS
Software Consultant for details.*




*due to the number of various host system and flights, SAS will
not support this proc, but we here at SAS do like the way the screen
looks.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X400-Trace: US* *BRADLEY; arrival Fri, 4 Sep 92 09:16:53 -0500 action Relayed
P1-Message-ID: US* *BRADLEY; 920904091540454-MTABUCC1
UA-Content-ID: 920904091540454-
Newsgroups: bit.listserv.sas-l
Date:         Fri, 4 Sep 1992 09:16:53 -0500
Reply-To:     Warren.E.McReynolds@BUCC1.BRADLEY.EDU
From:         Warren.E.McReynolds@BUCC1.BRADLEY.EDU
Subject:      Getting to MWSUG
Comments: To: SAS-L@uga.cc.uga.edu

I'm driving to KC for MWSUG, and, I have on question:

How torn up is I-70 across Missouri?
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.sas-l
Date:         Thu, 3 Sep 1992 13:20:00 CDT
Reply-To:     Deb Cannon 319-335-6321 <ADPDKHTS@UIAMVS.BITNET>
From:         Deb Cannon 319-335-6321 <ADPDKHTS@UIAMVS.BITNET>
Subject:      Re: SAS Futures / IBM's Book Manager

>
> Online manual access is CLEARLY the progressive thing to do, however I
> suspect it may cut into a company's manual-sales revenues. Remember the
> perhaps apocryphal Kodak annecdote: "Give the cameras away; we'll make
> our money on the film." Selling documentation is, I suspect, a major
> source of revenue for SAS Institute, like many other companies.

     That'd certainly be interesting to find out!   I don't see how
     the trend could be stopped - paper will get more and more
     expensive, prices will be driven up so high sales will decrease,
     if not that, SAS's much-protected reputation as being as
     leading  information-delivery system will start to falter
     if they insist on paper when everyone else in the industry has gone
     online (granted this will take a 'few' years.....).
>
> One final thought: remember that online manual access isn't wholly
> practical unless you have a high resolution workstation-quality interface
> ... or you're willing to sacrafice all illustrations and most page
> formatting.
>
     Book Manager for MVS can handle graphic illustrations, provided
     you have a graphics terminal.  Don't know about other platforms.

     an-old-poop-in-training,
     Deb

     p.s:
     LEICESTER: WOULDYA CUT IT OUT?
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer: ELM [version 2.3 PL10]
Newsgroups: bit.listserv.sas-l
Date:         Wed, 9 Sep 1992 16:46:59 EDT
Reply-To:     Gail Gill <glg2@GTE.COM>
From:         Gail Gill <glg2@GTE.COM>
Subject:      Proc IML
Comments: To: sas-l%marist.bitnet@cunyvm.cuny.edu

Thanks to W. Davis for a very quick and accurate reply to my
IML question. The append needed a from statement.
Gail
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU