NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Steve, In your script running from cron, make sure you source Gemenviron. If it works when run from your shell, it is probably inheriting values for GEMTBL from your environment. When run from cron, the shell will not have your .cshrc environment. Steve Chiswell Unidata User Support On Wed, 24 Mar 1999, Steven L. Mullen wrote: > Steve, > > A quick one where your insight would be valuable. > I am trying to use nagrib in a script to degrib some > some files downloaded from NCEP. When I maually > invoke the script, it runs flawlessly. But when I > schedule crontab to run the script, nagrib chokes > with errors shown below. My question: any hints > why the script/nagrib when run from cron can't > open GRIB decoding tables? This one baffles me. > > Regards, > Steve > > GBFILE = grib_1999032412 > INDXFL = > GDOUTF = 1999032412_mos.gem > PROJ = > GRDAREA = > KXKY = > MAXGRD = 9999 > CPYFIL = gds > GAREA = grid > OUTPUT = t > GBTBLS = ;tdlgrib2.tbl > GBDIAG = > GEMPAK-NAGRIB> Changing center table to cntrgrib1.tbl > Changing vertical coord table to vcrdgrib1.tbl > Changing WMO parameter table to wmogrib2.tbl > Changing center parameter table to tdlgrib2.tbl > [NA -1] The table tdlgrib2.tbl cannot be opened. > [NAGRIB 3] No valid parameter found for 220. > . > . > . > etc > > -- > ------------------------------------------------------- > {} Steven L. Mullen > {} {} Dept. of Atmospheric Sciences > {} {} {} University of Arizona > {} {} {} 1118 E. 4th St. > {}{}{} PO Box 210081 > {} Tucson, Arizona 85721-0081 > {} Tel:(520) 621-6842 > {} Fax:(520) 621-6833 > {} Email: address@hidden > ------------------------------------------------------- > > >