| ### GDS Client Programs This topic describes the programs that make up the client side of GDS. The DCE configuration script installs the GDS client software but does not configure it. To configure and activate a GDS client, run the gdssysadm program, then initialize the Directory User Agent (DUA) cache by running gdsditadm. For details on these programs and on setting up and activating GDS, see the OSF DCE GDS Administration Guide and Reference. The GDS control program (gdscp) is a utility that you can use for managing and maintaining the GDS software. For additional information on the gdscp program, see the OSF DCE GDS Administration Guide and Reference. If GDS is installed, the DCE client runs the DUA. The DUA, which is the client side of GDS, sends requests to the GDS server process, the DSA. The DUA consists of the following processes: · The gdscache process caches user data and stores data used for regulation purposes locally. · The gdscstub process handles all outgoing requests to remote DSAs. · The gdscacheadm program supports administration of the contents of the local DUA cache database. · The gdsipcchk program verifies the IPC-state information contained in the shared memory area of a GDS installation. · The gdssysadm program supports administration of the local GDS installation, such as configuring GDS, activating servers, and backing up the database. A machine running only the client side of GDS can access GDS servers on other machines, or one machine can run both the client and server portions of GDS. Machines running just the DUA are known as client systems. Client systems can access directory information on server machines without having to store that information. ###