OLD-ACCOUNT-SAVE

Creates a tape with a format suitable for loading on a 5.3 or 6.0 Reality system. This is otherwise similar to the ACCOUNT-SAVE Proc.

Caution

You must always perform a VERIFY-SAVE as soon as possible after completing a save procedure. This verifies the integrity of the data saved to tape to ensure that it can be restored.

The Migration Utilities described in the optional manual User's Guide to Reality Migration Utilities should be used in preference to OLD-ACCOUNT-SAVE.

If you decide not to use the migration utilities, OLD-ACCOUNT-SAVE must be used instead of ACCOUNT-SAVE, where appropriate, to avoid file and/or item loss on restore. However, there are a number of potential problems on restoring to a pre-7.0 Reality system - see Restrictions

OLD-ACCOUNT-SAVE should not be used to transfer SYSMAN, SYSPROG or SYSFILES to a pre-7.0 Reality system. Use T-DUMP to transfer data instead.

Command Class

Proc.

Restrictions

SYSMAN and SYSPROG accounts only. If run from SYSPROG, accounts with update/retrieval lock codes are not saved.
Once accounts are restored they must be updated using UPDATE-ACCOUNT.
Item-ids to be restored must not be more than 50 characters long.
All data is saved to tape, but on restore, very large items are truncated to the maximum system size.
Any single level files must have a data pointer in the dictionary.
Binary items are not restored.
Passwords are irreversibly encrypted on Reality. If passwords are not removed before accounts are saved then, on restore, an encrypted form of password is expected at the 'PASSWORD:' prompt.
The account to be saved must have MD entries of type Q for MD, Proc, and M/DICT.
The save must be single reel.

Procedure

The procedure is very similar to the ACCOUNT-SAVE procedure.