User's Guide

FSTFMTLBL

Initialize tape label generation and call FSTFMTOUT

Function:

Initialize tape label generation and call FSTFMTOUT.

Parameters:

NAME
Requesters initials. The initials assigned to the user for the EROS tape archive.

CODE
Code for the requesters group. The code assigned to the user's group for the EROS tape archive. For example, Software Development is assigned code 091.

PROJECT
Project abbreviation. For example, LAS, AVHRR, etc. All spaces will be converted to underscores.

DESCRPT
Description of the tape set. Short description of the contents of the tape set.

NMONTHS(60)
Number of months to retain tape. The number of months from today's date that the tapes are to be removed from the tape archive. If allowed to default then the purge date will be set to sixty months from today's date. If a zero is entered, permanent storage is indicated.

IN
Input image. IN may be a single or multi-band image and may be of any data type. Window and/or band options may be specified.

COMMENT
Description of tape. A text string sent to the operator's terminal describing the tape to be mounted. If a new tape is being created the comment should indicate the type of tape to be used. For example, "please mount a 9-track scratch tape." If there is a specific tape that the images are to be placed on, then the comment should contain the tape library identification number and a short description of the tape. This will allow the operator to ensure that the correct tape is mounted.

INFILE(--)
Input file. The input ASCII file that can be appended to the end of the image data. Refer to USER NOTE 3.

TAPEDENS(&$TPDENS)
Tape density. The density of the tape in bits per inch. The default is defined by the TAE global $TPDENS and the list of valid densities are defined by the TAE global $TPVAL.

BLKSIZ(1)
Block size. The number of image lines to be written as a physical tape record.

AFTYPE(--)
Associated file type. The type of ancillary files associated with the image. This determines which associated files are read to retrieve information to fill the fast format header. If an associated file is not present or is in a different form than that listed, leave AFTYPE NULL and the associated file will not be used. Refer to USER NOTE 2.

= CCTX: The CCTX formatted associated files. = EDIPS: The EDIPS formatted associated files = FFMT: The Fast Format formatted associated files = TIPSP: The TIPSP formatted associated files.

Examples:

    See FSTFMTOUT.

Description/Algorithm:

Call INITLBL and then call FSTFMTOUT.

Fatal Error Message:

  1. [tapelbl-fatal] Fatal error encountered

    A fatal error was encountered. The message that is displayed preceding this message was the error that was encountered.

USERNOTES.

  1. Reference the EOSAT Fast Format document version B, October 1, 1991.
  2. For the CCTX associated files, a file with a name such as <xxxxx>.cctx_siat will be expected. This file is created by PLENTER. For EDIPS associated files, files with a name such as <xxxxx>.edips_<yyyy> were <yyyy> can be "headr", "trail", "ancil",or "annot" are expected. These files are created by EDIPSIN. For the FFMT associated file, a file with a name such as <xxxxx>.fhdr will be expected. This file is created by FSTFMTIN. For the TIPSP associated files, files with a name such as <xxxxx>.tipsp_<yyyy> where <yyyy> can be "head", "trail", or "annot" will be expected. These file are created by CCTTIPSP.

  3. Data for the input file can be created by running DSPASSOC. DSPASSOC will read the information in the associated files and can place the information in a file.