FAST IDL Software: cdf

This page was created by the IDL library routine mk_html_help2.

Last modified: Thu Oct 7 03:00:58 1999.


C , E , M , P , R

Directories Searched:


Directory Listing of Routines

Alphabetical List of Routines


Routine Descriptions

CDF.PRO[1]

[Next Routine] [List of Routines]
 NAME:
       cdf.pro

 PURPOSE:
       `cdf.pro' is used to create a set of local variables containing the
       general constants used by the CDF library.  The CDF status codes are
       defined by `cdf1.pro' and the CDF Internal Interface constants are
       defined by `cdf2.pro'.

       This include file is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       IDL> @cdf.pro

 RESTRICTIONS:
       The use of `cdf.pro' may result in too many local variables being
       created.  If that occurs, consider using `cdf0x.pro' instead.

 REVISION HISTORY:
       26-Jun-95        Original version.
       21-Aug-96        CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdf.pro)


CDF.PRO[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       cdf.pro

 PURPOSE:
       `cdf.pro' is used to create a set of local variables containing the
       general constants used by the CDF library.  The CDF status codes are
       defined by `cdf1.pro' and the CDF Internal Interface constants are
       defined by `cdf2.pro'.

       This include file is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       IDL> @cdf.pro

 RESTRICTIONS:
       The use of `cdf.pro' may result in too many local variables being
       created.  If that occurs, consider using `cdf0x.pro' instead.

 REVISION HISTORY:
       26-Jun-95        Original version.
       21-Aug-96        CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/include/cdf.pro)


