Document revision date: 5 July 2000

UAF_NOSUCHUSER, username !AS does not exist in the DCE$UAF

Explanation: The specified OpenVMS username does not exist, so the requested action could not be performed.
User Action: Specify a username that exists in the DCE$UAF. Use the SHOW command to see the entries, if necessary.

UAF_NOSUCHPRIN, principal "!AZ" does not exist in the DCE$UAF

Explanation: The specified DCE principal does not exist, so the requested action could not be performed.
User Action: Specify a principal that exists in the DCE$UAF. Use the SHOW command to see the entries, if necessary.

UAF_NOTADDED, error creating entry <USERNAME>

Explanation: The ADD command failed.
User Action: Take action based on the accompanying error message.

UAF_NOTDELETED, error deleting entry <USERNAME>

Explanation: The DELETE command failed.
User Action: Take action based on the accompanying error message.

UAF_NOTMODED, error modifying entry <USERNAME>

Explanation: The MODIFY command failed.
User Action: Take action based on the accompanying error message.

UAF_NOVERIFY, unable to verify account

Explanation: A VERIFY command could not be completed. The accompanying message explains the reason.
User Action: Take action based on the accompanying error message.

UAF_NOVREC, no version record found in file

Explanation: Each DCE$UAF.DAT file contains a special version record that is added when the file is created and read each time the file is opened. If no version record is found, then the file-control library will abort any attempt to read or write authorization data from or to the file. This message indicates a possible problem in the way that the file was created, or possible damage to the file after it was created.
User Action: Delete the current file and create a new one.

UAF_NYI, this feature is not yet implemented

Explanation: The specified command (or part of the command) is not implemented in this field test version of the software.
User Action: This feature will be implemented in an update to the field test software.

UAF_RECEXISTS, record already exists

Explanation: The ADD command cannot be performed because the specified username or principal already exists in the DCE$UAF file.
User Action: Check the username and principal name and reenter the command if incorrect.

UAF_SYSCHKBEG, starting scan of SYSUAF file

Explanation: The ANALYZE command is starting the scan of the SYSUAF file.
User Action: None.

UAF_SYSCHKEND, completed scan of SYSUAF file

Explanation: The ANALYZE command has completed the scan of the SYSUAF file.
User Action: None.

UAF_VERSIONSKEW, version skew between library and UAF file

Explanation: Each DCE$UAF.DAT file contains a special version record that is added when the file is created and read each time the file is opened. If the version information in the file record is not compatible with the internal version of the file-control library, then this message is returned, and any attempt to read or write authorization data from or to the file will be aborted. The message indicates an incompatibility between the DCE$UAF.DAT file and the file-control library. This can only happen as a result of the installation of newer software on a system with an existing DCE$UAF.DAT file.
User Action: Convert the older-format file to the format required by the new software.

UAF_VERUSERERR, error accessing registry

Explanation: An error occurred while attemping to access the DCE registry. The accompanying text explains the reason. (A connection to the DCE registry is made only for a VERIFY command.)
User Action: Take action based on the accompanying error message.

UAF_VRECFAIL, write of version record failed

Explanation: Each DCE$UAF.DAT file contains a special version record that is added when the file is created. This message indicates that the record could not be written to the file, in which case the newly created file is deleted. This message indicates a possible problem with the file system, the file device, or other low-level problem that is generally not within the user's power to correct.
User Action: If multiple attempts to create the file correctly fail, then further diagnostic work by the system administrator may be necessary to find the source of the problem.

This chapter contains reference information on the CDS subtree commands that are in the CDS control program (cdscp). The CDS subtree commands are equivalent to their counterparts in the DCE control program (dcecp). The dcecp subtree commands are documented in the Open Group documentation.

Deletes a subtree of directories and their contents or an individual directory and its contents.

Synopsis

cdscp delete subtree tree-name [norecurse] [exclude entry-type ]

Parameters

tree-name

The name of the uppermost directory in the subtree you intend to delete. You can use the optional norecurse keyword to restrict the deletion only to the directory (and contents) you specify in tree-name.

entry-type

One or more of the following types of entries to exclude from deletion: all objects, soft links, or specific directories. You can exclude multiple entry-types in a single command. Use any combination of the following entry-type specifiers, separating multiple arguments with commas. You must leave a blank character space after each comma and after each directory-name specification.

objects
links
directory directory-name

Description

The delete subtree command deletes a subtree of directories and their contents. You can use the optional norecurse keyword to restrict the deletion to only the directory you specify in tree-name. If that directory has child directories (and you use the optional norecurse keyword) the command deletes only the directory's contents.

You can use the optional exclude directory argument to specify one or more directories to exclude from deletion. Specify multiple directories in the following format:

exclude directory directory-name, directory directory-name, directory directory-name

Permissions Required

You must have delete permission to all affected directories and their contents. (Delete and administer permission to all affected directories is also sufficient.) You also need write permission to the clearinghouse that stores the master replica of the directory you specify in tree-name.

Example

The following command deletes the /.:/admin/site03 directory and its contents as well as all of its child directories and their contents.

cdscp> delete subtree /.:/admin/site03

