Clearcase CMI Integration mkcmprovider command doesn't recognize -options - clearcase

I am using BASE Clearcase with CMI integration.
In the mkcmprovider command, if I use -options, then the command fails due to unrecognized token called '-options'.
But the Clearcase 8.0x manual says that the -options keyword is valid inside mkcmprovider.
Following is the VERSION information of my server:
M:\DevView\Test>cleartool -version
ClearCase version 8.0.1.00 (Mon May 27 15:08:54 EDT 2013) (8.0.1.D130526)
#(#) MVFS version 8.0.1.0 (Wed May 15 14:57:16 2013)
cleartool 8.0.1.0 (Wed May 15 21:46:14 2013)
db_server 8.0.1.0 (Wed May 15 18:40:45 2013)
VOB database schema versions: 54, 80
Following is the error:
M:\DevView\Test>cleartool mkcmprovider -brtype main -replace -options ciVerifyPr
ov:true,ciVerifyUser:true,reqProvTask:true CQPROV
cleartool: Error: Unrecognized option "-options"
Usage: mkcmprovider {-vob vob-selector | -replica replica-selector} `enter code here`[-replace]
{-data prov-info-file | -type <type> -version <version> -des
cription <description>
-connection <connection_info>} provider_name
mkcmprovider {-brtype <brtype-name>} [-replace]
[{-data context-info-file | -context <context-string>}] prov
ider_name

Make sure to actually type the '-' of '-options' instead of copying it from the IBM documentation for cleartool mkcmprovider.
The doc has only has a minus instead of the hyphen-minus.
However, in this case, -options is only supported from 8.0.1.5: see the 8.0.1.X release notes.
What's New
This release introduces the following features.
Change management interface (CMI)
The following enhancements to CMI are introduced in this release:
CMI supports the configuration of Rational Team Concert state transitions; for instructions, refer to Configuring CMI for Rational Team Concert state transitions.
The mkcmprovider command supports policy configuration for base ClearCase and UCM; for complete information, refer to the command reference page.
ClearTeam Explorer (CTE) supports CMI independent of the RTC bridge for dynamic views only.

Related

Openstack installation issue on ubuntu-18.04