CDF.PRO[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       cdf.pro

 PURPOSE:
       `cdf.pro' is used to create a set of local variables containing the
       general constants used by the CDF library.  The CDF status codes are
       defined by `cdf1.pro' and the CDF Internal Interface constants are
       defined by `cdf2.pro'.

       This include file is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       IDL> @cdf.pro

 RESTRICTIONS:
       The use of `cdf.pro' may result in too many local variables being
       created.  If that occurs, consider using `cdf0x.pro' instead.

 REVISION HISTORY:
       26-Jun-95        Original version.
       21-Aug-96        CDF V2.6.

(See cdf/cdf_ssl/cdf.pro)


CDF0.PRO[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       cdf0.pro

 PURPOSE:
       `cdf0.pro' is used to create a set of structure variables containing
       the constants used by the CDF library.  The structures created and
       their contents are as follows...

               CDFconst     - General CDF constants.
               CDFdataType  - Data type codes.
               CDFencoding  - Encoding codes.
               CDFdecoding  - Decoding codes.
               CDFiCode     - Informational status codes.
               CDFwCode     - Warning status codes.
               CDFeCode     - Error status codes.
               CDFiiFnc     - Internal Interface functions.
               CDFiiItem    - General Internal Interface items.
               CDFiiItemA   - Internal Interface attribute items.
               CDFiiItemE   - Internal Interface entry items.
               CDFiiItemR   - Internal Interface rVariable items.
               CDFiiItemZ   - Internal Interface zVariable items.

       These structures contain the same values defined using the `cdf.pro',
       `cdf1.pro', and `cdf2.pro' batch files.  To see the contents of each
       structure, use the command...

               IDL> help, /structure, <structure-name>

       The use of these structures eliminates the problem of too many local
       variables caused by the use of `cdf.pro', `cdf1.pro', and `cdf2.pro'.

       This include file is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

       If the lengths of these structure names are longer than desired,
       consider using `cdf0x.pro' instead.

 CALLING SEQUENCE:
       IDL> @cdf0.pro

 EXAMPLE:
       IDL> @cdf0.pro
       IDL> status = CDFlib (CDFiiFnc.OPEN_, CDFiiItem.CDF_, 'rain2x', id, $
       IDL>                  CDFiiFnc.NULL_)
       IDL> if (status lt CDFconst.CDF_WARN) print, 'CDF not opened...'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       26-Jun-95       Original version.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdf0.pro)


CDF0.PRO[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       cdf0.pro

 PURPOSE:
       `cdf0.pro' is used to create a set of structure variables containing
       the constants used by the CDF library.  The structures created and
       their contents are as follows...

               CDFconst     - General CDF constants.
               CDFdataType  - Data type codes.
               CDFencoding  - Encoding codes.
               CDFdecoding  - Decoding codes.
               CDFiCode     - Informational status codes.
               CDFwCode     - Warning status codes.
               CDFeCode     - Error status codes.
               CDFiiFnc     - Internal Interface functions.
               CDFiiItem    - General Internal Interface items.
               CDFiiItemA   - Internal Interface attribute items.
               CDFiiItemE   - Internal Interface entry items.
               CDFiiItemR   - Internal Interface rVariable items.
               CDFiiItemZ   - Internal Interface zVariable items.

       These structures contain the same values defined using the `cdf.pro',
       `cdf1.pro', and `cdf2.pro' batch files.  To see the contents of each
       structure, use the command...

               IDL> help, /structure, <structure-name>

       The use of these structures eliminates the problem of too many local
       variables caused by the use of `cdf.pro', `cdf1.pro', and `cdf2.pro'.

       This include file is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

       If the lengths of these structure names are longer than desired,
       consider using `cdf0x.pro' instead.

 CALLING SEQUENCE:
       IDL> @cdf0.pro

 EXAMPLE:
       IDL> @cdf0.pro
       IDL> status = CDFlib (CDFiiFnc.OPEN_, CDFiiItem.CDF_, 'rain2x', id, $
       IDL>                  CDFiiFnc.NULL_)
       IDL> if (status lt CDFconst.CDF_WARN) print, 'CDF not opened...'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       26-Jun-95       Original version.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf0.pro)


CDF0.PRO[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       cdf0.pro

 PURPOSE:
       `cdf0.pro' is used to create a set of structure variables containing
       the constants used by the CDF library.  The structures created and
       their contents are as follows...

               CDFconst     - General CDF constants.
               CDFdataType  - Data type codes.
               CDFencoding  - Encoding codes.
               CDFdecoding  - Decoding codes.
               CDFiCode     - Informational status codes.
               CDFwCode     - Warning status codes.
               CDFeCode     - Error status codes.
               CDFiiFnc     - Internal Interface functions.
               CDFiiItem    - General Internal Interface items.
               CDFiiItemA   - Internal Interface attribute items.
               CDFiiItemE   - Internal Interface entry items.
               CDFiiItemR   - Internal Interface rVariable items.
               CDFiiItemZ   - Internal Interface zVariable items.

       These structures contain the same values defined using the `cdf.pro',
       `cdf1.pro', and `cdf2.pro' batch files.  To see the contents of each
       structure, use the command...

               IDL> help, /structure, <structure-name>

       The use of these structures eliminates the problem of too many local
       variables caused by the use of `cdf.pro', `cdf1.pro', and `cdf2.pro'.

       This include file is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

       If the lengths of these structure names are longer than desired,
       consider using `cdf0x.pro' instead.

 CALLING SEQUENCE:
       IDL> @cdf0.pro

 EXAMPLE:
       IDL> @cdf0.pro
       IDL> status = CDFlib (CDFiiFnc.OPEN_, CDFiiItem.CDF_, 'rain2x', id, $
       IDL>                  CDFiiFnc.NULL_)
       IDL> if (status lt CDFconst.CDF_WARN) print, 'CDF not opened...'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       26-Jun-95       Original version.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/include/cdf0.pro)


CDF0X.PRO[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       cdf0x.pro

 PURPOSE:
       `cdf0x.pro' is used to create a set of structure variables containing
       the constants used by the CDF library.  The structures created and
       their contents are as follows...

               CDFx     - General CDF constants.
               CDFdt    - Data type codes.
               CDFen    - Encoding codes.
               CDFde    - Decoding codes.
               CDFic    - Informational status codes.
               CDFwc    - Warning status codes.
               CDFec    - Error status codes.
               CDFiif   - Internal Interface functions.
               CDFiix   - General Internal Interface items.
               CDFiia   - Internal Interface attribute items.
               CDFiie   - Internal Interface entry items.
               CDFiir   - Internal Interface rVariable items.
               CDFiiz   - Internal Interface zVariable items.

       These structures contain the same values defined using the `cdf.pro',
       `cdf1.pro', and `cdf2.pro' batch files.  To see the contents of each
       structure, use the command...

               IDL> help, /structure, <structure-name>

       The use of these structures eliminates the problem of too many local
       variables caused by the use of `cdf.pro', `cdf1.pro', and `cdf2.pro'.

       This include file is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       IDL> @cdf0x.pro

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFlib (CDFiif.OPEN_, CDFiii.CDF_, 'rain2x', id, $
       IDL>                  CDFiif.NULL_)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDF not opened...'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       21-Aug-96        Original version.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdf0x.pro)


CDF0X.PRO[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       cdf0x.pro

 PURPOSE:
       `cdf0x.pro' is used to create a set of structure variables containing
       the constants used by the CDF library.  The structures created and
       their contents are as follows...

               CDFx     - General CDF constants.
               CDFdt    - Data type codes.
               CDFen    - Encoding codes.
               CDFde    - Decoding codes.
               CDFic    - Informational status codes.
               CDFwc    - Warning status codes.
               CDFec    - Error status codes.
               CDFiif   - Internal Interface functions.
               CDFiix   - General Internal Interface items.
               CDFiia   - Internal Interface attribute items.
               CDFiie   - Internal Interface entry items.
               CDFiir   - Internal Interface rVariable items.
               CDFiiz   - Internal Interface zVariable items.

       These structures contain the same values defined using the `cdf.pro',
       `cdf1.pro', and `cdf2.pro' batch files.  To see the contents of each
       structure, use the command...

               IDL> help, /structure, <structure-name>

       The use of these structures eliminates the problem of too many local
       variables caused by the use of `cdf.pro', `cdf1.pro', and `cdf2.pro'.

       This include file is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       IDL> @cdf0x.pro

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFlib (CDFiif.OPEN_, CDFiii.CDF_, 'rain2x', id, $
       IDL>                  CDFiif.NULL_)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDF not opened...'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       21-Aug-96        Original version.

(See cdf/cdf_ssl/cdf_nssdc/include/cdf0x.pro)


CDF1.PRO[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       cdf1.pro

 PURPOSE:
       `cdf1.pro' is used to create a set of local variables containing the
       status codes used by the CDF library.  The general CDF constants are
       defined by `cdf.pro' and the CDF Internal Interface constants are
       defined by `cdf2.pro'.

       This include file is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       IDL> @cdf1.pro

 RESTRICTIONS:
       The use of `cdf1.pro' may result in too many local variables being
       created.  If that occurs, consider using `cdf0x.pro' instead.

 REVISION HISTORY:
       26-Jun-95        Original version.
       21-Aug-96        CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdf1.pro)


CDF1.PRO[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       cdf1.pro

 PURPOSE:
       `cdf1.pro' is used to create a set of local variables containing the
       status codes used by the CDF library.  The general CDF constants are
       defined by `cdf.pro' and the CDF Internal Interface constants are
       defined by `cdf2.pro'.

       This include file is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       IDL> @cdf1.pro

 RESTRICTIONS:
       The use of `cdf1.pro' may result in too many local variables being
       created.  If that occurs, consider using `cdf0x.pro' instead.

 REVISION HISTORY:
       26-Jun-95        Original version.
       21-Aug-96        CDF V2.6.

(See cdf/cdf_ssl/cdf1.pro)


CDF1.PRO[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       cdf1.pro

 PURPOSE:
       `cdf1.pro' is used to create a set of local variables containing the
       status codes used by the CDF library.  The general CDF constants are
       defined by `cdf.pro' and the CDF Internal Interface constants are
       defined by `cdf2.pro'.

       This include file is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       IDL> @cdf1.pro

 RESTRICTIONS:
       The use of `cdf1.pro' may result in too many local variables being
       created.  If that occurs, consider using `cdf0x.pro' instead.

 REVISION HISTORY:
       26-Jun-95        Original version.
       21-Aug-96        CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/include/cdf1.pro)


CDF2.PRO[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       cdf2.pro

 PURPOSE:
       `cdf2.pro' is used to create a set of local variables containing the
       Internal Interface constants used by the CDF library.  The general CDF
       constants are defined by `cdf.pro' and the CDF status codes are defined
       by `cdf1.pro'.

       This include file is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       IDL> @cdf2.pro

 RESTRICTIONS:
       The use of `cdf2.pro' may result in too many local variables being
       created.  If that occurs, consider using `cdf0x.pro' instead.

 REVISION HISTORY:
       26-Jun-95        Original version.
       21-Aug-96        CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdf2.pro)


CDF2.PRO[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       cdf2.pro

 PURPOSE:
       `cdf2.pro' is used to create a set of local variables containing the
       Internal Interface constants used by the CDF library.  The general CDF
       constants are defined by `cdf.pro' and the CDF status codes are defined
       by `cdf1.pro'.

       This include file is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       IDL> @cdf2.pro

 RESTRICTIONS:
       The use of `cdf2.pro' may result in too many local variables being
       created.  If that occurs, consider using `cdf0x.pro' instead.

 REVISION HISTORY:
       26-Jun-95        Original version.
       21-Aug-96        CDF V2.6.

(See cdf/cdf_ssl/cdf2.pro)


CDF2.PRO[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       cdf2.pro

 PURPOSE:
       `cdf2.pro' is used to create a set of local variables containing the
       Internal Interface constants used by the CDF library.  The general CDF
       constants are defined by `cdf.pro' and the CDF status codes are defined
       by `cdf1.pro'.

       This include file is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       IDL> @cdf2.pro

 RESTRICTIONS:
       The use of `cdf2.pro' may result in too many local variables being
       created.  If that occurs, consider using `cdf0x.pro' instead.

 REVISION HISTORY:
       26-Jun-95        Original version.
       21-Aug-96        CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/include/cdf2.pro)


CDFATTRCREATE[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrCreate

 PURPOSE:
       `CDFattrCreate' is used to create a new attribute in a CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrCreate (id, attrName, attrScope, attrNum)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrName:       STRING.  The new attribute's name.
       attrScope:      LONG.  The attribute scope.  Use one of the attribute
                       scopes defined by `cdf0x.pro'.

       All input variables must have been created/initialized before calling
       `CDFattrCreate'.

 OUTPUTS:
       attrNum:        LONG.  The number of the new attribute.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrCreate'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrCreate (id, 'TITLE', CDFx.GLOBAL_SCOPE, attrNum)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrCreate failed.'

 RESTRICTIONS:
       The attribute name must not already be in use in the CDF.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdfattrcreate.pro)


CDFATTRCREATE[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrCreate

 PURPOSE:
       `CDFattrCreate' is used to create a new attribute in a CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrCreate (id, attrName, attrScope, attrNum)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrName:       STRING.  The new attribute's name.
       attrScope:      LONG.  The attribute scope.  Use one of the attribute
                       scopes defined by `cdf0x.pro'.

       All input variables must have been created/initialized before calling
       `CDFattrCreate'.

 OUTPUTS:
       attrNum:        LONG.  The number of the new attribute.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrCreate'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrCreate (id, 'TITLE', CDFx.GLOBAL_SCOPE, attrNum)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrCreate failed.'

 RESTRICTIONS:
       The attribute name must not already be in use in the CDF.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdfattrcreate.pro)


CDFATTRCREATE[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrCreate

 PURPOSE:
       `CDFattrCreate' is used to create a new attribute in a CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrCreate (id, attrName, attrScope, attrNum)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrName:       STRING.  The new attribute's name.
       attrScope:      LONG.  The attribute scope.  Use one of the attribute
                       scopes defined by `cdf0x.pro'.

       All input variables must have been created/initialized before calling
       `CDFattrCreate'.

 OUTPUTS:
       attrNum:        LONG.  The number of the new attribute.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrCreate'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrCreate (id, 'TITLE', CDFx.GLOBAL_SCOPE, attrNum)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrCreate failed.'

 RESTRICTIONS:
       The attribute name must not already be in use in the CDF.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/bin/cdfattrcreate.pro)


CDFATTRENTRYINQUIRE[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrEntryInquire

 PURPOSE:
       `CDFattrEntryInquire' is used to inquire about an attribute entry.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrEntryInquire (id, attrNum, entryNum, dataType, $
                                     numElems)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute.
       entryNum:       LONG.  The number of the entry.

       All input variables must have been created/initialized before calling
       `CDFattrEntryInquire'.

 OUTPUTS:
       dataType:       LONG.  The entry's data type.  This will be one of
                       the data types defined in `cdf.pro'.
       numElems:       LONG.  The number of elements of the data type.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrEntryInquire'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrEntryInquire (id, CDFattrNum(id,'TITLE'), 0L,
       IDL>                               dataType, numElems)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrEntryInquire failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdfattrentryinquire.pro)


CDFATTRENTRYINQUIRE[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrEntryInquire

 PURPOSE:
       `CDFattrEntryInquire' is used to inquire about an attribute entry.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrEntryInquire (id, attrNum, entryNum, dataType, $
                                     numElems)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute.
       entryNum:       LONG.  The number of the entry.

       All input variables must have been created/initialized before calling
       `CDFattrEntryInquire'.

 OUTPUTS:
       dataType:       LONG.  The entry's data type.  This will be one of
                       the data types defined in `cdf.pro'.
       numElems:       LONG.  The number of elements of the data type.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrEntryInquire'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrEntryInquire (id, CDFattrNum(id,'TITLE'), 0L,
       IDL>                               dataType, numElems)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrEntryInquire failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdfattrentryinquire.pro)


CDFATTRENTRYINQUIRE[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrEntryInquire

 PURPOSE:
       `CDFattrEntryInquire' is used to inquire about an attribute entry.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrEntryInquire (id, attrNum, entryNum, dataType, $
                                     numElems)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute.
       entryNum:       LONG.  The number of the entry.

       All input variables must have been created/initialized before calling
       `CDFattrEntryInquire'.

 OUTPUTS:
       dataType:       LONG.  The entry's data type.  This will be one of
                       the data types defined in `cdf.pro'.
       numElems:       LONG.  The number of elements of the data type.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrEntryInquire'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrEntryInquire (id, CDFattrNum(id,'TITLE'), 0L,
       IDL>                               dataType, numElems)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrEntryInquire failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/bin/cdfattrentryinquire.pro)


