- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We have upgraded to ivf 11.1 and we found that when we write to unit 6 we get a runtime error when there is no console window opened.
Normally a console window is only opened when we are testing our app.
Unit 6is opened with this code:
open(6,file='con',carriagecontrol='list')
WhenI want to print some diagnostic text I use:
write(6,'(a)') 'Error text'
The app crashes and traceback info points to the write statement.
The error is: Error during write, unit 6, file con.
This was no problem with ivf 9.1 Output just went to the bitbucket.
Changing the code to write to a file or other output is no option because we have mixed console and windows apps which share parts of our codebase.
Does someone know how to get around this problem? Or do I have to suibmit my problem to intel support?
Michel.
Normally a console window is only opened when we are testing our app.
Unit 6is opened with this code:
open(6,file='con',carriagecontrol='list')
WhenI want to print some diagnostic text I use:
write(6,'(a)') 'Error text'
The app crashes and traceback info points to the write statement.
The error is: Error during write, unit 6, file con.
This was no problem with ivf 9.1 Output just went to the bitbucket.
Changing the code to write to a file or other output is no option because we have mixed console and windows apps which share parts of our codebase.
Does someone know how to get around this problem? Or do I have to suibmit my problem to intel support?
Michel.
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In my opinion, the new behavior is correct and the old one was a bug. You could just add IOSTAT=IOS to the WRITE and ignore the error.

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