User's Guide

ESAMETAIN

Acquire ESA metadata from a tar tape

Function:

Acquire ESA metadata from a tar tape.

Parameters:

TAPEID
Tape identifier. The identification label number of the tape to be mounted.

OUTDIR(--)
Output directory. The directory in which to place the ESA metadata files. If defaulted, the metadata will be placed in the "[esameta]" subdirectory below the ADAPSORB directory.

Examples:

  1. LAS> esametain tapeid=km1234 outdir=[dir1.dir2]

    A request is sent to the operators to locally mount an ESA metadata tape km1234. The ESA metadata is extracted from tape into the directory "[dir1.dir2]".

Description/Algorithm:

A tape containing ESA metadata is mounted on a tape drive. ESAMETAIN then goes into the directory specified by OUTDIR. The metadata is extracted from the tape using the UNIX "tar" utility. ESAMETAIN returns to its original working directory and the tape is dismounted. Messages are logged in the file "esametain.log" within the ADAPSLOG directory.

Nonfatal Error Messages:

    None

Fatal Error Messages:

  1. [esametain-fatal] Fatal error encountered

    A fatal error was encountered. The message displayed prior to this is the actual error encountered.

  2. [esametain-env] Error retrieving destination directory

    An error was encountered while attempting to determine the destination directory. Ensure that the environment variable ADAPSORB has been defined.

  3. [esametain-dir] Error changing directories

    An error changing directories was encountered. Ensure that the directory specified by OUTDIR exists with the proper permissions.

  4. [esametain-drv] Error allocating a tape device for <XXXXXX>

    An error occurred while allocating a tape drive. Retry executing the program.

  5. [esametain-tar] Error extracting tar information from <XXXXXX>

    An error occurred extracting the information from the tape. Ensure that the tape is a "tar" format tape.

  6. [esametain-rel] Error releasing tape drive for <XXXXXX>

    An error occurred releasing the tape drive. Examine the metadata extracted from the tape to ensure that it is complete.

User Notes:

  1. The ESA metadata is being supplied to EDC in order to determine which input scenes were used to create the ESA stitched orbits. This information is then used at EDC to update the production database, signifying which individually acquired scenes have been stitched into a half orbit. There should exist one (1) metadata file per half orbit generated, possibly more if the stitching routines were rerun. Each metadata file will contain the input scenes used to generate a half orbit. The file format follows:

        scene id      database source link (unused)
        --------------------------------------------
        ah11122693095142 |  00000
        ah11122693102158 |  00000
        ah11122693102554 |  00000
        ah11122693102942 |  00000
        ah11122693103806 |  00000