CDFATTRGET[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrGet

 PURPOSE:
       `CDFattrGet' is used to read an entry value from an attribute.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrGet (id, attrNum, entryNum, value)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute
       entryNum:       LONG.  The number of the entry.

       All input variables must have been created/initialized before calling
       `CDFattrGet'.

 OUTPUTS:
       value:          DATA TYPE DEPENDENT.  The value which was read.  The
                       entry's CDF data type will determine which IDL data
                       type is used for this IDL variable.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf1.pro'.

       All output variables are (re)created/assigned by `CDFattrGet'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrGet (id, CDFattrNum('TITLE'), 0L, value)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrGet failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdfattrget.pro)


CDFATTRGET[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrGet

 PURPOSE:
       `CDFattrGet' is used to read an entry value from an attribute.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrGet (id, attrNum, entryNum, value)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute
       entryNum:       LONG.  The number of the entry.

       All input variables must have been created/initialized before calling
       `CDFattrGet'.

 OUTPUTS:
       value:          DATA TYPE DEPENDENT.  The value which was read.  The
                       entry's CDF data type will determine which IDL data
                       type is used for this IDL variable.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf1.pro'.

       All output variables are (re)created/assigned by `CDFattrGet'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrGet (id, CDFattrNum('TITLE'), 0L, value)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrGet failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/bin/cdfattrget.pro)


CDFATTRGET[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrGet

 PURPOSE:
       `CDFattrGet' is used to read an entry value from an attribute.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrGet (id, attrNum, entryNum, value)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute
       entryNum:       LONG.  The number of the entry.

       All input variables must have been created/initialized before calling
       `CDFattrGet'.

 OUTPUTS:
       value:          DATA TYPE DEPENDENT.  The value which was read.  The
                       entry's CDF data type will determine which IDL data
                       type is used for this IDL variable.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf1.pro'.

       All output variables are (re)created/assigned by `CDFattrGet'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrGet (id, CDFattrNum('TITLE'), 0L, value)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrGet failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdfattrget.pro)


CDFATTRINQUIRE[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrInquire

 PURPOSE:
       `CDFattrInquire' is used to inquire about an attribute in a CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrInquire (id, attrNum, attrName, attrScope, maxEntry)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute.

       All input variables must have been created/initialized before calling
       `CDFattrInquire'.

 OUTPUTS:
       attrName:       STRING.  The attribute name.
       attrScope:      LONG.  The attribute's scope.  This will be one of
                       attribute scopes defined by `cdf0x.pro'.
       maxEntry:       LONG.  The maximum entry number written for this
                       attribute.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrInquire'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrInquire (id, CDFattrNum(id,'TITLE'), attrName, $
       IDL>                          attrScope, maxEntry)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrInquire failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdfattrinquire.pro)


