." ." Copyright (c) 1991 by Sun Microsystems, Inc. ." ." @(#)codemgr.1 92/05/18 SMI ." .TH CODEMGR 1 "01 December 1992" .SH NAME codemgr \- The TeamWare "umbrella" command. .SH SYNOPSIS .B codemgr .RI [ " command " ] .SH DESCRIPTION .IX "CodeManager" "TeamWare" "codemgr" "" "\fBcodemgr\fP" .TP 7 Note: The .B man pages for TeamWare commands are referenced by specifying the individual command name. TeamWare was formerly known as CodeManager. The command .B man pages are listed in the .SM "SEE ALSO" section of this man page. .LP Like .SM SCCS commands, all TeamWare .SM CLI commands can be executed through a central "umbrella" command. The individual commands may also be executed directly by specifying the individual command name. The umbrella command named .B codemgr provides a unified method of execution that enables you to conveniently list TeamWare commands. .LP TeamWare commands can be listed along with their usage summaries by executing .B codemgr without specifying any arguments. You can achieve the same results by executing .B codemgr with the .B help subcommand. .LP To use the umbrella command to execute commands, type .B codemgr followed by the name of the subcommand you wish to execute. For example: .IP \fBexample% codemgr bringover -w my_child -p their_parent /usr/ws/project\fP .LP Since using the .B codemgr umbrella command requires extra typing, you may also execute the commands directly (without typing .BR codemgr ")." For example: .IP \fBexample% bringover -w my_child -p their_parent /usr/ws/project\fP .SH USAGE .TP 12n .B help Specify the .B help subcommand to cause the .B codemgr command to list the TeamWare commands with a usage summary for each. You can achieve the same results by executing .B codemgr without specifying any arguments. .SH ENVIRONMENT .TP 25 .SM CODEMGR_PATH_ONLY TeamWare commands first search for other TeamWare binaries relative to where their own binary is located in the file system, they then search in the directories specified in the .SM PATH environment variable. Setting this variable causes TeamWare commands to search for other TeamWare binaries only in .SM PATH. .SH "SEE ALSO" .I TeamWare User's Guide .sp 0 .BR bringover (1), .BR def.dir.flp (1), .BR putback (1), .BR resolve (1), .BR twmerge (1), .BR ws_undo (1), .BR workspace (1), .BR access_control (4), .BR args (4), .BR children (4), .BR conflicts (4), .BR history (4), .BR locks (4), .BR nametable (4), .BR notification (4), .BR parent (4)