# WRITE operation to a record that was too long **URL:** \ **Category:** Unified Model\ **Created:** [21 June 2021 08:26 UTC](https://cms-helpdesk.ncas.ac.uk/t/write-operation-to-a-record-that-was-too-long/86 "2021-06-21T08:26:21Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Leighton\_Regayre](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/leighton_regayre/32/20_2.png) [@Leighton\_Regayre](https://cms-helpdesk.ncas.ac.uk/u/Leighton_Regayre)\ **Post date:** [21 June 2021 08:26 UTC](https://cms-helpdesk.ncas.ac.uk/t/write-operation-to-a-record-that-was-too-long/86/1 "2021-06-21T08:26:21Z")
Hello, I have made some minor code changes to my UKESM suite u-ce487. The atmos\_main task crashes with the unrecoverable library error: ‘A WRITE operation tried to write a record that was too long’. I don’t know if the error is caused by my code changes, which I’ve double-checked, my choice of diagnostics, or some problem related to the python scripts that perturb values of namelists in my suite. Could you advise me how I might explore this further please? Thanks, Leighton ---
**Author:** ![grenville](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/grenville/32/29_2.png) [@grenville](https://cms-helpdesk.ncas.ac.uk/u/grenville)\ **Post date:** [21 June 2021 08:59 UTC](https://cms-helpdesk.ncas.ac.uk/t/write-operation-to-a-record-that-was-too-long/86/2 "2021-06-21T08:59:35Z")
Hi Leighton A the risk of being inconsistent - try switching off Extra DIagnostic Messages. Grenville ---
**Author:** ![Leighton\_Regayre](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/leighton_regayre/32/20_2.png) [@Leighton\_Regayre](https://cms-helpdesk.ncas.ac.uk/u/Leighton_Regayre)\ **Post date:** [22 June 2021 08:21 UTC](https://cms-helpdesk.ncas.ac.uk/t/write-operation-to-a-record-that-was-too-long/86/3 "2021-06-22T08:21:11Z")
Thanks for the suggestion Grenville. I changed the setting of ‘PRINT\_STATUS’ in um-\>Runtime\_Controls-\>Atmosphere\_Only so that ‘Extra diagnostic messages’ is false. But, the same error is repeated in my ‘u-ce487’ atmos\_main log file. Any idea how I can explore this further? Thanks, Leighton ---
**Author:** ![grenville](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/grenville/32/29_2.png) [@grenville](https://cms-helpdesk.ncas.ac.uk/u/grenville)\ **Post date:** [22 June 2021 13:55 UTC](https://cms-helpdesk.ncas.ac.uk/t/write-operation-to-a-record-that-was-too-long/86/4 "2021-06-22T13:55:06Z")
Leighton The suite still has eg atmos\_main002/rose-app-run.conf:PRINT\_STATUS=PrStatus\_Diag set PRINT\_STATUS=Operational status Grenville ---
**Author:** ![Leighton\_Regayre](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/leighton_regayre/32/20_2.png) [@Leighton\_Regayre](https://cms-helpdesk.ncas.ac.uk/u/Leighton_Regayre)\ **Post date:** [23 June 2021 07:30 UTC](https://cms-helpdesk.ncas.ac.uk/t/write-operation-to-a-record-that-was-too-long/86/5 "2021-06-23T07:30:35Z")
Hi Grenville, I understood from your earlier suggestion I should set the diagnostic messages to FALSE instead of TRUE, hence the PRINT\_STATUS was still set to PrStatus\_Diag. But, I have now set the PRINT\_STATUS to ‘Normal’ and set the ios\_verbosity to 2 (Normal). This will likely take a while to run, so hopefully the ticket isn’t automatically clsoed before I get results of this test. Thanks, Leighton ---
**Author:** ![Leighton\_Regayre](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/leighton_regayre/32/20_2.png) [@Leighton\_Regayre](https://cms-helpdesk.ncas.ac.uk/u/Leighton_Regayre)\ **Post date:** [23 June 2021 11:57 UTC](https://cms-helpdesk.ncas.ac.uk/t/write-operation-to-a-record-that-was-too-long/86/6 "2021-06-23T11:57:23Z")
Hi Grenville, My suite is running now, so reducing the verbosity of output and/or reducing the number of diagnostic messages seems to have done the trick. If you have time, it would be useful to have some insight into why this happens, since it is a counter-intuitive solution. Thanks, Leighton ---
**Author:** ![grenville](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/grenville/32/29_2.png) [@grenville](https://cms-helpdesk.ncas.ac.uk/u/grenville)\ **Post date:** [23 June 2021 15:24 UTC](https://cms-helpdesk.ncas.ac.uk/t/write-operation-to-a-record-that-was-too-long/86/7 "2021-06-23T15:24:42Z")
Leighton It’s trying to write a message but the message buffer it writes to is too small to hold it. The message maybe informative only (which seems to be the case since your model is running) - but extra diagnostics can be useful if it writes an error message short enough to fit in the buffer. I guess no one has found the time to fix the buffer problem. Grenville ---
**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/cms_support/original/1X/1fd2411499ffcbc299fe756cd5cdf26e44956558.png) [@system](https://cms-helpdesk.ncas.ac.uk/u/system)\ **Post date:** [24 June 2021 15:24 UTC](https://cms-helpdesk.ncas.ac.uk/t/write-operation-to-a-record-that-was-too-long/86/8 "2021-06-24T15:24:48Z")
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.