Fortran input conversion error-reg..

[parasuraman]

Dear All,
Greetings. I am trying to read from a data file which contain numerical information and occupies 22GB disk space. The program is getting compiled and when trying to run the a.out, i get these error messages.

I am using RHEL5.4. As to the hardware, the RAM is 4GB and HDD is 250GB. I am using fortran compiler 9.1 for linux.

I tried to run the same program in an IBM server (X3550M2) with CentOS. I am using 64bit intel compiler downloaded from intel site(very recent compiler). I got the same error.


Can anybody help me to solve the problem?


Error
forrtl: severe (64): input conversion error, unit 2, file /home/parasu/data/all.dat

Image PC Routine Line Source
a.out 000000000047638A Unknown Unknown Unknown
a.out 0000000000474E86 Unknown Unknown Unknown
a.out 00000000004551C0 Unknown Unknown Unknown
a.out 000000000043EB4E Unknown Unknown Unknown
a.out 000000000043E08F Unknown Unknown Unknown
a.out 00000000004107F2 Unknown Unknown Unknown
a.out 0000000000403453 Unknown Unknown Unknown
a.out 0000000000402ABC Unknown Unknown Unknown
libc.so.6 00000035A5E1EC5D Unknown Unknown Unknown
a.out 00000000004029B9 Unknown Unknown Unknown

Thanks in advance

[mecej4]

There is probably a mismatch between what type and format of data the READ statement expects and what it found in the data file. It is also possible that the error is caused by earlier READ statements consuming more/fewere lines of input than the programmer expected.

Don't expect any specific answers because you have not given sufficient detail. Considering the size of the data file, most readers here would not want that detail, either. You will have to hunt for the bug.

[Lina_F_]

 I am facing similar problem as mentioned above. Is there any quick way to fix this?

[Lina_F_]

Dear all,

I am facing similar problem as mentioned above. Is there any quick way to fix this? I am using ubuntu 14.04 LTS and intel fortran composer xe  2013. sp1

Thanks in advance!

[Steven_L_Intel1]

mecej4's answer in post #2 still applies. The only way to fix it is to figure out what data is being read and which format it is supposed to be in. Sometimes you can get this error if the wrong number of values were read earlier.