lslock

Type objects can be rendered obsolete with the lock –obsolete xxtype: command. lslock lists an obsolete type object if you specify its name with a type-name argument or you use the –obsolete option.

Default

lslock displays the lock state of the global type for the object selector you specify.

–local

Displays the lock state of the local copy of the global type. For more information, see the DevOps Code ClearCase Administrator's Guide.

Default

A lock listing looks like this:

—09-01T08:42 drp lock attribute type "AT2" (locked)
"Locked for all users."

–l/ong

Expands the listing with more time-specific and user-specific information.

–s/hort

Restricts the listing to names of locked objects only.

–fmt format-string

Lists information using the specified format string. For details about using this report-writing facility, see the fmt_ccase reference page.

Default

An obsolete object is not listed unless you specify it with a command-line argument.

–obs/olete

Includes obsolete objects in the listing. (Has no effect if you specify one or more objects with arguments.)

Default

Lists all the locks created in the VOB containing the current working directory.

[ –pna/me ] pname ...

One or more path names, each of which specifies an element or branch:

foo.c	Element foo.c
foo.c@@	Element foo.c
foo.c@@/main/bugfix	Branch of element foo.c

(Versions cannot be locked; a path name to a version references the element object.) Using pname arguments restricts the listing to locks on those particular objects (but see the –all description below).

If pname has the form of an object selector, you must include the –pname option to indicate that pname is a path name.

Note: Specifying an element lists only the lock on the element itself, not on any of its branches.

–all

For each pname argument, lists all locks in the VOB containing pname. Has no effect if you do not specify any pname argument (because the default is to list all locks in the current VOB).

object-selector ...

One or more non-file-system VOB objects. The objects must exist in the VOB containing the current working directory, unless you specify another VOB with @vob-specifier. Specify object-selector in one of the following forms:

Table for object-selector

vob-selector	[vob:]pname-in-vob
	pname-in-vob can be the pathname of the VOB tag (whether or not the VOB is mounted) or of any file system object within the VOB (if the VOB is mounted). It cannot be the pathname of the VOB storage directory.
attribute-type-selector	attype:type-name[@vob-selector]
branch-type-selector	brtype:type-name[@vob-selector]
element-type-selector	eltype:type-name[@vob-selector]
hyperlink-type-selector	hltype:type-name[@vob-selector]
label-type-selector	lbtype:type-name[@vob-selector]
trigger-type-selector	trtype:type-name[@vob-selector]
pool-selector	pool:pool-name[@vob-selector]
oid-obj-selector	oid:object-oid[@vob-selector]
The following object selector is valid only if you use MultiSite:
replica-selector	replica:replica-name[@vob-selector]