See Also

delete_directory
dump_subtree
merge_file
merge_subtree

Dumps a subtree of directories and their contents into an interim file.

Synopsis

cdscp dump subtree tree-name [norecurse] [to, into] file filename [exclude entry-type ]

Parameters

tree-name

The name of the uppermost directory in the subtree you intend to dump to the interim file. You can use the optional norecurse keyword to restrict the dump only to the directory (and contents) you specify in tree-name.

filename

The name of the interim file to which the subtree is dumped.

entry-type

One or more of the following types of entries to exclude from the dump: all ACLs, object entries, soft links, or specific directories. You can exclude multiple entry types in a single command. Use any combination of the following entry-type specifiers, separating multiple arguments with commas. You must leave a blank character space after each comma and after each directory-name specification.

acls
objects
links
directory directory-name

Description

The dump subtree command dumps a subtree of directories and their contents into an interim file. You can use the optional norecurse keyword to dump only the directory (and contents) you specify in tree-name. You can use the optional [exclude] keyword to omit all ACLs, object entries, soft links, or specific directories from the interim file. Use the file extension .dat as a convention for interim filenames.

This command is useful for backing up individual directories or subtrees and can also be used as the first step of a directory merge operation. If you intend to merge a subtree into the namespace of a foreign cell (or a reconfigured cell), use the optional exclude keyword to exclude the ACLs from the interim file.

ACLs that reference the source cell name will have no meaning in the target cell and will convey no access.

Permissions Required

You must have read permission to all affected directories and their contents.

Example

The following command creates an interim file named /.:/admin/site03.dat that contains the /.:/admin/site03 directory, its contents, and all its subdirectories and their contents.

cdscp> dump subtree /.:/admin/site03 into file site03.dat

See Also

delete_subtree
merge_file
merge_subtree

Merges the contents of an interim file (created with the dump subtree command) into an existing subtree.

Synopsis

cdscp merge file ifile [to, into] subtree tree-name failures [to] file [=] filename

Parameters

ifile

The name of an interim file that contains a directory and its contents, or a subtree of directories and their contents.

tree-name

The name of the uppermost directory in the target subtree.

filename

The name of a failures file that contains names that could not be merged.

Description

The merge file command merges the contents of an interim file created with the dump subtree command into an existing subtree whose uppermost directory you specify in tree-name. If the target directory tree-name does not exist, you must use the create directory or recreate directory command to create the target directory before you proceed.

The existing values of the CDS_Convergence, CDS_InChName, and CDS_UpgradeTo attributes associated with the directory you specify in tree-name are overwritten with the corresponding attribute values associated with the directory that was specified as tree-name in the dump subtree command used to create the interim file.

If you did not exclude source subtree ACLs from the interim file, the ACLs of new entries created in the target subtree as a result of the merge will contain the original source subtree ACL entries as well as any ACL entries that may propagate from the new parent directory in the target subtree of the uppermost directory in the interim file. The principal who executes the merge file command is granted full permission to all new entries in the target subtree.

You use the failures to file = filename argument to specify the name of a file that will contain the names of any directories, object entries, or soft links (including their ACLs) that could not be merged. You can use this file if you perform subsequent merge file operations to merge failed names.

Permissions Required

You must have read and insert permission to the target directory (and contents) you specify in tree-name. You also need write permission to the clearinghouse that stores the master replica of the uppermost directory in the target subtree.

Example

The following command merges the interim file branch01.dat with the /.:/admin/site03 directory:

cdscp> merge file branch01.dat into subtree /.:/admin/site03 failures to file = branch01failed.dat

See Also

dump_subtree
merge_subtree

Dumps a directory or subtree and its contents into an interim file and then merges the contents of that file into an existing directory.

Synopsis

cdscp merge subtree old-tree-name [norecurse] [to, into] subtree new-tree-name [exclude entry-type ]

Parameters

old-tree-name

The name of the uppermost directory in the subtree whose directories and contents you intend to merge. If you use the optional norecurse keyword, you can restrict the dump and merge operation to the particular directory (and contents) you specify in old-tree-name.

new-tree-name

The name of the uppermost directory in the target subtree.

entry-type

One or more of the following types of entries to exclude from the dump and merge operation: ACLs, object entries, soft links, or specific directories. You can exclude multiple entries in a single command. Use any combination of the following entry-type specifiers, separating multiple arguments with commas. You must leave a blank character space after each comma and after each directory-name specification.

acls
objects
links
directory directory-name

Description

The merge subtree command combines the operations performed by the dump subtree and merge file commands into a single operation. This command dumps a subtree into an interim file and then merges the contents of the file into another existing subtree. If you use the optional norecurse keyword, the command dumps and merges only the directory you specify in old-tree-name. You can use the optional exclude keyword to omit all ACLs, object entries, soft links, and specific directories form the dump and merge operation. The target directory you specify in new-tree-name must already exist. If it does not, the command returns an error and you must use the create directory or recreate directory command to create the target directory before you proceed.

