- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Open statements in Fortran applications are compiled correctly but leads in execution to an unrecoverable failure.
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - gerd-paul.hoffmannt-online.de
Open statements in Fortran applications are compiled correctly but leads in execution to an unrecoverable failure.
A bit more info is required, I'm afraid. What's the error message?
A.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - gerd-paul.hoffmannt-online.de
Open statements in Fortran applications are compiled correctly but leads in execution to an unrecoverable failure.
Are the files you are reading created on a different system ?
Example code together with the error message(s) would also help.
Les
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As others as said, we'd need to see more to be much help. The following are just guesses:
If you are opening binary direct access files, check your record lengths. The default for CVF/IVF is to measure
in WORDS instead of BYTES. This behavior is changeable through compiler options.
If you are reading binary files created on other systems (or even with different compilers on the same system),
there can be all sorts of problems. Some of these (like "endianness") can be addressed with options in the
OPEN statements. On the other hard, if the files are unformatted (and not direct access), there's no standard
layout for this type of file, and you may find it difficult to read files created with another compiler or on a different
operating system.
In any case, add some more specific info on what is going wrong, and we may be able to point you in the
right direction.
If you are opening binary direct access files, check your record lengths. The default for CVF/IVF is to measure
in WORDS instead of BYTES. This behavior is changeable through compiler options.
If you are reading binary files created on other systems (or even with different compilers on the same system),
there can be all sorts of problems. Some of these (like "endianness") can be addressed with options in the
OPEN statements. On the other hard, if the files are unformatted (and not direct access), there's no standard
layout for this type of file, and you may find it difficult to read files created with another compiler or on a different
operating system.
In any case, add some more specific info on what is going wrong, and we may be able to point you in the
right direction.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page