Improve the error/warning message handling in analysis and forecast jobs (v2.5) (bugzilla #1638)

[DanIredell-NOAA]

http://www2.spa.ncep.noaa.gov/bugzilla/show_bug.cgi?id=1638

New (per v2.5 upgrade) and preexisting bugs collected herein.

Preexisting:
In all preexisting cases the current message does not include ‘FATAL ERROR’ for fatal errors or ‘WARNING’ for non-fatal/warning errors. Please include this language as needed.

• scripts/exrtofs_glo_post.sh (analysis_post, forecast_post_d0?): echo Post timed out, arfile_tplate not available after $icnt_max iterations.
• scripts/exrtofs_glo_post.sh (analysis_post, forecast_post_d0?): echo Missing file $fn, will not be able to run
• ush/rtofs_atmforcing_getges.sh (analysis_pre, forecast_step{1,2}_pre): echo getges.sh: filetype $typef or resolution $resol not recognized >&2

New:
When a corrupt GRIB2 file is encountered, these instances should be able to be handled/reported with messaging that includes ‘FATAL ERROR’ for fatal errors or ‘WARNING’ for non-fatal/warning errors. Please address this fatal error.

• ush/rtofs_atmforcing.sh (analysis_pre, forecast_step{1,2}_pre): rtofs_atmforcing call on line 133 produces a non descriptive error message when testing corrupt GDAS/GFS flux GRIB2 files. This is likely a wgrib2 generated error, not from rtofs (FATAL ERROR: rtofs_global_analysis_pre return code 174) and other info from searching elsewhere in the output file (mod_gribio: opening IDX as unit 42; getgb2 error = 99 ip 0).

[DanIredell-NOAA]

Updated scripts/exrtofs_glo_post.sh, scripts/exrtofs_glo_post.sh, and ush/rtofs_atmforcing_getges.sh with the appropriate keyword in the message. Keyword is either FATAL or WARNING depending of the severity of the error.

Not done was any change to ush/rtofs_atmforcing.sh when encountering a corrupted grib file. This script will be changed for V3.0 and the executable rtofs_atmforcing probably will not exist anymore.