readme-cmvc-client-samples.html

CMVC是IBM和许多跨国公司的缺陷管理工具。这里给出了很多在Linux下用KSH编写的使用CMVC命令的例子。这些例子来自于IBM内部的CMVC培训。

numbers and abstracts that caused a change to a specified
file in a specified release.
<p>

<li> fileInfo.sh
<br> 
This sample shell script displays information for a specified file.
<p>

<li> filesInComp.sh
<br> 
This sample shell script lists all files related to a specified component.
<p>

<li> filesInRelease.sh
<br> 
This sample shell script lists all files related to a specified release.
<p>

<li> filesLockedBy.sh
<br> 
This sample shell script lists all files that a specified user has locked.
<p>

<li> fileVersionsInLevel.sh
<br> 
This sample shell script shows the file versions that are included in a level.
<p>

<li> findFilePath.sh
<br> 
This sample shell script finds and lists all files that
match a partial file path name
<p>

<li> findUser.sh
<br> 
This shell script finds user information based on part of the
user's name.  It will perform a fuzzy search for the user based
on the part of the user's name that is provided.  For example,
if you want to find the id for a person with the last name of
Smith, you would enter :  findUser smith
The result will be a list of users who have Smith as parth of
their name.
<p>

<li> getCompFiles.sh
<br> 
This sample shell script gets all the files associated with a
specific component.  The files are placed in a directory that
represents the release name to which the version of the file
is associated.  This directory is created relative to the
relativePathName parameter.  The most recently created version
of the file will be extracted by default unless the committed
parameter is provided in which case only the committed versions
will be extracted.
<p>

<li> getTrackFiles.sh
<br> 
This sample shell script gets all the files associated with a
specific track and places them in the path specified by the
relativePathName parameter.
<p>

<li> giveAccessAuth.sh
<br> 
This sample shell script lists the users who have the authority
to give other users access to a specified component.
<p>

<li> levelFileChgs.sh
<br> 
This sample shell script lists the files that were
changed for a specified level.
<p>

<li> levelHasDefFea.sh
<br> 
This sample shell script lists the name of the levels that
contain a specified defect or feature.
<p>

<li> levelMembers.sh
<br> 
This sample shell script lists the defect and feature
members of a specified level for a specified release.  The
releaseName will be taken from the CMVC_RELEASE environment
variable if it is not supplied on the command line.
<p>

<li> managerReport.sh
<br> 
This sample shell script generates a manager's report
based on the specified areas or departments of interest.

The report contains the following statistics:
 + Open defects owned by the specified ownerarea (DEPTS)
 + Returned defects originated by originarea (DEPTS)
 + Ready test records owned by userarea (DEPTS)
 + Active size records owned by userarea (DEPTS)
 + Active features owned by ownerarea (DEPTS)
 + Returned features originated by originarea (DEPTS)
 + Blocked or NotReady test records owned by ownerarea (DEPTS)
 + Active defects owned by ownerarea (DEPTS)
<p>

<li> mrClean.pl
<br> 
This is a PERL script.
<br>
To clean up "dead" releases.
Remove work associated with uncommitted tracks,  
the tracks themselves and any empty levels.
Return defect/feature if track cancelled and
there are no others (in other releases).
<br>
The user running the script must have sufficient    
authority (superuser, projectLead ?) for the CMVC
commands.  Otherwise, mrClean will miss a few spots.
<br>
The output is logged in mrClean.log in the working directory.
<p>

<li> mrsClean.pl
<br>
This is a PERL script.
<br>
Clean up release (from CMVC_RELEASE).
Remove work associated with the input tracks,
the tracks themselves and any empty levels.
Return defect/feature if track cancelled and
there are no others (in other releases).
<br>
The user running the script must have sufficient
authority (superuser, projectLead?) for the CMVC
commands being issued.  Otherwise, mrsClean may
miss a few spots.   If other, non-specified, tracks
interfere with the undoing of a File operation, a
warning message is printed and logged.  The script
must be rerun with the interfering track(s) included
to complete the job.
<br>
The output logged to  mrsClean.log  in working directory.
<p>

<li> newestDefect.sh
This sample shell script displays the number of the most
recent defect that was entered in the system.
<br> 
This sample shell script displays the number of the most
recent defect that was entered in the system.
<p>

<li> newestFeature.sh
<br> 
This sample shell script displays the number of the most
recent feature that was entered in the system.
<p>

<li> parentComponent.sh
<br> 
This sample shell script lists the parent component of a specified component.
<p>

<li> reassignWork.sh
<br> 
This sample shell script will re-assign all current work
and objects owned by userLogin1 to userLogin2.   The user
running this script must have the appropriate authority to
modify and reassign objects.
<p>

<li> releaseOwners.sh
<br> 
This sample shell script displays a list of addresses of all
the release owners in a specified family.
<p>

<li> reopenDefect.sh
<br> 
This sample shell script reopens a previously cancelled or
returned defect
<p>

<li> reopenFeature.sh
<br> 
This sample shell script reopens a previously cancelled or returned feature.
<p>

<li> sendMailTo.sh
<br> 
This sample shell script sends a message to the addresses
read through stdin.  For example, the compOwners shell
script can be run and the output can be piped to sendMailTo
in order to send a message to all component owners.
<br>
USAGE: sendMailTo messagefile subject
<p>