CDFATTRINQUIRE[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrInquire

 PURPOSE:
       `CDFattrInquire' is used to inquire about an attribute in a CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrInquire (id, attrNum, attrName, attrScope, maxEntry)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute.

       All input variables must have been created/initialized before calling
       `CDFattrInquire'.

 OUTPUTS:
       attrName:       STRING.  The attribute name.
       attrScope:      LONG.  The attribute's scope.  This will be one of
                       attribute scopes defined by `cdf0x.pro'.
       maxEntry:       LONG.  The maximum entry number written for this
                       attribute.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrInquire'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrInquire (id, CDFattrNum(id,'TITLE'), attrName, $
       IDL>                          attrScope, maxEntry)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrInquire failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/bin/cdfattrinquire.pro)


CDFATTRINQUIRE[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrInquire

 PURPOSE:
       `CDFattrInquire' is used to inquire about an attribute in a CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrInquire (id, attrNum, attrName, attrScope, maxEntry)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute.

       All input variables must have been created/initialized before calling
       `CDFattrInquire'.

 OUTPUTS:
       attrName:       STRING.  The attribute name.
       attrScope:      LONG.  The attribute's scope.  This will be one of
                       attribute scopes defined by `cdf0x.pro'.
       maxEntry:       LONG.  The maximum entry number written for this
                       attribute.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrInquire'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrInquire (id, CDFattrNum(id,'TITLE'), attrName, $
       IDL>                          attrScope, maxEntry)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrInquire failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdfattrinquire.pro)


