[NCO Bug] Display clear warning when missing snogrb file

[KateFriedman-NOAA]

What is wrong?

Bugzilla 1373

From bugzilla text from SPA Carlos Diaz:

In gfs_atmos_analysis, if the current gfs.t$CCz.snogrb_t1534.3072.1536 (from the 
gfs_atmos_emcsfc_sfc_prep job) is missing, the task proceeds normally with no clear warning.

Below are recommendations from George Gayno that there should be an alert if the file is missing:

"If the process that creates the snogrb file breaks somehow, the previous cycle's snogrb file is copied 
to the current directory. So the GFS will continue to run, even if snogrb is old. (GFS checks the date in
snogrb and if it is old, it does not apply the snow). 
Snow data is not 'critical'. The GFS should continue to run. But there should be an alert if the IMS or 
Air Force data are old so the problem can be investigated."

Please work to produce a clear warning if the file is missing as well as an email alert if needed.

What should have happened?

An alert should have been printed when snogrb used is old.

Steps to reproduce

Simulate no snogrb for current cycle and make system use older one.

Bugzilla issue

1373

Additional information

Reply from @RussTreadon-NOAA in bugzilla:

gfs_atmos_analysis and gdas_atmos_analysis execute j-job JGLOBAL_ATMOS_ANALYSIS.  This job,
in turn, executes exglobal_atmos_analysis.sh.   These jobs now reside in the NOAA-EMC/global-workflow
repository.  Therefore, reassign this bugzilla to EIB.  Add George Gayno to cc list since he maintains
gfs_atmos_emcsfc_sfc_prep.  The MDAB-DAQC team will support EMC staff in resolution of this bugzilla.

Do you have a proposed solution?

No response