The following behaviors are unique to D3 Windows:
|Account restore|| When restoring an account from tape to an account that already exists in the FSI, specifying
the (o option in the restore overlays the data. Items on disk are replaced
by the corresponding tape items. Disk items with no counterpart on tape (for example, items
created after the backup) are not removed.
The FSI:DM account contains the FileOfFiles file that describes FSI files. Use the list-file-stats command to view this information.
|Disk usage||The FSI is designed for efficient use of NTFS and fast disk access. Each FSI file contains its own overflow space and indexes. Because of this, FSI files typically require more disk space than VME files.|
|D-Pointer caching||Whenever a change is made to a D-Pointer, you must log off, and then log back on to the line for that file.|
|FSI File Of Files||The File-of-Files file for the FSI is stored in the FSI:DM account. The File-of-Files file for the VME is stored in the DM account.|
|FSI:DM vs. VME:DM|| FlashBASIC programs opening the DM account will open the FSI:DM account. Conversely,
non-Flashed programs will open the VME:DM account.
It is good practice to avoid dealing with DM account files. Instead, use an explicit data OSFI name (for example, VME:DM or FSI:DM).
|Full file restores||Use the D3VME /restore option to restore the VME only. Use the /fileload option to restore both VME and FSI files.|
|Poorly sized files||The FSI is more sensitive to poorly sized files, thus increasing the chance of performance degradation when poorly sized files exist.|
|Third trailing comma in full path||The optional third comma (for example, "account,dict,data,") is ignored in D3 Windows. This comma changes the behavior for certain Q-Pointer resolution instances.|