IPnom Home • Manuals • ClearCase

 Rational ClearCase Commands Reference

ClearCase Stuff:ClearCase LinksClearCase BooksClearCase Commands ReferenceClearCase ForumsClearCase News
Keyword Live Search (10 results max):
 Type in part of a ClearCase command in the search box.
 
Commands Index:
  intro
  annotate
  apropos
  catcr
  catcs
  cc.icon
  cc.magic
  cd
  chactivity
  chbl
  checkin
  checkout
  checkvob
  chevent
  chflevel
  chfolder
  chmaster
  chpool
  chproject
  chstream
  chtype
  chview
  clearaudit
  clearbug
  cleardescribe
  cleardiffbl
  cleardiff
  clearexport_ccase
  clearexport_cvs
  clearexport_pvcs
  clearexport_rcs
  clearexport_sccs
  clearexport_ssafe
  clearfsimport
  cleargetlog
  clearhistory
  clearimport
  clearjoinproj
  clearlicense
  clearmake
  clearmake.options
  clearmrgman
  clearprojexp
  clearprompt
  cleartool
  clearviewupdate
  clearvobadmin
  comments
  config_ccase
  config_spec
  cptype
  credmap
  creds
  deliver
  describe
  diffbl
  diffcr
  diff
  dospace
  edcs
  endview
  env_ccase
  events_ccase
  export_mvfs
  exports_ccase
  file
  find
  findmerge
  fmt_ccase
  getcache
  get
  getlog
  help
  hostinfo
  init_ccase
  ln
  lock
  lsactivity
  lsbl
  lscheckout
  lsclients
  lscomp
  lsdo
  lsfolder
  lshistory
  ls
  lslock
  lsmaster
  lspool
  lsprivate
  lsproject
  lsregion
  lsreplica
  lssite
  lsstgloc
  lsstream
  lstype
  lsview
  lsvob
  lsvtree
  makefile_aix
  makefile_ccase
  makefile_gnu
  makefile_pmake
  makefile_smake
  makefile_sun
  man
  merge
  mkactivity
  mkattr
  mkattype
  mkbl
  mkbranch
  mkbrtype
  mkcomp
  mkdir
  mkelem
  mkeltype
  mkfolder
  mkhlink
  mkhltype
  mklabel
  mklbtype
  mkpool
  mkproject
  mkregion
  mkstgloc
  mkstream
  mktag
  mktrigger
  mktrtype
  mkview
  mkvob
  mount_ccase
  mount
  msdostext_mode
  mvfslog
  mvfsstorage
  mvfstime
  mvfsversion
  mv
  omake
  pathnames_ccase
  permissions
  profile_ccase
  promote_server
  protect
  protectvob
  pwd
  pwv
  query_language
  quit
  rebase
  recoverview
  reformatview
  reformatvob
  register
  relocate
  rename
  reqmaster
  reserve
  rgy_backup
  rgy_check
  rgy_passwd
  rgy_switchover
  rmactivity
  rmattr
  rmbl
  rmbranch
  rmcomp
  rmdo
  rmelem
  rmfolder
  rmhlink
  rmlabel
  rmmerge
  rmname
  rmpool
  rmproject
  rmregion
  rmstgloc
  rmstream
  rmtag
  rmtrigger
  rmtype
  rmver
  rmview
  rmvob
  schedule
  schemes
  scrubber
  setactivity
  setcache
  setcs
  setplevel
  setsite
  setview
  shell
  snapshot.conf
  softbench_ccase
  space
  startview
  type_manager
  umount
  uncheckout
  unlock
  unregister
  unreserve
  update
  version_selector
  view_scrubber
  vob_restore
  vob_scrubber
  vob_sidwalk
  vob_snapshot
  vob_snapshot_setup
  wildcards_ccase
  winkin
  xclearcase
  xcleardiff
  xmldiffmrg

chtype

Changes the type of an element or renames a branch

APPLICABILITY