This command is especially useful when all clearinghouses are available for every directory in both subtrees, no duplicate names exist in source and target subtrees, and when the permissions required to create entries in the target subtree have already been granted. If a duplicate name is detected, or if any affected clearinghouse cannot be reached while the merge subtree command is in progress, the command completes what it can. No failures file is created.

Permissions Required

You must have read permission to all affected directories and contents in the source subtree (old-tree-name). You also need read and insert permission to the target directory (and contents) you specify in new-tree-name, and write permission to the clearinghouse that stores the master replica of the target directory.

Example

The following command merges the contents of a subtree beginning with the /.:/admin/site01 directory with the /.:/admin/site02 directory.

cdscp> merge subtree /.:/admin/site01 into subtree /.:/admin/site02

See Also

dump_subtree
merge_file

Recreates an existing directory (in a source subtree) as a new directory (in a target subtree).

Synopsis

cdscp recreate directory directory-name [as] directory newdirectory-name [exclude acls]

Parameters

directory-name

The full name of the directory you intend to recreate.

newdirectory-name

The name of the recreated directory.

Description

The recreate directory command recreates an existing directory (in a source subtree) as a new directory (in a target subtree). Only the directory itself is duplicated, not its contents. This command does not delete or modify the source directory.

All writable attribute values of the source directory (CDS_Convergence, CDS_InChName, and CDS_UpgradeTo) are retained in the duplicate. The ACL entries associated with the source directory are also preserved unless you use the optional exclude acls keywords.

If you include a wildcard character in your directory-name specification, the name you specify as newdirectory-name must already exist. Only directories matching the wildcard are recreated in newdirectory-name.

Although all original ACL entries are retained, the duplicate directory also inherits ACL entries that may be propagated from its new parent directory in the target subtree. The principal executing this command is granted full access to the new directory.

The following attribute values are updated in the duplicate and may not match the values of the original directory: CDS_AllUpTo, CDS_CTS, CDS_DirectoryVersion, CDS_InCHName, CDS_ParentPointers, CDS_Replicas, and CDS_UTS.

Permissions Required

You must have read and insert permission to the target directory (newdirectory-name) in which you intend to recreate the source directory. You also need write permission to the clearinghouse that stores the master replica of the target directory.

Example

The following command recreates the existing directory /.:/sales/quar1 as a new directory named /.:/mkt/quar1 .

cdscp> recreate directory /.:/sales/quar1 as directory /.:/mkt/quar1

See Also

merge_file
merge_subtree
recreate_link
recreate_object

Recreates an existing soft link as a new soft link with a new full name.

Synopsis

cdscp recreate link link-name [as] link newlink-name [exclude acls]

Parameters

link-name

The full name of the soft link.

newlink-name

The new name of the soft link you are recreating. If you specify the name of an existing directory in the target subtree, the soft link is recreated in that directory with its original simple link name.

Description

The recreate link command creates a copy of the specified soft link with a new full name. All of the soft link's writable attribute values are retained in the duplicate. (CDS_CTS and CDS_UTS attribute values are not preserved.) You can use the optional exlude acls keywords to omit the original ACL entries from the duplicate.

Although all original ACL entries are retained, the new soft link also inherits ACL entries that may be propagated from the new parent directory in the target subtree. The principal executing this command is granted full access to the new soft link.

You can use a trailing wildcard character after the link-name argument to recreate multiple soft links. In this case, you must specify a directory in the newlink-name argument, and all recreated soft links will have the same simple names as their sources.

Permissions Required

You must have insert permission to the directory in which you intend to recreate the soft link.

Example

The following command recreates all soft links that exist in the /.:/sales directory as new soft links in the /.:/mkt directory.

cdscp> recreate link /.:/sales/* as link /.:/mkt

See Also

merge_file
merge_subtree
recreate_directory
recreate_object

Recreates an existing object entry as a new object entry with a new full name.

Synopsis

cdscp recreate object object-name [as] object newobject-name [exclude acls]

Parameters

object-name

The full name of the object.

newobject-name

The new name of the copy of the object entry. If you specify the name of an existing directory in the target subtree, the object specified in object-name is recreated in that directory with its original simple name.

Description

The recreate object command creates a copy of an object entry with a new full name. All of the object's writable attribute values, including its ACL, are retained in the duplicate. (CDS_CTS and CDS_UTS attribute values are not preserved.) You can use the optional exclude acls keywords to omit the original ACL entries from the duplicate.

Although all original ACL entries are retained, the new object entry also inherits ACL entries that may be propagated from the new parent directory in the target subtree. The principal executing this command is granted full access to the new object entry.

You can use a trailing wildcard character after the object-name argument to recreate multiple object entries. In this case, you must specify an existing directory in the newobject-name argument and all duplicate object entries will have the same simple names as their sources. The command does not modify or delete the source object entry (or entries).

Permissions Required

You must have insert permission to the directory in which you intend to recreate the object entry.

Example

The following command recreates the existing object entry /.:/eng/psprinter03 as a new object entry named /.:/rnd/printer01.

cdscp> recreate object /.:/eng/psprinter03 as object /.:/rnd/printer01

See Also

merge_file
merge_subtree
recreate_directory
recreate_link

	privacy and legal statement
6533_DCE_REF_PRO_006.HTML