DBCOPY makes it possible to move a TSP databank from one type of computer to another, since the actual databank files are not compatible between different computers.
DBCOPY (DOC) <list of filenames> ;
Usage
Follow the word DBCOPY with the filenames of the TSP databanks to be moved. A file containing TSP commands and data is created for each databank. When this file is moved to another computer and run with TSP, the databank is created with all its original variables and values. The filename with the TSP commands will be the same as the databank name, except it will have filetype .TSP instead of .TLB . The .TSP file has record length of at most 80, so it can be easily moved to another computer. There are no restrictions on the sizes of the databanks, SMPLs and FREQs of the series, or types of the TSP variables (it handles CONST, PARAM, SERIES, MATRIX, FRML, and IDENT). The SMPLs and FREQs are determined by the series in the databank, not by the current SMPL or FREQ.
DOC/NODOC controls the listing of documentation (created with the DOC command). Specify NODOC if you will be using TSP version 4.1 or earlier.
Suppose that you have a databank called FOO.TLB which contains two time series X and Y, and a parameter B. The command
DBCOPY FOO;
would create the file FOO.TSP which would contain:
? Re-create TSP Databank
? FOO.TLB
END; OUT FOO;
PARAM B 3.14 ;
FREQ Q; SMPL 60:1,85:4;
LOAD X;
1 2 3 4 ... ;
LOAD Y;
11 22 33 44 ... ;