Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!decvax!decwrl!hplabs!ucbvax!nuhub.acs.northeastern.edu!JOHNSON From: JOHNSON@nuhub.acs.northeastern.edu.UUCP Newsgroups: mod.computers.vax Subject: SAS Message-ID: <8612312355.AA19354@ucbvax.Berkeley.EDU> Date: Tue, 30-Dec-86 16:32:00 EST Article-I.D.: ucbvax.8612312355.AA19354 Posted: Tue Dec 30 16:32:00 1986 Date-Received: Wed, 31-Dec-86 21:04:44 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 48 Approved: info-vax@sri-kl.arpa >Hi, > We just upgraded from VMS 4.2 through VMS >4.4 onto VMS 4.5. > >Two problems resulted, both minor. > > The first is that SAS 5.03 won't run. >[fixable with directions] > > . . . > >*** SAS 5.03: We talked to the people out at the >SAS Institute. > >They said (well approximately): > > "Oh, if you upgrade to VMS 4.4 or 4.5, > SAS stops working. This is a known and > correctable problem. The instructions for > telling SAS to use the VMS 4.2 run-time > libraries are in the document shipped on > May X,1986. > > What? You didn't get that? Oh, we'll ship >it out to you." > >P.S. They say SAS will not need this sort >of pampering in the future. > >I'm expecting the document this week, but I'm >wondering if there's anything else about it I >should know. > >I would appreciate any reponses (to the >address(es) below) from anyone who has been >through this. We have SAS at Northeastern University. We also ran into much the same problem. The directions SAS gives will work. We modified them a little. When you activate SAS here you realy run a command file that does what the SAS directions say on a local user level only and then runs SAS. To the best of my knowledge SAS works fine except for real SAS bugs. Chris Johnson Northeastern University