Greetings,
I am progressing with my attempt to update a legacy Fortran 77 solution to use some of the newer Fortran capabilities (as least those that I think I somewhat understand :-)) and have run into my latest problem being a runtime error 37:
This solution is a Fortran DLL called by a Fortran exe and was working until some recent modifications. The EXE runs to completion when run through the Visual Studio IDE in Debug or Release; however, when I copy the DLL and EXE to a separate folder the error is produced. The EXE is actually a batch processor that processes multiple files through the DLL, and the first file executes to completion with error 37 being produced on the second file. From what I have read error 37 indicates that an attempt was made to open a direct access file without specifying a record length. I have set the runtime library setting to Multithread DLL on both the EXE and DLL projects. Although my program does use a unit 14, I don't think this is the actual problem as another user in the forum also had unit 14 show up several years ago, and it sounded like his fix was in the runtime library setting.
Bill
Link Copied
Steve,
None of the cut off file names are associated with the subroutine that opens unit 14. The EXE is a small driver program containing a loop that repeatedly opens an input file from a list of about 150 test files and calls the DLL for processing the file data and continues until the list has been completely processed. I have tried turning on all of the runtime checking (using both Debug and Release versions) and found several problems that, while I'm very glad they were caught, did not solve the error 37. I reviewed this forum topic: https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/475951 which I guess by coincidence also had a problem with unit 14. The code for opening unit 14 looks like this:
RLF is defined elsewhere as a parameter of 4, yielding RECL of 1152. JROT has the SAVE attribute assigned to it. I tried using RECL=1152 and still had error 37 when run outside of the Visual Studio IDE; it works fine inside VS IDE and all test files run to completion through the EXE-DLL interaction process. Unit 14 (as well as all open units) are closed at the conclusion of the DLL. I just tried adding write statements at line 44 and 49 of the code above and see the following in the results of the first file of the list:
The second file where the error 37 occurs never reached the line 44 write statement, so I don't think the problem is here. I may have a data corruption somewhere, as I don't know it I ever really solved the corruption problem noted in my previous forum post, although variable DSTMOM is behaving now :-) at least per comparison with saved test file results. Problems can be very difficult to find if they are not an explicit catch by the compiler.
Bill
Jim,
Here is how JROT is initialized:
I will read about the environment variables and let you know if I have questions, thanks.
Bill
