[MITgcm-devel] [altMITgcm/MITgcm66h] Bugfix/scratch files (#11)

[Martin Losch]

Hi Jean-Michel,

I suggest to test this now as you say, i.e. check in an eeset_parms.F where only the appropriate close statements are ammended with STATUS=‘DELETE’ (which in my opinion should always work, since this option is F77 standard, but you never know …), but also have (at least) one testreport-verification-experiment use the USE_FORTRAN_SCRATCH_FILES flag, so that it is always tested (that’s a bit annoying, since it would be the only experiment with it’s own CPP_EEOPTIONS.h file, or can this be put into some genmake_local?)

Martin

> On 25. Jul 2017, at 18:17, Jean-Michel Campin <jmc at mit.edu> wrote:
> 
> An other thing:
> Are we 100% sure that closing a scratch unit file with status "delete" 
> is completly standard on all platforms & compilers ? If not, we could
> test just this independently (i.e., check-in and see how daily test run). 
> The reason is that when someone chose to use USE_FORTRAN_SCRATCH_FILES,
> (which is not going to be the default and therefore not tested) we need to be 
> sure that the close instruction is OK.