home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!bnr.co.uk!bnrgate!nrcnet0!cunews!torn!utcsri!rutgers!zeus.ieee.org!europa.asd.contel.com!paladin.american.edu!auvm!ALASKA.BITNET!AFDGF
- From: AFDGF@ALASKA.BITNET (DENNIS G FISHER)
- Newsgroups: bit.listserv.sas-l
- Subject: vms
- Message-ID: <SAS-L%92110422160806@UGA.CC.UGA.EDU>
- Date: 4 Nov 92 23:08:53 GMT
- Sender: "SAS(r) Discussion" <SAS-L@UGA.BITNET>
- Reply-To: "ACAD2A::AFDGF" <AFDGF@ALASKA.BITNET>
- Lines: 20
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
-
- I have had several responses to my post about not being able to
- run a job on vms 6.06 but being able to run it on 6.07. The
- job was reading a sasdataset and format library. The dataset
- was 750 variables by 450 observations. The format library and
- dataset had been created in 6.06. The responses that I got to
- my post was that I did not have sufficient resource quotas on
- my account. Let me assure you that my quotas had been set to
- the max that my system manager could go. Also my system manager
- ran the same job on his account which had all the resources of the
- system and it bombed exactly in the same way. It also bombed when
- the statewide technical support person ran the job on 6.06. The
- job ran just fine when all three of us used 6.07. We have now
- tried it on other accounts that have much smaller quotas and the
- job works fine if we set the default to 6.07. It bombs on 6.06.
- I still maintain that vms users need to be very aware of what
- version they are running on and that 6.06 is very different in
- than 6.07. Good luck to all vms users.
- Dennis Fisher
- Center for Alcohol and Addiction Studies
- University of Alaska Anchorage.
-