MBUBIT -- DIPIX Format Tape Bitmap Transfer

Reads a specified training area file from an R-stream Dipix BU tape, and creates a new bitmap segment on a PCIDSK database file.

PARAMETERS

MBUBIT is controlled by the following global parameters: 

Name     Prompt                                  Count     Type
BUFILE   DIPIX Filename                          1-13      Char
FILE     Database File Name                      1-64      Char
DBSN     Database Segment Name                   1-8       Char

BUFILE

Specifies the name of the BU file to be read. MBUBIT will read only one BU file per run. The filename should be of the form: 

 Character:       1 2 3  4 5  6 7 8 9  10 11 12 13
 Contents:        (A A A)(T A)(C C C C)(. T A F)
Characters 1 through 3 specify a Dipix area name. Characters 4 and 5 specify the type of file type (TA). Characters 6 through 9 specify a Dipix training area name. Characters 10 through 13 specify the file extension, which is normally .TAF for training area files. If the file extension is not specified, it defaults to .TAF.

FILE

Specifies the PCIDSK file to which to write the signature segment data. 

 EASI>FILE="file_specification"         | input file name

DBSN

Specifies a 1 to 8-character name that will be assigned to the output bitmap segment. 

 EASI>DBSN="project"

DETAILS

MBUBIT reads a training area file from a Dipix BU tape (BUFILE) and outputs it to a bitmap segment on a PCIDSK image database file (FILE). If the dimensions of the training area file are not the same as the PCIDSK file dimensions, a warning message is printed on the terminal, and only the window common to both training area file and PCIDSK file is transferred. NO automatic shrinking or zooming takes place when using MBUBIT. The desired training area file can be determined by running MBUREP program. All training area files have the extension ".TAF".

A 1 to 8-character segment descriptor (DBSN) must be assigned to the newly created bitmap segment. The Dipix BU file name is stored in the database segment history record.

MBUBIT only reads ONE training area file per run. So if you want to transfer `N' files from the tape to database, then you must run MBUBIT `N' times, setting up the appropriate parameters.

A description of the Dipix tape format is given in documentation for MBUREP program. 

 A TAPE MUST BE MOUNTED ON THE TAPE DRIVE BEFORE MBUBIT CAN BE
 RUN.  CLEANING THE TAPE HEADS IS RECOMMENDED TO MINIMIZE THE
 CHANCE OF TAPE READ ERRORS.

EXAMPLE

Transfer a training site file, called ATBTAMIXD.TAF, from tape to database: 

 EASI>BUFILE="ATBTAMIXD"
 EASI>FILE="ATBTAMIXD.PIX"
 EASI>DBSN="Lakes"
 EASI>RUN MBUBIT
About PCI Help Gateway