A Fileset's FLDB Information

· The name of the fileset, with a .readonly or .backup extension, if appropriate.

· The fileset IDs of the read/write, read-only, and backup versions.

· A separate status flag for each of the three versions, indicating whether the version exists at some site. A status of valid indicates the version exists at some site; a status of invalid indicates the version does not exist at any site. Note that the status of the read-only version is valid once a replication site is defined, regardless of whether a replica yet exists at the site.

· The number of sites at which a version of the fileset exists.

· An indicator if the FLDB entry is locked. The indicator is omitted if the entry is not locked.

· The replication parameters that are associated with the fileset.

· Information identifying the File Server machines and aggregates (sites) where read/write (RW), read-only (RO), or backup (BK) versions of the fileset reside.

· For each read-only site, the MaxSiteAge replication parameter defined for that site. (See Creating Read-Only DCE LFS Filesets for more information about replication parameters.)

· The abbreviated DCE principal name of each File Server machine on which a version of the fileset resides, and the name of the group that owns the server entry for the machine in the FLDB or <nil> if no group owns the server entry.

· For each fileset with advisory RPC authentication bounds, the values for both sets of upper and lower bounds (one set for communications with the Cache Managers in the local cell and the other set for communications with Cache Managers in foreign cells.)

Because functionality such as replication is not supported for non-LFS filesets, FLDB entries for non-LFS filesets do not contain as much information as entries for DCE LFS filesets. However, information such as the ID number and site of each non-LFS fileset is recorded in the FLDB. The fts lsfldb and fts lsft commands display this information.