Index of Functions: A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  X 
Index Page
dafcs

Table of contents
Procedure
Abstract
Required_Reading
Keywords
Declarations
Brief_I/O
Detailed_Input
Detailed_Output
Parameters
Exceptions
Files
Particulars
Examples
Restrictions
Literature_References
Author_and_Institution
Version

Procedure

     DAFCS ( DAF, continue search )

     ENTRY DAFCS ( HANDLE )

Abstract

     Select a DAF that already has a search in progress as the
     one to continue searching.

Required_Reading

     DAF

Keywords

     FILES

Declarations

    INTEGER               HANDLE

Brief_I/O

     VARIABLE  I/O  DESCRIPTION
     --------  ---  --------------------------------------------------
     HANDLE     I   Handle of DAF to continue searching.

Detailed_Input

     HANDLE   is the handle of a DAF in which either a forward
              or backward search has already been started by
              DAFBFS or DAFBBS. The DAF may be open for read
              or write access.

Detailed_Output

     None.

Parameters

     None.

Exceptions

     1)  If the input handle is invalid, an error is signaled by a
         routine in the call tree of this routine.

     2)  If this routine is called when no search is in progress in the
         the current DAF, the error SPICE(DAFNOSEARCH) is signaled.

Files

     None.

Particulars

     DAFCS supports simultaneous searching of multiple DAFs. In
     applications that use this capability, DAFCS should be called
     prior to each call to DAFFNA, DAFFPA, DAFGN, DAFGS, DAFRS, or
     DAFWS, to specify which DAF is to be acted upon.

Examples

     See $Examples in DAFFA.

Restrictions

     1)  Calls that do or may change DAF addresses of DAF summaries,
         names, or data of a given DAF file should not be made during
         a search of that file initiated by either DAFBFS or DAFBBS.
         No such changes should be made between the start of a search
         and calls to any entry point that reads or writes to the
         summary of the "current array" found by that search, or
         that returns a "found" flag indicating whether the current
         array exists.

         Changing the size of the comment area while a search is in
         progress can invalidate record numbers stored in local data
         structures of this routine. This can cause corrupted array
         summaries and names to be returned upon read access and file
         corruption to occur upon write access.

         Adding arrays (aka "segments") while either a forward or
         backward search is in progress can cause the search to miss
         the new segments.

Literature_References

     None.

Author_and_Institution

     N.J. Bachman       (JPL)
     J. Diaz del Rio    (ODC Space)
     B.V. Semenov       (JPL)
     W.L. Taber         (JPL)

Version

    SPICELIB Version 1.0.3, 26-OCT-2021 (JDR) (NJB)

        Edited the header to comply with NAIF standard.

        Updated $Restrictions section.

    SPICELIB Version 1.0.2, 10-FEB-2014 (BVS)

        Added full declaration of HANDLE to the $Declarations section
        of the header.

    SPICELIB Version 1.0.1, 10-MAR-1992 (WLT)

        Comment section for permuted index source lines was added
        following the header.

    SPICELIB Version 1.0.0, 04-SEP-1991 (NJB) (WLT)
Fri Dec 31 18:36:07 2021