clone [From=]inpath [To=]outpath [option]*
(+|-)Askme (-) (+|-)ME (+) (+|-)Overwrite (-) (+|-)PUrge (-) (+|-)PAsswords (+) (+|-)ReMovable (+) (+|-)ReLease (-) (+|-)Verbose (-) (+|-)errorStop (+) Device=name Levels=number
clone /frodo /bilbo +v clone F=userid/rmv /rmv -me -s clone T=/cat1/cat2 /cat1 clone T=/cat1 F=/cat1/cat2
Device=st1
or a device code as in
Device=.ds450
If you do not specify a Device= option, the cloned files and catalogs have the same device restrictions as the originals. If you specify
Device=
(with no value after the "="), the cloned files/catalogs will not have any of the device restrictions associated with the originals.
CLONE creates duplicates of files and catalogs. Permissions, both general and specific, are preserved, as are passwords, locks, ids-file attributes, FMS protection options, concurrency, mode, and user-specified information.
If you specify +ReLease or +PUrge, but there is some reason why a file or catalog cannot be released, CLONE preserves just enough of "inpath" to maintain a link to the item. For example, if you do not have enough permission to release a certain file four levels down in "inpath", the three catalogs leading to that file are also preserved.
When you specify +ReLease or +PUrge, the duplicate file/catalog is created, the contents are copied, and then the old version is released. For this reason, pressing BREAK does not destroy files. However, you cannot clone a file greater than your available file space within your own account, since there will be a space of time when both the original and the clone exist.
When a catalog is to be cloned, CLONE first builds up an image of the catalog's contents in memory. This means that a catalog can be cloned as a subcatalog of itself without causing infinite recursion.
CLONE copies the lowermost level of files/catalogs, then the next level up, and so on. This means that you will not have trouble cloning a catalog X to a new subcatalog of X. If, however, you try an operation like
clone from=a/b/c/d to=a/b l=10
you may run into trouble as CLONE tries to clone files that have just been created by the same clone operation.
If the original files/catalogs contain passwords, CLONE asks you to supply the passwords before they are cloned. Normally, the clones are given the same passwords; however, if you specify -PAsswords, the clones are created without passwords.
It is impossible to create time-lock passwords from TSS. If an original file/catalog has a time-lock password, the clone version is given a normal password, not a time-lock one.
It is impossible to create non-structured files from TSS. Therefore, if you try to clone a non-structured file, you receive an error.
Copyright © 1996, Thinkage Ltd.