Browse other questions tagged fortran fortran90 or ask your own question. But when I'm working on a machine that is installed win 7, it works and I do not have this message ! MP=10 INQUIRE(file='output.out',exist=FILE_EXIST) IF(FILE_EXIST)THEN OPEN(10,file='output.out',STATUS='OLD') when I'm working on a machine that is installed windows 7, it works and I do not have this message ! opening 'file open' dialog from console 12.
Comment 7 Jerry DeLisle 2008-11-15 19:13:52 UTC Subject: Re: "file already opened in another unit" error when opening /dev/null or /dev/tty twice > Which OP? GCC Bugzilla – Bug38122 "file already opened in another unit" error when opening /dev/null or /dev/tty twice Last modified: 2009-01-18 01:33:12 UTC Home | New | Browse | Search | [?] Try 'man 4 null' and 'man 4 tty' on your Redhat box. > Regardless, it's code that runs in an older version that doesn't run > in a new version. HTH.
APPEL ET EXECUTION DU BLOC 'IMAG' ! DU NOEUD(',I4,') EST SUPERI & &EUR A NDLN=',I4) GO TO 900 140 WRITE(MP,2140) 2140 FORMAT(' ***ERREUR, LES NUMEROS DU PREMIER ET DU SECOND NOEUDS & &SONT INCOMPATIBLES AVEC L INCREMENT DE HTH. --Dave Tue, 19 Apr 2011 01:29:16 GMT dpb#3 / 43 opening file twice... Retry, Abort?" Or something like that.
When you create a new source file, you have the option of fixed-form source. It's no different than building free-form source. LECTURE DES COORDONNEES DES NOEUDS !======================================================================== IMPLICIT REAL*8(A-H,O-Z) REAL*4 TBL COMMON/COOR/NDIM,NNT,NDLN,NDLT,FAC(3) COMMON/ALLOC/NVA COMMON/ES/M,MR,MP,M1 COMMON/LOC/LCORG,LDLNC COMMON/TRVL/FAC1(3),IN(3) !c COMMON VA(1) DIMENSION TBL(2) DATA ZERO/0.D0/,TBL/4HCORG,4HDLNC/ !--------------------------------------------------------------------------- !--------- EN-TETE DE BLOC print*,'DEBUT DE BLCOOR *-*-*-*-' This code is used by the vendor to identify the error caused.
Hardly Standard-conforming. > Could you give some pointer related to this topic, please? ... www.quickthreadprogramming.com Top jimdempseyatthecove Wed, 03/04/2009 - 08:16 (Damb edit window wouldn't let me type past pasted text...) What you might want to consider to close the race condition window is a Quote:> Or... My training was that > Unix-like file systems allow multiple read access on the same file.
If you opened it with write or readwrite status you will probably get an error on the open statement instead! If you want to have multiple > tghreads doing I/O to the same file, you pretty much had better be aware > that the whole business is nonstandard and has potential Why is absolute zero unattainable? Quote: >> Also recall I told OP I normally did such things w/ OS APIs, typically >> memory mapped files.
The only point of the first OPEN was to allow the subsequent CLOSE statement to delete the file if it existed or to error trap a problem. How should I interpret "English is poor" review when I used a language check service before submission? This Fortran Runtime Error File Already Opened In Another Unit error code has a numeric error number and a technical description. NVA=20000 NVA = 2000000 !----------------------------------------------------------------------- !--------initialisation------------------------------------------------- ! ! ! !------- READING OF FILES INPUT-OUTPUT---------------------------------- !
Of course, recall also that the OP said he needed this because of threads. But in Fixed form, there is only "Solution(0projets)" so I can not Build this Solution!! Given the topic you > can not expect to be very lucky. If anyone sees any other Fortran Standard specifics we may be missing, let me know so I can fix those.
This problem will cause people to use the old version > of the compiler. You seem to have CSS turned off. Alternatively, let the project wizard create the new project with free-form source. And in the real molecular dynamics simulations you have millions of particles.
Try adding: CALL SLEEPQQ(500) after the CLOSE. Mon, 04/14/2014 - 08:34 Hi Steve, I have the same problem when I am working on a machine that win 8.1 is installed. Reason, Windows may defer the actual deletion, and your OPEN to create may occur before the file is actually deleted. Quote:> Sun fortran and XLF 8.1 accept this without complaint.
Race condition here IF (FILE_EXIST) THEN ! ** existing file on INQUIRE might not exist at time of OPEN OPEN(90,FILE=DsnProfExportName, ACTION = 'WRITE', STATUS='OLD', ERR=100) CLOSE(90,STATUS='DELETE') END IF ! ** If Thank you for your help Top andrew_4619 Tue, 04/15/2014 - 02:46 That compiles OK, I presume you mean runtime errors? net | experience comes from bad judgment. This website should be used for informational purposes only.
Note that Windows makes it difficult to run programs that write to folders under Program Files. They have a tendency to pass test cases and then fail miserably in actual application. (And yes, I'm reasonably sure that you are aware of all this, Gordon; it isn't directed Top Steve Lionel (Intel) Tue, 03/03/2009 - 16:24 Is this excerpt faithfully representative of your actual application, or is it a "paraphrase"? comment:4 Changed 6 years ago by jr_reuter Milestone v2.0.0final deleted Milestone v2.0.0final deleted Note: See TracTickets for help on using tickets.
Comment 6 kargl 2008-11-15 17:28:39 UTC (In reply to comment #5) > > I do believe that one could write a standard conforming "layer" in Fortran to > handle all of One point made there is that gfortran should not reposition the file after a reopen as the default position= specifier should be ASIS. While gfortran tries to provide backwards compatibility with g77, the author of g77 made several questionable choices with violating the Fortran 77 Standard. Vendors hope you will use their nonstandard convenience extension so you will not be able to use any other vendors compiler.
Mostly, because it's impossible to specify what it could mean on a wide variety of systems.