hi -
I meant this not to dictate words, but just as a general comment that
friendly human-readable error messages are desirable; something that
will be meaningful to the end-user. Also that the application code
should be able to get those messages as a string to use in its own error
handling procedures.
Ansley
Dennis Heimbigner wrote:
ok, I see; there is a defined error code for server
side errors. It is NC_EDAPSVC,
and has the associated string: "NetCDF: DAP server side error"
I can certainly modify the error string to include the
... Please contact the adminstrator " to the message.
=Dennis
Ansley Manke wrote:
Hi Dennis,
Dennis Heimbigner wrote:
I dont think I follow this comment.
The log output is generally for debugging purposes
and I would not expect ordinary users to use it.
Rather, they will see a netcdf error such as NC_SVCERR
indicating a server side error. If they encounter that,
then someone more sophisticated can turn on logging and
see the details. The problem is that there is currently no
way to pass more detailed info thru the netcdf API.
I'm thinking along the lines of the NF_STRERROR(status) call which
takes an error code and returns an error string. It might be that
the string would be "error at the data server. Please contact the
administrator ..." Returning some words is better than
** unknown netCDF error code: -69
In any case, the error messages available after "setenv OCLOGFILE"
are highly useful. This output received by Ferret is much more
helpful than the error code alone. Can things be set so that the
application can get this kind of message? Could the Warnings and
Errors be separated so that we could get one and not the other?
=Dennis Heimbigner
_______________________________________________
netcdfgroup mailing list
netcdfgroup@xxxxxxxxxxxxxxxx
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
