This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Eowyn, That error number corresponds to a "system error" rather than a netCDF-specific error. If you could run the command ncdump FILENAME on the file, it would probably give you a more helpful error message, as the ncdump program prints a human-readable error message instead of an error number. You might also try another program on the file, such as ls -l FILENAME which should also provide a readable error message. If that says the file doesn't exist, make sure all the intermediate directories in the file name exist and are readable by using the ls command, as in ls -l /project/tss/eowyn/testing --Russ Russ Rew UCAR Unidata Program address@hidden http://www.unidata.ucar.edu Ticket Details =================== Ticket ID: OKF-439434 Department: Support netCDF Priority: Normal Status: Closed