Opened 13 years ago

Closed 12 years ago

#25 closed help (fixed)

setting size of STASH headers, pp0 (unit 60)

Reported by: arbetter Owned by: cwang
Component: Diagnostics Keywords:
Cc: Platform:
UM Version:

Description

Hi,

In my job xcftf, I eventually get an error like

ERROR detected in routine STWORK: stop model
: No. of output fields (= 4097 ) exceeds no. of reserved PP headers for unit 60
STASH : Error processing diagnostic section 15 , item 3 , code 4

STWORK : NO. OF FIELDS EXCEEDS RESERVED HEADERS

*
UM ERROR (Model aborting) :
Routine generating error: ST_DIAG1
Error code: 4
Error message:

STWORK : NO. OF FIELDS EXCEEDS RESERVED HEADERS

*

This appears to be a problem with saving to the xcftf.pp0 file (unit 60).

One way to avoid it might be to reduce the frequency in which data are saved
to the file (which I can do in Atmosphere → STASH → Specification of Diagnostic
Requirements).

But a more direct way would be to increase the number of reserved headers
to something greater than 4096. Poking around the UMUI and some of the
documentation, I haven't found where this can be done, though. Is it possible?

t

Change History (2)

comment:1 Changed 13 years ago by cwang

  • Status changed from new to assigned

Hi Arbetter,

Without changing the reserved header size, you can use different unit numbers to save different fields which is the way we do.

I just had a look at your job xcftf. You put quite a lot of fields into U0. You could arrange some of them to U2 or U5. You can do this by change the 'USAGE' field after clicking Atmosphere → STASH → Specification of Diagnostic Requirements within UMUI.

By the way, you can always do 'Verify diagnostics' from the menu 'Diadgnosts' on the same panel to see if each unit execeed reserved size before you submit the job.

Let me know if you have any problems.

Chang

comment:2 Changed 12 years ago by ros

  • Resolution set to fixed
  • Status changed from assigned to closed

Since this ticket has been dormant for a long time and we haven't been informed of any further problems this ticket is being closed.

Note: See TracTickets for help on using tickets.