Top  Previous  Next


The T.DUMP command saves data to a Pick style T-DUMP tape.





T.DUMP {DICT} filename {id...} {BINARY} {COUNT.SUP} {DET.SUP} {FROM listno}




filenameis the name of the file to be saved.


id...is a list of record ids to be saved.


BINARYsuppresses conversion of newlines to field marks in directory files. Use this mode when saving binary data.


COUNT.SUPsuppresses display of the count of records saved.


DET.SUPsuppresses display of the detailed list of records saved.


FROM listnouses the specified select list to identify the records to be saved.



The T.LOAD command processes the named file to produce a Pick style T-DUMP tape


The tape or pseudo-tape to be created must first be assigned to the process using the SET.DEVICE command.


By default, the entire content of the named file is saved. If the default select list is active or the FROM option is used to identify an active select list, that list is used to determine the records to be saved. Alternatively, a list of ids may be given on the command line.





T.DUMP operates within the security rules imposed by use of QM's encryption features. Files that use record level encryption cannot be saved if the user performing the save does not have access to the encryption key. The data saved for files that use field level encryption will have all fields for which the user is denied access set to null strings. All saved data is recorded in decrypted form and hence storage of T.DUMP media may reduce system security. The media format used by T.DUMP is an industry standard that does not provide a way to record details of data encryption. Restoring a save in which encrypted fields have been omitted is unlikely to yield a usable file. Backup of accounts that include encrypted data should be performed using operating system level tools.





The media format of T.DUMP also imposes a restriction that makes it impossible to save an item that contains a field mark (character 254) immediately followed by a text mark (character 251). In practical terms, this means that it is unlikely to be possible to use T.DUMP to save binary data such as compiled programs or dictionary items. For this reason, T.DUMP is not considered as suitable for routine system backups.



See also: