Hello, I have checked this curious thing, and can confirm that the missing "INTEGER bi,bj" in aim_do_inphys.F was responsible for the strange behaviour of the 2D solver in the 4cpu run on cote (d') azur. Same run on 1 cpu (no JAM, no MPI) with same compiler was OK. See you, Jean-Michel