home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Newsgroups: bit.listserv.sas-l
- Path: sparky!uunet!paladin.american.edu!auvm!uvvm!klassen
- References: <SAS-L%92072120431304@VTVM2.BITNET>
- Message-ID: <92204.102030KLASSEN@UVVM>
- Date: Wed, 22 Jul 1992 10:20:30 PDT
- Reply-To: Melvin Klassen <KLASSEN@UVVM.BITNET>
- Sender: "SAS(r) Discussion" <SAS-L@UGA.BITNET>
- Comments: Warning -- original Sender: tag was NETNEWS@UVVM.UVIC.CA
- From: Melvin Klassen <KLASSEN@UVVM.BITNET>
- Subject: Re: LIMDEP on IBM
- Lines: 16
-
- 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.
-