[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 19990813: NCSNC problem with netCDF v3.4

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.

  • Subject: Re: 19990813: NCSNC problem with netCDF v3.4
  • Date: Tue, 17 Aug 1999 10:09:08 -0600
Carlie,

>Date: Tue, 17 Aug 1999 11:56:47 -0400 (EDT)
>From: Carlie Coats <address@hidden>
>Organization: MCNC/NCSC Environmental Programs
>To: address@hidden (Steve Emmerson)
>Subject: Re: 19990813: NCSNC problem with netCDF v3.4
>Keywords: 199908101517.JAA21345

In the above message, you wrote:

> Since I'm working through an API layered on top of the netCDF2
> interface, that is a new one for me.  No, the NC_SHARE mode-bit 
> was not turned on;

The behavior you're observing is consistent with the NC_SHARE mode-bit
not being set.

> will the v2 interface function still work with
> IOR(NF_NOCLOBBER, NF_SHARE) as its mode-argument?

It should.  Let me know if it doesn't.

Information on the NF_SHARE mode-bit (which is appropriate for the
Fortran API) can be found at the following URL:

    
<http://www.unidata.ucar.edu/packages/netcdf/guidef/guidef-10.html#HEADING10-0>

Scroll down to the NF_CREATE function.

Please let me know if this helps.

--------
Steve Emmerson   <http://www.unidata.ucar.edu>