NCEPLIBS-bufr
11.6.0
|
Define a customized maximum length for output BUFR messages. More...
Go to the source code of this file.
Functions/Subroutines | |
subroutine | maxout (MAXO) |
This subroutine allows the user to define the maximum length of a BUFR message that can be written to an output file by the BUFRLIB software. More... | |
Define a customized maximum length for output BUFR messages.
Definition in file maxout.f.
subroutine maxout | ( | MAXO | ) |
This subroutine allows the user to define the maximum length of a BUFR message that can be written to an output file by the BUFRLIB software.
This subroutine can be called from within an application program at any time after the initial call to subroutine openbf(), and the specified value MAXO will then be used for all future BUFR messages written by the software to all output files for the remainder of the program, unless another call is made to this same subroutine to reset the value of MAXO again. Otherwise, if this subroutine is never called, a default maximum message length is used for all output files, as set via an initial internal call to subroutine bfrini().
[in] | MAXO | – integer: New maximum length (in bytes) for all BUFR messages written to all output files
|
Program history log:
Date | Programmer | Comments |
---|---|---|
2002-05-14 | J. Woollen | Original author |
2004-08-09 | J. Ator | Maximum message length increased from 20,000 to 50,000 bytes |
2006-04-14 | J. Ator | Added MAXO=0 option and overflow check |
2009-03-23 | D. Keyser | No longer print record length change diagnostic if requested record length is the same as the previous value |
2009-04-21 | J. Ator | Use errwrt() |
2014-12-10 | J. Ator | Use modules instead of COMMON blocks |
2015-09-24 | D. Stokes | Correct typos in docblock |
Definition at line 38 of file maxout.f.
References errwrt().
Referenced by split_by_subset().