<li> showAllCommonFiles.sh
<br> 
This sample shell script shows the files that are 
common to other releases; that is, it shows all the
files that are not unique to this release.
<br>
This script does NOT show the releases to which the
common files are linked to. You can use the sample
showCommonFiles to show the releases to which a 
common file is linked to.
<br>
USAGE: showAllCommonFiles releaseName
<p>

<li> showAllVersions.sh
<br> 
This sample shell script displays all the version numbers of a file.
<br>
USAGE: showFileVersions pathName releaseName
<p>

<li> showCommonFiles.sh
<br>
This sample shell script shows common files and releases.
The CMVC_RELEASE environment variable must be set 
if the release name is not specified on the command line.
<br>
USAGE: showCommonFiles filePathName [releaseName]
<p>

<li> showConfig.sh
<br>
This sample shell script lists the valid values pertaining
to a specified configurable type.
<br>
USAGE: showConfig configType
<p>

<li> showFilesChangedByUser.sh
<br>
This sample shell script shows the files that were
changed by a given user in a given release.
The most recent changes are shown first.
<br>
USAGE: showFilesChangedByUser userName
<p>

<li> showInheritedAccess.sh
<pre>
#
# FUNCTIONS:   This sample shell script shows the inherited access
#              for a component.
#
# USAGE:       showInheritedAccess  compName
</pre>
<p>

<li> showNoCommonFiles.sh
<pre>
# FUNCTIONS:   This sample shell script shows the files that are not
#              common to other releases; that is, it shows all the
#              files that are unique to this release.
#
# USAGE:       showNoCommonFiles releaseName
</pre> 
<p>

<li> trackStats.sh
<pre>
# FUNCTIONS:   This sample shell script generates a track activity statistics
#              report on a user area basis.
#
# USAGE:       trackStats userArea
</pre> 
<p>

<li> tracksInCommit.sh
<pre> 
# FUNCTIONS:   This sample shell script lists the tracks that are in the
#              commit state for a specified release.
#
# USAGE:       tracksInCommit releaseName
</pre>
<p>

<li> tracksInDevLvl.sh
<pre>
# FUNCTIONS:   This sample shell script lists the tracks that are in the
#              integrate state and are associated with at least one
#              development level for the specified release.
#
# USAGE:       tracksInDevLvl releaseName 
</pre>
<p>

<li> tracksInFix.sh
<pre> 
# FUNCTIONS:   This sample shell script lists all the tracks that are in the
#              fix state for a given release.
#
# USAGE:       tracksInFix releaseName
</pre>
<p>

<li> tracksInInt.sh
<pre> 
# FUNCTIONS:   This sample shell script lists the tracks that are in the
#              integrate state for a specified release.
#
# USAGE:       tracksInInt releaseName
</pre>
<p>

<li> tracksInProdLvl.sh
<pre> 
# FUNCTIONS:   This sample shell script lists the tracks that are in the
#              integrate state and are associated with at least one
#              production level for the specified release.
#
# USAGE:       tracksInProdLvl releaseName
</pre>
<p>

<li> tracksInTest.sh
<pre> 
# FUNCTIONS:   This sample shell script lists the tracks that are in the
#              test state for a specified release.
#
# USAGE:       tracksInTest releaseName
</pre>
<p>

<li> userAccess.sh
<pre> 
# FUNCTIONS:   This sample shell script lists the explicit access of a
#              specified userLogin for the specified component and its
#              descendant components.
#
# USAGE:       userAccess userLogin componentName
</pre>
<p>

<li> userReport.sh
<pre>
# FUNCTIONS:   This sample shell script generates a user's report
#              based on the specified userLogin.
#
#              The report contains the following statistics.
#                o Defects owned by the user that require action now
#                o Defects created by the user that require action now
#                o Verify records owned by the user that are active
#                o Fix records owned by the user that are active
#                o Test records owned by the user that are active
#                o Size records that the user must respond to
#                o Approval records that the user must respond to
#                o Features owned by the user that require action now
#                o Features originated by the user that require action now
#                o Test records owned by the user that are not ready
#                o Verify records owned by the user that are not ready
#                o Fix records owned by the user that are not ready
#                o Files checked out by the user
#                o Defects originated by the user
#                o Detail Report for all defects originated by the user
#                o Features originated by the user
#                o Defects owned by the user
#                o Features owned by the user
#                o Tracks owned by the user
#
# USAGE:       userReport userLogin 
</pre>
<p>

<li> whoHasFile.sh
<pre>
# FUNCTIONS:   This sample shell script lists who has a specified file
#              checked out.
#
# USAGE:       whoHasFile fileName 
</pre>
<p>

</ul>


<hr>
<h1> <a name="old"> Old Samples </a>
</h1>
<p>
Although these files are included in this package, 
they are considered to be obsolete.
For more details, see the comments in the header of each file.

<ul>
<li> compChildren
<br> 
This sample shell script lists the direct children of
a specified component.
Also lists the description and the owner of each child component.
<p>

<li> compOwners
<br> 
This sample shell script displays a list of component
owners' addresses in a specified family.
<p>

</ul>

<p>
*** end ***
</p>
<!-- -->
</body>
</html>
<!-- end of file -->