ProductCommand type
ClearCasecleartool subcommand
ClearCase LTcleartool subcommand

Platform
UNIX
Windows

SYNOPSIS

chtype [ –c·omment comment | –cfi·le comment-file-pname
| –cq·uery | –cqe·ach | –nc·omment ]
[ –f·orce ] [ –pna·me ] type-selector
{ pname ... | object-selector ... }

DESCRIPTION

The chtype command changes the element type of one or more existing elements or renames one or more existing branches. These operations involve changing the type object associated with the element or branch.

RESTRICTIONS

Identities

For an element, you must have one of the following identities:

  • Element owner
  • VOB owner
  • root (UNIX)
  • Member of the ClearCase administrators group (ClearCase on Windows)
  • Local administrator of the ClearCase LT server host (ClearCase LT on Windows)

For a branch, you must have one of the following identities:

  • Branch creator
  • Element owner
  • VOB owner
  • root (UNIX)
  • Member of the ClearCase administrators group (ClearCase on Windows)
  • Local administrator of the ClearCase LT server host (ClearCase LT on Windows)

Locks

An error occurs if one or more of these objects are locked:

ElementVOB, element type, element, pool
BranchVOB, element type, element, branch type, branch.

Mastership

(Replicated VOBs only) For an element, your current replica must master the element. For a branch, your current replica must master the new branch type and the branch you are changing.

OPTIONS AND ARGUMENTS

Event Records and Comments

Default
Creates one or more event records, with commenting controlled by your .clearcase_profile file (default: –nc). See the comments reference page. Comments can be edited with chevent.

–c·omment comment | –cfi·le comment-file-pname |–cq·uery | –cqe·ach | –nc·omment
Overrides the default with the option you specify. See the comments reference page.

Confirmation Step

Default
chtype prompts for confirmation if changing an element's type will change the way its versions are stored in the VOB storage pool.

–f·orce
Suppresses the confirmation step.

Specifying the New Type

Default
None.

type-selector
An element type or branch type. The type must already exist. (Exception: If you specify a global element type or global branch type, a local copy of the type is created if one does not already exist.) Specify type-selector in the form [type-kind:]type-name[@vob-selector].
type-kind One of brtype branch type eltype element type
type-name Name of the type object
vob-selector Object-selector for a VOB, in the form [vob:]pname-in-vob. The 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)

Specifying the Elements, Branches, or Activities

Default
None.

[ –pna·me ] pname ...
One or more pathnames, each of which specifies a file or directory element. A standard pathname is valid; you need not append the extended naming symbol. That is, specifying a version is equivalent to specifying its element. Specifying a branch (for example, foo.c@@/main/bugfix) causes an error.

If pname has the form of an object selector (for example, eltype:fl2), you must use the –pname option to indicate that it is a pathname. The –pname option must precede nonoption arguments. For example:

cmd-context chtype –nc –force –pname eltype:c_source eltype:fl2

object-selector ...
One or more extended pathnames, each of which specifies a particular branch of an element. For example:

foo.c@@/main/bugfix
bar.@@/main/maint/bug405

EXAMPLES

The UNIX examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.

The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.

In cleartool single-command mode, cmd-context represents the UNIX shell or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.

  • Convert an element to type file.

    cmd-context chtype file hello.c 
    Change version manager and reconstruct all versions for "hello.c"? [no] yes
    Changed type of element "hello.c" to "file".

  • Change branch rel2_bugfix to branch maintenance, providing a comment.

    cmd-context chtype -c "rel2_bugfix no longer in use" maintenance util.c@@\main\rel2_bugfix 
    Changed type of branch "util.c@@\main\rel2_bugfix" to "maintenance".

  • Convert an archive library to compressed_file format, suppressing confirmation prompts.

    cmd-context chtype -force compressed_file libutil.a 
    Changed type of element "libutil.a" to "compressed_file".

SPONSORED LINKS



 

ClearCase Links • ClearCase Books • ClearCase Commands Reference • ClearCase Forums • ClearCase News