bug with open statement

[jvandeven]

I recently upgraded to VS2015 and IVF Composer 2016.  Since upgrading the Fortran compiler, the application I work with returns error code 30 on an OPEN statement.  A file is created, but cannot be written to.  I have tried various permutations of the OPEN statement including:

call get_unit( file_id )
open ( unit = file_id, file = file_name, status = 'replace', iostat = istat )
if ( istat.ne.0 ) then

    open ( newunit = file_id, file = file_name, status = 'replace', action = 'write', iostat = istat )
    open ( newunit = file_id, file = file_name, status = 'replace', iostat = istat )
    open ( newunit = file_id, file = file_name, iostat = istat )

None of these seems to help.  The affected code writes output to a number of CSV (comma separated varaible) files.  The OPEN statement works fine to begin with, but appears to fail after a sufficiently large number of data points have been written to disk (ie, it will write 10 variables of size X, and 8 variables of size Y, where Y>X).  I am returning to IVF Composer 2015, update 4 - which processes the data without incident - until this problem can be resolved.

I have tried doing a complete rebuild (both after "cleaning" the solution, and deleting the x64 working directory), tried working on different drives, tried rebooting the computer, and tried working on different computers.  None of these quick fixes helped.

Hope that someone is able to identify the root cause of this issue,

Justin.

[Steven_L_Intel1]

You certainly can submit it through Premier Support if your support license is current. Maybe one of our other support engineers will be able to reproduce it. (I will be away for the next 8 weeks so I won't be trying it myself.) I do encourage you to add the instrumentation to see if it shows an effect.

[jvandeven]

Steve Lionel (Intel) wrote:

You certainly can submit it through Premier Support if your support license is current. Maybe one of our other support engineers will be able to reproduce it. (I will be away for the next 8 weeks so I won't be trying it myself.) I do encourage you to add the instrumentation to see if it shows an effect.

I just saw your new posts here, so will try to implement the handles test and see what I get.  I will contact permier support once I know more.  Have a good break Steve, Justin.

[jvandeven]

I have run the instrumentation test for handle use, and can confirm that my routine's handle use explodes with PSXE16.0, and VS2010 or VS2015.  This isn't replicated using PSXE15.04 (see screen shots attached).  Using alternative libraries seems to have no effect in my case, so I suspect that it is something to do with with compiler set-up.  I therefore hope a resolution is found to DPD200375683.

[andrew_4619]

Hmmm , I might wait for update 1 before i deploy 16......

[jvandeven]

app4619 wrote:

Hmmm , I might wait for update 1 before i deploy 16......

With two others reporting the same issue (cited in above thread), and the issue being important for any application that writes large data files, I expect that it will be resolved quickly.  Nevertheless, I am following some of your earlier advice and logging the problem with premier support.  

[Lars_H_]

I am having the exact same issues with file writing.  Does anyone know if this has been resolved and when a software update will be available?

[Kevin_D_Intel]

Development reported the issue is fixed in the upcoming PSXE 2016 Update 1 that is due to release in a couple of weeks. I have not yet confirmed the fix myself yet but will do so soon.

[jvandeven]

This would be useful, as the issue has prevented me from migrating from the 15.4 to the 16. compiler.

[Simon_Geard]

I had exactly this problem and submitted it to Premier Support who have told me it has been marked 'must fix' for the next update so our migration assessment is on hold for that update.

To get your application working you could try removing the /threads flag - I think that circumvents the problem.

[Steven_L_Intel1]

I am told that this problem is fixed for 16.0.1 (2016 Update 1).

[jvandeven]

This is great news - do you know when 16.0.1 will be released?

[Steven_L_Intel1]

Later this week or sometime next week, so I am told. But testing is still in progress so this might slip.

[jvandeven]

This problem is resolved by the 16.0.1 compiler update - many thanks