3 Eloquence Migration Tools
Syntax
ctd260 [options] device file
Options:
Examples:
Example One:
ctd260 -xv -ndbm* /dev/rdsk/c1001d0s2Extracts files from disk.
ctd260 -xv -ndbm* /dev/rct/c1002d0s2Extracts files from cartridge tape.
While one command sequence shows the device file name for a disk and the other a cartridge tape, both do the following:
B1368B CTD260 (C) COPYRIGHT HEWLETT-PACKARD GmbH 1991 (A.03.00) *** volume header *** System id code: 600 Volume Size : 16352 kbytes Directory size: 4080 entries User area : 16160 kbytes Volume label : NAME PR TYPE RECS RECL START ----- -- ---- ------ ------ -------- dbmap2 DATA 11 256 768 dbmap1 DATA 7 256 779 dbmap3 DATA 16 256 786 dbmap4 DATA 11 256 802 dbmap5 DATA 13 256 813Example Two:
ctd260 -xv -tFORM -tR260 /dev/rdsk/c1001d0s2
Files of type FORM and ROOT are extracted into the current directory.
As there are no file types under HP-UX, the file names have an extension which indicates the file type the file was on the HP 260:
NOTE: When transferring ROOT files the ctd260 program generate files with the extension .R260. These files denote an HP 260 root file.
The ctd260 utility can be used to extract files from archives created by the HP260 FVBACK utilitiy. The undocumented -f commandline flag is used to unpack HP260 FVBACK files.
To unpack an FVBACK archive, the following steps must be executed:
For example, if you have three FVBACK files named FVBFL.BKUP, FVBFL2.BKUP and FVBFL3.BKUP:
ctd260 -f -x FVBACK.BKUPThis will unpack all files, contained in the three backup files.
Note:
This feature is considered unsupported because some revisions of FVBACK are known to create inconsistent FVBACK files so ctd260 may not be able to unpack them.