The D3 file servers on a network can run Windows Server and Windows Client. A D3 file server must be started on every machine on the system that has at least one D3 file on its local or mapped disks.
A file server is uniquely identified inside a domain by its network name or an optional alias. This name, followed by a colon, is used as a prefix to the D3 MDS when referencing a table. For example, prod:ba,entity refers to a table located on the prod server.
The file server should be configured to support the required number of concurrent clients. For example, on a network with 100 clients, only 20 might make file accesses at any given time. It is important to evaluate the number of concurrent accesses at any given time.
If the client thread is a thread running inside the VME in Windows (see D3 User’s Guide), the thread-ID is replaced by the PIB number. Usually, a thread number is a large number (for example, 0xfffff00a0), which may appear negative in decimal, and a PIB number is always a small number from 0 to a few thousand. It is normally easy to tell the difference. For example, dev(12) is the PIB 12 running on the Virtual Machine Environment on the system dev.
See Also
D3 File System Interface Server Configuration