File System Access

The VME does not contain application files. User data is located outside the VME, stored on the D3 Windows file system distributed across the network. Data is accessed through the Open Systems File Interface (OSFI), which provides transparent access to D3 applications, and allows sharing data with Visual Basic applications or other VME environments on the network.

The driver name in the dm,hosts, file is FSI.

Files located outside the VME are managed by the D3 File Manager. There are several advantages to locating files outside of the VME:

Note that accessing files from the network is slower than with files located inside the VME.

Once an account has been restored into the external file system, log to the external account by creating a Q-pointer in the MDS. For example, to create a Q-pointer to the external account accounting, create the following item in the MDS:

accounting

001 Q{S}

002 fsi:accounting

The QS.UPD utility creates all Q-pointers automatically.

To access databases or tables defined in another Network Domain, use Table Naming Conventions as described in the Administrators Guide.

Consider, for example, a large multidomain environment where there is a Personnel database in both the Manufacturing and the Sales domains. The domains fsi:[Manufacturing]Personnel and fsi:[Sales]Personnel allow accessing the two databases.

NOTE

Once an external file has been opened by a D3 process running in the VME, the file remains opened, even if the process drops back to TCL. External files are closed only when the user logs off.

These topics are presented:

Frame Size

Restoring Accounts

Saving Accounts

See Also

Virtual Machine Environment in Windows

Accessing the VME

Serial Terminals

Telnet Emulation

VME Tapes

VME Printers

Form Queue

Print File

VME Supported OSFI Drivers