DIGITAL Visual Fortran 5.0

From: alison@c255.ucsf.EDU (ABoeckmann) Subject: DIGITAL Visual Fortran 5.0 Date: 18 Jul 1997 12:55:37 -0400 To NONMEM users with PC's and DIGITAL Visual Fortran 5.0: In May I sent email suggesting DIGITAL Visual Fortran 5.0 as an alternative to the discontinued Microsoft Fortran PowerStation. I said: "The command that invokes Fortran 5.0 is "df" and it has a totally new set of options. However, for the sake of customers who are moving from Powerstation, it can also be invoked as "fl32", and the old options are recognized. (Old command; new compiler!) It detects which command was used, and has different defaults for "df" vs. "fl32", but recognizes both sets of options." It turns out that there is a known bug when the "fl32" command is used (DIGITAL's "PowerStation I/O compatibility mode"). This bug does not exist when the "df" command is used (DIGITAL's "native DIGITAL Fortran I/O"). It does not exist with Microsoft PowerStation Fortran's fl32 command. When NM-TRAN is processing a relatively large file (e.g., the size of the PHENO file on the release medium, approx. 745 lines), the bug causes NM-TRAN to fail with the message AN ERROR WAS FOUND IN THE CONTROL STATEMENTS. THE CHARACTERS IN ERROR ARE: FWORK 36 ERROR HAS OCCURED WHILE CREATING REQUIRED FILE. A similar error occurs in NONMEM with large files. The workaround is simple. With DIGITAL Visual Fortran 5.0, all compiles of NONMEM, PREDPP, and NM-TRAN should be done using the "df" command rather than "fl32". ----------------------------------------------- Note to people who received the Installation Notes memo dated May 13, 1997: In every case, simply change fl32 to df in the lines marked with (DF). For NONMEM and PREDPP: df /c /fpe:0 /optimize:1 *.for For NM-TRAN: df *.for For NONMEM executable, use either of the below depending if the nmfe.bat file is used or not used: df /fpe:0 /optimize:1 fsubs.for @link.lnk \nmiv\nm\*.obj df /fpe:0 /optimize:1 fsubs.for @adv2tr1.lnk \nmiv\nm\*.obj