$ cat /etc/issue
Ubuntu 18.04.6 LTS \n \l
I'm following this Link to install Openstack using Devstack. However git clone https://git.openstack.org/openstack-dev/devstack master branch's ./stack.sh fails with below error.
+./stack.sh:main:230 SUPPORTED_DISTROS='bullseye|focal|f34|opensuse-15.2|opensuse-tumbleweed|rhel8|rhel9|openEuler-20.03'
+./stack.sh:main:232 [[ ! bionic =~ bullseye|focal|f34|opensuse-15.2|opensuse-tumbleweed|rhel8|rhel9|openEuler-20.03 ]]
WARNING: this script has not been tested on bionic
+./stack.sh:main:234 [[ '' != \y\e\s ]]
+./stack.sh:main:235 die 235 'If you wish to run this script anyway run with FORCE=yes'
+functions-common:die:253 local exitcode=0
+functions-common:die:254 set +o xtrace
[Call Trace]
./stack.sh:235:die
[ERROR] ./stack.sh:235 If you wish to run this script anyway run with FORCE=yes
/opt/stack/devstack/functions-common: line 299: /opt/stack/logs/error.log: No such file or directory
Even ./stack.sh FORCE=yes and stable/newton, stable/pike, stable/victoria & stable/xena branch also results the same above error.
Does the support for Ubuntu 18.04.6 LTS (bionic) deprecated?
Does the support for Ubuntu 18.04.6 LTS (bionic) deprecated?
Not exactly.
As a general rule, the latest version of the script targets the latest supported (by Openstack) versions of the host operating systems. Older versions may work. But there might be minor issues ... that someone with the ability to read / diagnose shell scripts ought to be able to figure out.
If you need a version of the script that explicitly supports (say) Bionic, there will be one in the Git6 repo history.
(This is in line with general OpenStack Ubuntu support. The latest OpenStack release is Wallably and Wallaby no longer supports Bionic. The Bionic -> Focal cross-over release of Openstack was Ussuri; see https://ubuntu.com/openstack/docs/supported-versions. Note that Devstack is not an official OpenStack product, but they are effectively forced to track the "supported release" rules, at least loosely.)
The version of the Devstack script that you checked out does not explicitly supports Focal rather than Bionic.
If you look at https://opendev.org/openstack/devstack/src/branch/master/stack.sh on line 230, it currently says:
# Warn users who aren't on an explicitly supported distro, but allow them to
# override check and attempt installation with ``FORCE=yes ./stack``
SUPPORTED_DISTROS="bullseye|focal|f34|opensuse-15.2|opensuse-tumbleweed|rhel8|rhel9|openEuler-20.03"
If you want a version of devstack that explicitly supports bionic, use git blame (or whatever) to track changes to the SUPPORTED_DISTROS line. You should be able to find some versions where FORCE is not necessary.
On the other hand .... the error message:
/opt/stack/devstack/functions-common: line 299: /opt/stack/logs/error.log:
No such file or directory
implies that the script is assuming that a file or directory already exists. You could probably just create it / them by hand. (It is clearly just a log file / directory.)

Gatling can't run simulation

I'm using gatling 2.2.3 and I'm following the Quickstart guide. I've got it all working up until the point where I can run the scenario.
Instead of allowing me to select the simulation I want to run I'm getting this output:
U:\>%GATLING_HOME%\bin\gatling.bat
GATLING_HOME is set to "C:\Users\name\Downloads\gatling-charts-highcharts-bundle-2.2.3\"
JAVA = "java"
Usage: java [-options] class [args...]
(to execute a class)
or java [-options] -jar jarfile [args...]
(to execute a jar file)
where options include:
-d32 use a 32-bit data model if available
-d64 use a 64-bit data model if available
-server to select the "server" VM
The default VM is server.
-cp <class search path of directories and zip/jar files>
-classpath <class search path of directories and zip/jar files>
A ; separated list of directories, JAR archives,
and ZIP archives to search for class files.
-D<name>=<value>
set a system property
-verbose:[class|gc|jni]
enable verbose output
-version print product version and exit
-version:<value>
Warning: this feature is deprecated and will be removed
in a future release.
require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -no-jre-restrict-search
Warning: this feature is deprecated and will be removed
in a future release.
include/exclude user private JREs in the version search
-? -help print this help message
-X print help on non-standard options
-ea[:<packagename>...|:<classname>]
-enableassertions[:<packagename>...|:<classname>]
enable assertions with specified granularity
-da[:<packagename>...|:<classname>]
-disableassertions[:<packagename>...|:<classname>]
disable assertions with specified granularity
-esa | -enablesystemassertions
enable system assertions
-dsa | -disablesystemassertions
disable system assertions
-agentlib:<libname>[=<options>]
load native agent library <libname>, e.g. -agentlib:hprof
see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:<pathname>[=<options>]
load native agent library by full pathname
-javaagent:<jarpath>[=<options>]
load Java programming language agent, see java.lang.instrument
-splash:<imagepath>
show splash screen with specified image
See http://www.oracle.com/technetwork/java/javase/documentation/index.html for more details.
It seems like it's trying to execute some Java command which isn't done properly. Does anyone know how I can fix this?
What this folder is:
U:>%GATLING_HOME%
Be sure don't have blank spaces in it

ClearCase SCM Adapter support for annotate

I wanted to annotate some code with version history. This is easy in Eclipse when using SVN, but the Rational ClearCase SCM Adapter plugin doesn't appear to support it.
I quick Google search reveals that on the command line ClearCase supports annotate via:
cleartool annotate -out - -fmt "%Vn |" -rm -nheader util.c
I also found a number of non-free plugins that support annotate.
Any free alternatives?
The cleartool annotate is the only form of annotation (or "blame") for ClearCase, and isn't available through the official plugins (ClearCase SCM adapter, or the CCRC plugin)
That is why you will fond some non-free option like:
annotate add-on
Visual Annotate (could have a free edition soon, according to his author Tamir Gefen)
FishEye & Crucible, although that stopped 4th April 2012, with FishEye 2.8.
In Visual Studio you can set it up to run the cleartool command line option (Using the Tools->External Tools...).
It seems like eclipse has a similar feature ("FAQ How do I add my own external tools?")
Command: \installationpath\cleartool.exe
Arguments: annotate -nheader $(ItemPath)
Initial directory: $(ItemDir)
After it creates the file you can open in your favorite editor.
I only mention it because it might be an option as it is free.
It is easier then using the command line excluding when my project files have the wrong capitalization which causes cleartool to not work and I find myself either update the .vcproj or using the command line.

I can't seem to get cleartool's find to work on a simple query

Disclamer: I'm very new to Clear Case.
I want to find out what files I've modified on a given date. I am using a Snapshot view:
ClearCase version 7.1.2.0 (Tue Sep 21 12:01:15 EDT 2010) (7.1.2.D100920)
#(#) MVFS version 7.1.2.0 (Tue Aug 10 00:37:25 2010)
cleartool 7.1.2.0 (Wed Sep 8 12:56:06 2010)
db_server 7.1.2.0 (Sat Sep 4 01:27:12 2010)
VOB database schema version: 54
EDIT: FYI, my view was created via CCRC (Clear Case Remote Client).
Here's what I've tried (from my Windows machine):
cd c:\SnapshotViews\my_view_name
cleartool
cleartool> find . -element "{created_since(12-Mar-2012)}" -print
cleartool: Error: Not an object in a vob: ".".
cleartool: Warning: Skipping ".".
cleartool>
cleartool> find . -cview -version 'created_since(12-Mar-2012)' -print
cleartool: Error: Not an object in a vob: ".".
cleartool: Warning: Skipping ".".
The IBM docs are sort of useless, the queries they provide don't work either. Can someone help me out?
You must go one directory within your snapshot view in order to be in a Vob.
c:\SnapshotViews\my_view_name is the root directory of your snapshot view
c:\SnapshotViews\my_view_name\aVob is within a Vob as referenced by the config spec of your snapshot view
Only Vobs contains elements (versions of directories and files), which means your cleartool find command can only find said elements within a Vob.
See "Additional examples of the cleartool find command" for more.
See also cleartool find man page.
If you stay at the root level of your snapshot view, you can type:
cleartool find <vobtag> -element "{created_since(target-data-time)}" -print
However, if you are on CCRC (that is ClearCase Remote Client), you won't have access to the cleartool find command.
Only a subset of cleartool commands are supported: see "Rational ClearCase Remote Client Command Line Interface (CCRC CLI)".

How to make check-outs be unreserved by default using ClearCase command line tools

Is there a way to make cleartool checkouts unreserved by default? Perhaps a ~/.cleartool file or some environment variable? I understand the default can be set on the VOB (or all VOBs), but that option is beyond my control.
The ClearCase version I'm using is:
$ ct -version ClearCase version 7.0.1 (Wed May 30 17:04:58 EDT 2007)
7.0.1.0-RATL-RCC-IFIX01 (Wed Sep 19 16:08:10 EDT 2007) #(#) MVFS version
7.0.1.0-IFIX01 (Thu Sep 6 20:09:08 2007) built at $Date: 2009-12-08.14:59:16 (UTC) $ cleartool
7.0.1.0-IFIX01 (Thu Aug 9 20:20:45 EDT 2007) db_server
7.0.1.0-IFIX01 (Fri Sep 14 20:23:09 EDT 2007) VOB database schema version: 54
You may ask "why in world would the default ever be set to -reserved?" A fair question. However, the matter is beyond my control.
Update: I neglected to mention the environment is Linux.
In the ClearCase Explorer, menu:
Tool / Options / button ClearCase Options / Tab "Operations"
Unchecked "reserved" in the "Check out" section.
However, this is for one user, not a global setting for all users...
On Windows, this is stored in the registry at:
HKEY_CURRENT_USER\Software\Atria\ClearCase\CurrentVersion\Checkout
key:
Reserved 0
So if you can add that as a post-install setting, you could generalize that behavior to all users using your custom setup.
alt text http://www-01.ibm.com/support/docview.wss?uid=swg21135939&aid=2
See also this IBM technote.
The OP unhillbilly comments rightly about the command cleartool unres (unreserve), which:
changes the checkout status of a checked-out version of an element to unreserved.
A temporary unreserve checkout of version event record is written to the VOB database.
I know this is an old post, but in case anyone in the future comes along with the same question, here's my answer.
If you want to set up a trigger so that everyone performs UNRESERVED checkouts then use the following command:
cleartool mktrtype -element -all -post checkout -exec '/opt/rational/clearcase/bin/cleartool unreserve -nc '$CLEARCASE_PN' TRIGGERNAME
The command I posed above should have another single quote so that it is '$CLEARCASE_PN' TRIGGERNAME

Resources