Im sure Ive done this before in the payu framework, almost certain. WRITE(,) statements from within the UM are prone to problems. WRITE(6,) statements forces write to std out. In pay’s case access.out. I actually recall watching the atm.fort.pe files and watching my diagnostics being written. I put a WRITE(6,) in place yesterday, I searched, I restored config.yaml back so that the ONLY difference from the working job it cloned was the module it picked up for um7 (pr28-34(33)). PR28-33(34) are built from um7:22-land-…. PR28-33 corresponds to failed WRITE(6,). I considered this was due to payu re-defining a std.out in some other place so I tried to write to an external file. PR28-34 corresponds to failed write to external file.
It would be helpful to at least be able to see the code that PR28-33(34) is building. Any ideas?