CDFATTRNUM[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrNum

 PURPOSE:
       `CDFattrNum' is used to determine the number of an existing attribute.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       attrNum = CDFattrNum (id, attrName)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrName:       STRING.  The attribute name.

       All input variables must have been created/initialized before calling
       `CDFattrNum'.

 OUTPUTS:
       attrNum:        LONG.  The number of the attribute.  If an error
                       occurred, this will be a completion status code
                       (less than zero).  The possible status codes are
                       defined by 'cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrNum'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> attrNum = CDFattrNum (id, 'TITLE')
       IDL> if (attrNum lt 0L) print, 'CDFattrNum failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdfattrnum.pro)


CDFATTRNUM[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrNum

 PURPOSE:
       `CDFattrNum' is used to determine the number of an existing attribute.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       attrNum = CDFattrNum (id, attrName)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrName:       STRING.  The attribute name.

       All input variables must have been created/initialized before calling
       `CDFattrNum'.

 OUTPUTS:
       attrNum:        LONG.  The number of the attribute.  If an error
                       occurred, this will be a completion status code
                       (less than zero).  The possible status codes are
                       defined by 'cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrNum'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> attrNum = CDFattrNum (id, 'TITLE')
       IDL> if (attrNum lt 0L) print, 'CDFattrNum failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/bin/cdfattrnum.pro)


CDFATTRNUM[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrNum

 PURPOSE:
       `CDFattrNum' is used to determine the number of an existing attribute.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       attrNum = CDFattrNum (id, attrName)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrName:       STRING.  The attribute name.

       All input variables must have been created/initialized before calling
       `CDFattrNum'.

 OUTPUTS:
       attrNum:        LONG.  The number of the attribute.  If an error
                       occurred, this will be a completion status code
                       (less than zero).  The possible status codes are
                       defined by 'cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrNum'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> attrNum = CDFattrNum (id, 'TITLE')
       IDL> if (attrNum lt 0L) print, 'CDFattrNum failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdfattrnum.pro)


CDFATTRPUT[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrPut

 PURPOSE:
       `CDFattrPut' is used to write an entry value to an attribute.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrPut (id, attrNum, entryNum, dataType, numElems, value)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute
       entryNum:       LONG.  The number of the entry.
       dataType:       LONG.  The entry's data type.  Use one of the data
                       types defined by `cdf0x.pro'.
       numElems:       LONG.  The number of elements of the data type.
       value:          DATA TYPE DEPENDENT.  The value to be written.  The
                       IDL data type of this IDL variable should correspond
                       to the CDF data type of the entry.

       All input variables must have been created/initialized before calling
       `CDFattrPut'.

 OUTPUTS:
       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined bu
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrPut'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> value = 'This is an example entry for the TITLE attribute. '
       IDL> status = CDFattrPut (id, CDFattrNum(id,'TITLE'), 0L, $
                                 CDFdt.CDF_CHAR, 50L, value)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrPut failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdfattrput.pro)


CDFATTRPUT[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrPut

 PURPOSE:
       `CDFattrPut' is used to write an entry value to an attribute.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrPut (id, attrNum, entryNum, dataType, numElems, value)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute
       entryNum:       LONG.  The number of the entry.
       dataType:       LONG.  The entry's data type.  Use one of the data
                       types defined by `cdf0x.pro'.
       numElems:       LONG.  The number of elements of the data type.
       value:          DATA TYPE DEPENDENT.  The value to be written.  The
                       IDL data type of this IDL variable should correspond
                       to the CDF data type of the entry.

       All input variables must have been created/initialized before calling
       `CDFattrPut'.

 OUTPUTS:
       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined bu
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrPut'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> value = 'This is an example entry for the TITLE attribute. '
       IDL> status = CDFattrPut (id, CDFattrNum(id,'TITLE'), 0L, $
                                 CDFdt.CDF_CHAR, 50L, value)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrPut failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/bin/cdfattrput.pro)


CDFATTRPUT[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrPut

 PURPOSE:
       `CDFattrPut' is used to write an entry value to an attribute.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrPut (id, attrNum, entryNum, dataType, numElems, value)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute
       entryNum:       LONG.  The number of the entry.
       dataType:       LONG.  The entry's data type.  Use one of the data
                       types defined by `cdf0x.pro'.
       numElems:       LONG.  The number of elements of the data type.
       value:          DATA TYPE DEPENDENT.  The value to be written.  The
                       IDL data type of this IDL variable should correspond
                       to the CDF data type of the entry.

       All input variables must have been created/initialized before calling
       `CDFattrPut'.

 OUTPUTS:
       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined bu
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrPut'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> value = 'This is an example entry for the TITLE attribute. '
       IDL> status = CDFattrPut (id, CDFattrNum(id,'TITLE'), 0L, $
                                 CDFdt.CDF_CHAR, 50L, value)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrPut failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdfattrput.pro)


CDFATTRRENAME[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrRename

 PURPOSE:
       `CDFattrRename' is used to rename an existing attribute.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrRename (id, attrNum, attrName)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute.
       attrName:       STRING.  The new attribute name.

       All input variables must have been created/initialized before calling
       `CDFattrRename'.

 OUTPUTS:
       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined bu
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrRename'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrRename (id, CDFattrNum(id,'vMin'), 'VALIDMIN')
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrRename failed.'

 RESTRICTIONS:
       The new attribute name must not already be in use in the CDF.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdfattrrename.pro)


CDFATTRRENAME[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrRename

 PURPOSE:
       `CDFattrRename' is used to rename an existing attribute.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrRename (id, attrNum, attrName)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute.
       attrName:       STRING.  The new attribute name.

       All input variables must have been created/initialized before calling
       `CDFattrRename'.

 OUTPUTS:
       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined bu
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrRename'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrRename (id, CDFattrNum(id,'vMin'), 'VALIDMIN')
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrRename failed.'

 RESTRICTIONS:
       The new attribute name must not already be in use in the CDF.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdfattrrename.pro)


CDFATTRRENAME[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFattrRename

 PURPOSE:
       `CDFattrRename' is used to rename an existing attribute.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFattrRename (id, attrNum, attrName)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.
       attrNum:        LONG.  The number of the attribute.
       attrName:       STRING.  The new attribute name.

       All input variables must have been created/initialized before calling
       `CDFattrRename'.

 OUTPUTS:
       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined bu
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFattrRename'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFattrRename (id, CDFattrNum(id,'vMin'), 'VALIDMIN')
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFattrRename failed.'

 RESTRICTIONS:
       The new attribute name must not already be in use in the CDF.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/bin/cdfattrrename.pro)


CDFCLOSE[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFclose

 PURPOSE:
       `CDFclose' is used to close a CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFclose (id)

 INPUTS:
       id:             LONG.  Identifier of the CDF being closed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.

       All input variables must have been created/initialized before calling
       `CDFclose'.

 OUTPUTS:
       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFclose'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFclose (id)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFclose failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdfclose.pro)


CDFCLOSE[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFclose

 PURPOSE:
       `CDFclose' is used to close a CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFclose (id)

 INPUTS:
       id:             LONG.  Identifier of the CDF being closed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.

       All input variables must have been created/initialized before calling
       `CDFclose'.

 OUTPUTS:
       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFclose'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFclose (id)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFclose failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdfclose.pro)


CDFCLOSE[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFclose

 PURPOSE:
       `CDFclose' is used to close a CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFclose (id)

 INPUTS:
       id:             LONG.  Identifier of the CDF being closed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.

       All input variables must have been created/initialized before calling
       `CDFclose'.

 OUTPUTS:
       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFclose'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFclose (id)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFclose failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/bin/cdfclose.pro)


CDFCREATE[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFcreate

 PURPOSE:
       `CDFcreate' is used to create a new CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFcreate (CDFname, numDims, dimSizes, encoding, majority, id)

 INPUTS:
       CDFname:        STRING.  The pathname of the CDF to create.  The
                       `.cdf' extension should not be specified.
       numDims:        LONG.  The number of rVariable dimensions.
       dimSizes:       LONG array.  The rVariable dimension sizes.
       encoding:       LONG.  The variable/attribute entry encoding.  Use
                       one of the encodings defined by `cdf0x.pro'.
       majority:       LONG.  The variable majority.  Use one of the
                       majorities defined by `cdf0x.pro'.

       All input variables must have been created/initialized before calling
       `CDFcreate'.

 OUTPUTS:
       id:             LONG.  A unique identifier for the created CDF.  This
                       identifier must be used in all subsequent calls when
                       referring to this CDF.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFcreate'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> dimSizes = lonarr(2)
       IDL> dimSizes(0) = 180
       IDL> dimSizes(1) = 360
       IDL> status = CDFcreate ('rain2x', 2L, dimSizes, $
                                CDFen.NETWORK_ENCODING, CDFx.ROW_MAJORITY, id)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFcreate failed.'

 RESTRICTIONS:
       The CDF must not already exist (an existing CDF with the same name
       will not be overwritten).

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdfcreate.pro)


CDFCREATE[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFcreate

 PURPOSE:
       `CDFcreate' is used to create a new CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFcreate (CDFname, numDims, dimSizes, encoding, majority, id)

 INPUTS:
       CDFname:        STRING.  The pathname of the CDF to create.  The
                       `.cdf' extension should not be specified.
       numDims:        LONG.  The number of rVariable dimensions.
       dimSizes:       LONG array.  The rVariable dimension sizes.
       encoding:       LONG.  The variable/attribute entry encoding.  Use
                       one of the encodings defined by `cdf0x.pro'.
       majority:       LONG.  The variable majority.  Use one of the
                       majorities defined by `cdf0x.pro'.

       All input variables must have been created/initialized before calling
       `CDFcreate'.

 OUTPUTS:
       id:             LONG.  A unique identifier for the created CDF.  This
                       identifier must be used in all subsequent calls when
                       referring to this CDF.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFcreate'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> dimSizes = lonarr(2)
       IDL> dimSizes(0) = 180
       IDL> dimSizes(1) = 360
       IDL> status = CDFcreate ('rain2x', 2L, dimSizes, $
                                CDFen.NETWORK_ENCODING, CDFx.ROW_MAJORITY, id)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFcreate failed.'

 RESTRICTIONS:
       The CDF must not already exist (an existing CDF with the same name
       will not be overwritten).

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdfcreate.pro)


CDFCREATE[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFcreate

 PURPOSE:
       `CDFcreate' is used to create a new CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFcreate (CDFname, numDims, dimSizes, encoding, majority, id)

 INPUTS:
       CDFname:        STRING.  The pathname of the CDF to create.  The
                       `.cdf' extension should not be specified.
       numDims:        LONG.  The number of rVariable dimensions.
       dimSizes:       LONG array.  The rVariable dimension sizes.
       encoding:       LONG.  The variable/attribute entry encoding.  Use
                       one of the encodings defined by `cdf0x.pro'.
       majority:       LONG.  The variable majority.  Use one of the
                       majorities defined by `cdf0x.pro'.

       All input variables must have been created/initialized before calling
       `CDFcreate'.

 OUTPUTS:
       id:             LONG.  A unique identifier for the created CDF.  This
                       identifier must be used in all subsequent calls when
                       referring to this CDF.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFcreate'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> dimSizes = lonarr(2)
       IDL> dimSizes(0) = 180
       IDL> dimSizes(1) = 360
       IDL> status = CDFcreate ('rain2x', 2L, dimSizes, $
                                CDFen.NETWORK_ENCODING, CDFx.ROW_MAJORITY, id)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFcreate failed.'

 RESTRICTIONS:
       The CDF must not already exist (an existing CDF with the same name
       will not be overwritten).

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/bin/cdfcreate.pro)


CDFDELETE[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFdelete

 PURPOSE:
       `CDFdelete' is used to delete an open CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFdelete (id)

 INPUTS:
       id:             LONG.  Identifier of the CDF being deleted.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.

       All input variables must have been created/initialized before calling
       `CDFdelete'.

 OUTPUTS:
       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFdelete'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFopen ('rain3', id)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFopen failed.'
       IDL> status = CDFdelete (id)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFdelete failed.'

 RESTRICTIONS:
       You must be able to open a CDF in order to delete it with `CDFdelete'.
       Corrupted CDFs must be deleted at the operating system command line.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdfdelete.pro)


CDFDELETE[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFdelete

 PURPOSE:
       `CDFdelete' is used to delete an open CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFdelete (id)

 INPUTS:
       id:             LONG.  Identifier of the CDF being deleted.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.

       All input variables must have been created/initialized before calling
       `CDFdelete'.

 OUTPUTS:
       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFdelete'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFopen ('rain3', id)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFopen failed.'
       IDL> status = CDFdelete (id)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFdelete failed.'

 RESTRICTIONS:
       You must be able to open a CDF in order to delete it with `CDFdelete'.
       Corrupted CDFs must be deleted at the operating system command line.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdfdelete.pro)


CDFDELETE[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFdelete

 PURPOSE:
       `CDFdelete' is used to delete an open CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFdelete (id)

 INPUTS:
       id:             LONG.  Identifier of the CDF being deleted.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.

       All input variables must have been created/initialized before calling
       `CDFdelete'.

 OUTPUTS:
       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFdelete'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFopen ('rain3', id)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFopen failed.'
       IDL> status = CDFdelete (id)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFdelete failed.'

 RESTRICTIONS:
       You must be able to open a CDF in order to delete it with `CDFdelete'.
       Corrupted CDFs must be deleted at the operating system command line.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/bin/cdfdelete.pro)


CDFDOC[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFdoc

 PURPOSE:
       `CDFdoc' is used to inquire the copyright notice and version/release
       of the CDF library which created/modified a CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFdoc (id, version, release, copyright)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.

       All input variables must have been created/initialized before calling
       `CDFdoc'.

 OUTPUTS:
       version:        LONG.  The version number of the creating/modifying
                       CDF library.
       release:        LONG.  The release number of the creating/modifying
                       CDF library.
       copyright:      STRING.  The copyright notice of the creating/modifying
                       CDF library.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFdoc'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFdoc (id, version, release, copyright)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFdoc failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdfdoc.pro)


CDFDOC[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFdoc

 PURPOSE:
       `CDFdoc' is used to inquire the copyright notice and version/release
       of the CDF library which created/modified a CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFdoc (id, version, release, copyright)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.

       All input variables must have been created/initialized before calling
       `CDFdoc'.

 OUTPUTS:
       version:        LONG.  The version number of the creating/modifying
                       CDF library.
       release:        LONG.  The release number of the creating/modifying
                       CDF library.
       copyright:      STRING.  The copyright notice of the creating/modifying
                       CDF library.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFdoc'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFdoc (id, version, release, copyright)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFdoc failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdfdoc.pro)


CDFDOC[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFdoc

 PURPOSE:
       `CDFdoc' is used to inquire the copyright notice and version/release
       of the CDF library which created/modified a CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFdoc (id, version, release, copyright)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.

       All input variables must have been created/initialized before calling
       `CDFdoc'.

 OUTPUTS:
       version:        LONG.  The version number of the creating/modifying
                       CDF library.
       release:        LONG.  The release number of the creating/modifying
                       CDF library.
       copyright:      STRING.  The copyright notice of the creating/modifying
                       CDF library.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFdoc'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFdoc (id, version, release, copyright)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFdoc failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/bin/cdfdoc.pro)


CDFERROR[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFerror

 PURPOSE:
       `CDFerror' is used to retrieve a text string descibing a CDF status
       code.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFerror (iStatus, text)

 INPUTS:
       iStatus:        LONG.  CDF status code for which an explanation
                       string is desired.

       All input variables must have been created/initialized before calling
       `CDFerror'.

 OUTPUTS:
       text:           STRING.  The explanation string.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFerror'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> iStatus = CDFopen ('rain2', id)
       IDL> tStatus = CDFerror (iStatus, text)
       IDL> print, text

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdferror.pro)


CDFERROR[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFerror

 PURPOSE:
       `CDFerror' is used to retrieve a text string descibing a CDF status
       code.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFerror (iStatus, text)

 INPUTS:
       iStatus:        LONG.  CDF status code for which an explanation
                       string is desired.

       All input variables must have been created/initialized before calling
       `CDFerror'.

 OUTPUTS:
       text:           STRING.  The explanation string.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFerror'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> iStatus = CDFopen ('rain2', id)
       IDL> tStatus = CDFerror (iStatus, text)
       IDL> print, text

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/bin/cdferror.pro)


CDFERROR[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFerror

 PURPOSE:
       `CDFerror' is used to retrieve a text string descibing a CDF status
       code.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFerror (iStatus, text)

 INPUTS:
       iStatus:        LONG.  CDF status code for which an explanation
                       string is desired.

       All input variables must have been created/initialized before calling
       `CDFerror'.

 OUTPUTS:
       text:           STRING.  The explanation string.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFerror'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> iStatus = CDFopen ('rain2', id)
       IDL> tStatus = CDFerror (iStatus, text)
       IDL> print, text

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdferror.pro)


CDFINQUIRE[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFinquire

 PURPOSE:
       `CDFinquire' is used to inquire general information about an opened
       CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFinquire (id, numDims, dimSizes, encoding, majority, $
                            maxRec, numVars, numAttrs)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.

       All input variables must have been created/initialized before calling
       `CDFinquire'.

 OUTPUTS:
       numDims:        LONG.  The number of rVariable dimensions.
       dimSizes:       LONG array.  The rVariable dimension sizes.
       encoding:       LONG.  The variable/attribute entry encoding.  This
                       will be one of the encodings defined in `cdf.pro'.
       majority:       LONG.  The variable majority.  This will be one of
                       the majorities defined by `cdf0x.pro'.
       maxRec:         LONG.  The maximum record number written for the
                       rVariables.
       numVars:        LONG.  The number of rVariables.
       numAttrs:       LONG.  The number of attributes.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFinquire'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFinquire (id, numDims, dimSizes, encoding, majority, $
       IDL>                      maxRec, numVars, numAttrs)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFinquire failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/cdfinquire.pro)


CDFINQUIRE[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFinquire

 PURPOSE:
       `CDFinquire' is used to inquire general information about an opened
       CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFinquire (id, numDims, dimSizes, encoding, majority, $
                            maxRec, numVars, numAttrs)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.

       All input variables must have been created/initialized before calling
       `CDFinquire'.

 OUTPUTS:
       numDims:        LONG.  The number of rVariable dimensions.
       dimSizes:       LONG array.  The rVariable dimension sizes.
       encoding:       LONG.  The variable/attribute entry encoding.  This
                       will be one of the encodings defined in `cdf.pro'.
       majority:       LONG.  The variable majority.  This will be one of
                       the majorities defined by `cdf0x.pro'.
       maxRec:         LONG.  The maximum record number written for the
                       rVariables.
       numVars:        LONG.  The number of rVariables.
       numAttrs:       LONG.  The number of attributes.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFinquire'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFinquire (id, numDims, dimSizes, encoding, majority, $
       IDL>                      maxRec, numVars, numAttrs)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFinquire failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/bin/cdfinquire.pro)


CDFINQUIRE[2]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFinquire

 PURPOSE:
       `CDFinquire' is used to inquire general information about an opened
       CDF.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFinquire (id, numDims, dimSizes, encoding, majority, $
                            maxRec, numVars, numAttrs)

 INPUTS:
       id:             LONG.  Identifier of the CDF being accessed.  This
                       identifier must have been returned from a successful
                       call to `CDFcreate' or `CDFopen'.

       All input variables must have been created/initialized before calling
       `CDFinquire'.

 OUTPUTS:
       numDims:        LONG.  The number of rVariable dimensions.
       dimSizes:       LONG array.  The rVariable dimension sizes.
       encoding:       LONG.  The variable/attribute entry encoding.  This
                       will be one of the encodings defined in `cdf.pro'.
       majority:       LONG.  The variable majority.  This will be one of
                       the majorities defined by `cdf0x.pro'.
       maxRec:         LONG.  The maximum record number written for the
                       rVariables.
       numVars:        LONG.  The number of rVariables.
       numAttrs:       LONG.  The number of attributes.

       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFinquire'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFinquire (id, numDims, dimSizes, encoding, majority, $
       IDL>                      maxRec, numVars, numAttrs)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFinquire failed.'

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdfinquire.pro)


CDFLIB[1]

[Previous Routine] [Next Routine] [List of Routines]
 NAME:
       CDFlib

 PURPOSE:
       `CDFlib' is used to perform all supported CDF operations.  It uses
       a variable-length argument list to perform one or more operations.
       The CDF C Reference Manual provides a complete description of how
       to use `CDFlib'.

       This function is part of the CDF interface provided with the CDF
       distribution.  IDL also provides its own built-in interface to CDFs.

 CALLING SEQUENCE:
       status = CDFlib (op1, ...)

 INPUTS:
       op1:            LONG.  First operation to be performed.

       All input variables must have been created/initialized before calling
       `CDFlib'.

 OUTPUTS:
       status:         LONG.  A completion status code.  CDF_OK indicates
                       success.  The possible status codes are defined by
                       `cdf0x.pro'.

       All output variables are (re)created/assigned by `CDFlib'.

 EXAMPLE:
       IDL> @cdf0x.pro
       IDL> status = CDFlib (CDFiif.OPEN_, CDFiix.CDF_, 'rain2', id, $
       IDL>                  CDFiif.GET_, CDFiix.CDF_FORMAT_, format, $
       IDL>                  CDFiif.NULL_)
       IDL> if (status lt CDFx.CDF_WARN) print, 'CDFlib failed.'

       The values of `CDFiif.OPEN_', `CDFiix.CDF_', etc. are defined by
       `cdf0x.pro'.

 RESTRICTIONS:
       None.

 REVISION HISTORY:
       13-May-93       Original version.
        1-Nov-94       CDF V2.5.
       26-Jun-95       IDL 4.0.
       21-Aug-96       CDF V2.6.

(See cdf/cdf_ssl/cdf_nssdc/src/idl/c