FILE.SAVE

FILE.SAVE

Top  Previous  Next

 

The FILE.SAVE command creates a Pick style FILE-SAVE tape.

 

 

Format

 

FILE.SAVE {account.list} {options}

 

where

 

account.listis a list of the names of the accounts to be saved. If omitted and the default select list is active, this list is used to determine the accounts to be saved. Otherwise, all accounts referenced in the QMSYS ACCOUNTS file are saved.

 

optionsspecifies options processing features:
BINARYsuppresses translation of newlines to field marks when saving directory files. Use this option when saving binary data.
DET.SUPsuppresses display of the names of files saved.
EXCLUDE.REMOTEcauses remote files to be omitted as described below.
INCLUDE.REMOTEcauses remote files to be saved as described below.
NO.QUERYsuppresses the confirmation prompt when using a select list. The NO.SEL.LIST.QUERY mode of the OPTION command can be used to imply this option.

 

 

The FILE.SAVE command creates a Pick style "compatible mode" tape and saves one or more QM accounts to it.

 

Note carefully: Although it would be possible to use this command to create a backup of a QM account, it is recommended that operating system level tools are used for this purpose. The media format used by FILE.SAVE cannot save ECS mode files or information related to triggers, alternate key indices, replication or encryption (see below). For this reason, FILE.SAVE is not considered suitable for routine system backups. It is provided primarily as a way to return data to a Pick style system during migration of an application.

 

The media format also has no way to represent a distributed file. These will be omitted and a warning message will be displayed. The data elements of the distributed file will be saved in the usual way so no data should be lost, however, it will be necessary to recreate the distributed file itself if the data is restored.

 

The tape to be created must first be opened to the process using the SET.DEVICE command.

 

The command reports its progress by displaying the name of each file as it is saved unless the DET.SUP option is used.

 

 

FILE.SAVE normally saves all files referenced by F-type records in the VOC of the account being saved. There is a three level mechanism by which files can be excluded:

 

1.Field 5 of the F-type VOC entry can contain

DSave the dictionary but omit the data element
EExclude this file from an ACCOUNT.SAVE or FILE.SAVE
IInclude this file in an ACCOUNT.SAVE or FILE.SAVE

 

2.If field 5 of the VOC record does not specify any of the above flags, the EXCLUDE.REMOTE and INCLUDE.REMOTE options are used to determine whether remote files (those with a directory delimiter in their pathnames) are to be saved.

 

3.If neither of the above methods of file selection is used, the value of the EXCLREM configuration parameter is used to determine whether remote files are to be saved.

 

By use of a combination of the above methods, it should be possible to achieve total control of what is included in a save.

 

 

Encryption

 

FILE.SAVE operates within the security rules imposed by use of QM's encryption features. Files that use record level encryption will not 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 FILE.SAVE media may reduce system security. The media format used by FILE.SAVE 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.

 

 

See also:

ACCOUNT.RESTORE, ACCOUNT.SAVE, FIND.ACCOUNT, QMSAVE, RESTORE.ACCOUNTS, SEL.RESTORE, SET.DEVICE, T.ATT, T.DUMP, T.LOAD, T.xxx