Bindery Queue

Represents an object that has been created by the Bindery Emulator to emulate a user-defined queue object.

Type:Effective
NDS Operational:Yes

ASN.1 ID

Class Flags

Class Flags

Setting

Container

Off

Effective

On

Nonremovable

On

Ambiguous Naming

Off

Ambiguous Container

Off

Auxiliary Class

Off

Class Structure

Mandatory Object Class

Bindery Queue

Inherited from Top

Inherited from Resource

Inherited from Queue

Bindery Type

Object Class

CN (Common Name)

Queue Directory

Optional Attributes

Bindery Queue

(None)

 

Default ACL Template

Object Name

Default Rights

Affected Attributes

Class Defined For

[Creator]

Supervisor

[Entry Rights]

Top

[Root]

Read

[All Attributes]

Bindery Queue

Remarks

For help in understanding the class definition template, see Reading Class Definitions.

The queue management service (QMS) requires the Host Server attribute to identify the NCP server that holds this queue.

The Queue directory names the subdirectory where this queue’s files are stored.

The Operator, Server, and User attributes are used by the QMS as access control lists.

The Operator attribute identifies users or groups that have operator privileges. The Server attribute identifies print servers allowed to service this queue.

The User attribute contains a list of objects that are authorized to use this queue. The server that controls the queue must determine if the user list is maintained by an administrator or if the list is automatically generated by the server. If the user list is used by the server as an access control list, the administrator will usually maintain the list. If the user list is purely informational, reflecting access control information stored elsewhere, the server usually maintains the list.

The See Also attribute might be used to list related queues. For example, two queues, “Fast” and “Slow,” might provide the same set of services, except that “Fast” runs at a higher priority. These two queues might reference each other in their respective See Also attributes.

The Host Resource Name attribute is used when the host’s local identification for a resource differs from the global resource identification. For example, a server might recognize “SYS:” as the local name for a volume with the following eDirectory name:

"Project X.Engineering.Acme.US"

The L (Locality Name), O (Organization Name), and OU (Organizational Unit Name) attributes are useful when multiple localities, organizations, or organizational units use a single resource. If these attributes contain appropriate values, a search can be initiated for resources associated with a particular locality or organization.

The Network Address attribute (inherited from Resource) acts as a cache for the server’s network address. The user can contact the server without having to dereference the Host Server attribute.

For LDAP clients to access this class, the LDAP server must map this class to a name that contains no spaces or colons.