forums.silverfrost.com

Emerson00 · Joined: 09 Dec 2013 Posts: 4

Getting this error message:
Runtime error from program:c:\fortran\xxxxxx121413\debug\win32\bubec.exe
Run-time Error
*** Error 29, Call to missing routine : _FLUSH at 0x0040200e.

main - in file xxxxxx.f at line 192 [+1013] [recur= 1]

Background:
Professor assigned a semester project to get an old code running that he wrote in 1993, and make some modifications to it. It runs on the University systems, but my computer can't log in for some reason, so I'm trying to run it on Silverfrost. I think I've worked through most of the issues, but for some reason it's failing on FLUSH. Is there a means of putting a Flush subroutine into the folder/project? Is there a better way to get it running? I thought FLUSH was a standard Fortran routine.

I haven't used Fortran since 1995. Embarassed

IanLambley · Joined: 17 Dec 2006 Posts: 506 Location: Sunderland

FLUSH seems to be a non-standard function. It is available in GNU Fortran.
If the file you are flushing is a sequential file, then you could try something like:

davidb · Joined: 17 Jul 2009 Posts: 560 Location: UK

Ian is correct. Flush isn't standard,

Try calling this:

DanRRight · Posted: Tue Dec 10, 2013 6:35 pm Post subject:

Would be great to see FLUSH function (of Fortran 2003) in FTN95.
One of the third party very confusing codes I use may hiccup due to our FLUSH workaround

Emerson00 · Joined: 09 Dec 2013 Posts: 4

Thanks, all. Off to try it now.

<- not a programmer... very appreciative of the help!

Emerson00 · Joined: 09 Dec 2013 Posts: 4

Ok so I dropped the shorter of the two into the code in place of Flush as follows:

old code:

davidb · Joined: 17 Jul 2009 Posts: 560 Location: UK

No! As you have it, the program won't compile.

Just write the FLUSH function as I have written it. Then it will work.

The dummy argument name should be UNIT. When you make your call this will be given the value of 1.

Don't worry about the INTENT(IN).
_________________
Programmer in: Fortran 77/95/2003/2008, C, C++ (& OpenMP), java, Python, Perl

JohnCampbell · Joined: 16 Feb 2006 Posts: 2615 Location: Sydney

Why are you using unit 1 ?
This is a special unit for screen I/O.
I would not open a file on this unit ??
Some compilers use units 5 and 6 for screen I/O; FTN95 uses unit 1.

Not sure if this is the main reason for your problems.

John

davidb · Joined: 17 Jul 2009 Posts: 560 Location: UK

I think the OP is trying to write an indication of progress to the screen, in which case unit 1 is correct.

Strictly speaking you are supposed to be able to open files on any of the pre-connected units. But some compilers have problems doing this reliably. If unit 1 is supposed to be connected to a file, then better heed John's warning and change to something else.
_________________
Programmer in: Fortran 77/95/2003/2008, C, C++ (& OpenMP), java, Python, Perl

JohnCampbell · Joined: 16 Feb 2006 Posts: 2615 Location: Sydney

Why would you require a buffer flush on unit 1 ?
I thought the main use of flush is when you trap an exception or error and want to clear the file buffers or for some mult-process communication.
Unit 1 should not require this approach.

John

davidb · Joined: 17 Jul 2009 Posts: 560 Location: UK

I have sometimes needed flush on the screen (perhaps not for some years now).

I agree that in this modern age, the OP probably doesn't need the Flush and could just delete this line.
_________________
Programmer in: Fortran 77/95/2003/2008, C, C++ (& OpenMP), java, Python, Perl

Emerson00 · Joined: 09 Dec 2013 Posts: 4

Thanks, all. Will try again this evening. I tried running it with the exact code provided, and the compiler started returning problems with c*************** which only occurs up in the descriptive header and hasn't been an issue before. I'm going to start fresh this evening and see what happens.

For what it's worth, the code references a couple of external files, and the bubout.dat file was referenced as Unit=1, so I assumed (yeah, yeah) it was necessary to clarify which file.

IanLambley · Joined: 17 Dec 2006 Posts: 506 Location: Sunderland

Due to the units 1, 2, 5 & 6 being preconnected to the keyboard and screen, depending upon the compiler, then using them for file IO, disconnects their original use. For file IO try adding 10 to all the unit numbers and leave the console items as they are.

Try running this program to find the preconnected channels:

DanRRight · Posted: Sat Dec 14, 2013 5:58 pm Post subject:

Besides those units the logical unit 0 is also special. It is equivalent in FTN95 to write(*,*) but in other Fortran compilers (like GNU for example) it was and still is used as a "console" unit (older ages therminology) with obviously higher priorities (like not allowing the stream to unit 0 to be redirected to anything else, the file or printer)