DO
READ(11,'(a)',iostat=IERR)line
IF ((line(1:2)/='--').and.(line/=' '))THEN
READ(line,*,iostat=IERR) posinumber
EXIT
ENDIF
ENDDOiostat=IERR, ERR=100100 IF (IERR .EQ. FOR$IOS_FILNOTFOU) THEN
WRITE (6,*) 'File: ', FILNM, ' does not exist '
ELSE IF (IERR .EQ. FOR$IOS_FILNAMSPE) THEN
WRITE (6,*) 'File: ', FILNM, ' was bad, enter new file name'
ELSE
PRINT *, 'Unrecoverable error, code =', IERR
STOP
END IFjim mcnamara said:It means to store the result of the I/O operation in the variable IERR.
A more useful construct - this braches to the 100 line label on error. At line 100 test the value of the IERR variable to find the error number. You have to code the test somewhat like this:Code:iostat=IERR, ERR=100
Some of the above example is FORTRAN implementation-specific - meaning those FOR$xxxxx constants are not guaranteed to exist for your flavor of FORTRAN. Eeee. I haven't looked at FORTRAN for a long time.Code:100 IF (IERR .EQ. FOR$IOS_FILNOTFOU) THEN WRITE (6,*) 'File: ', FILNM, ' does not exist ' ELSE IF (IERR .EQ. FOR$IOS_FILNAMSPE) THEN WRITE (6,*) 'File: ', FILNM, ' was bad, enter new file name' ELSE PRINT *, 'Unrecoverable error, code =', IERR STOP END IF
You are absolutely right. It doesn't run actually. I was given an assignment to fix this and make it run. I am really new to this so I am pretty much clueless. Do you think you can help me in private?jim mcnamara said:You have what appears to be a 'code snippet' - meaning a piece of incomplete code - I do not know if your FORTRAN compiler will compile and run it. Too many years have elapsed...
1. it is a format specifier - this tells the compiler what kinds of input to expect
2. it is a variable, presumably it stores positive numbers - in coding your should give meaningful names to variables.
jedishrfu said:Your first read is reading data from file 11 and placing it in the "line" variable. I think the "(a)" means read it as text ie alphanumeric data.
The "if" statement looks at the first two characters of the "line" variable to see if its "--" or two spaces and if NOT then it processes the second "read" statement
The second "read" statement is reading from whatever file the "line" variable now holds.
I would look at the file read by the first "read" statement to see what's inside it and piece that information together with what your program is doing to get an understanding of what's actually going on.
ydonna1990 said:What about this nCtrl here. I googled and found that it means node control. What does that mean?
IERR stands for "internal error." In FORTRAN, it is a specific type of error that occurs when the program detects an error in its own internal operations, rather than an error in the input or output of the program. IERR is typically used to indicate a problem with the program's logic or structure.
In FORTRAN, IERR is typically detected through the use of the "IF IERR" statement. This statement checks the value of the IERR variable and executes a specific set of instructions if the value is non-zero. Programmers can also use the "IERR=0" statement to reset the IERR variable to zero, indicating that no internal errors have been detected.
IERR can be caused by a variety of factors, such as incorrect syntax or logic errors in the program, insufficient memory or storage space, or unexpected input data. It can also be caused by a failure in the compiler or other system software used to run the program.
To prevent IERR in FORTRAN, it is important for programmers to carefully review and debug their code, ensuring that all syntax and logic errors have been addressed. Additionally, proper memory management and handling of input data can help prevent unexpected errors from occurring.
In addition to IERR, other common error types in FORTRAN include syntax errors, logical errors, and runtime errors. Syntax errors occur when the code does not follow the proper syntax rules of the language. Logical errors occur when the code does not produce the expected output due to incorrect logic or calculations. Runtime errors occur during the execution of the program and can be caused by factors such as invalid input data or insufficient memory.