Error No Registered Vob Tag In Path
with cleartool edcsThis topic has been locked. 3 replies Latest Post - 2009-10-14T09:56:25Z by SystemAdmin Display:ConversationsBy Date 1-4 of 4 Previous Next John1971 270002N9QN 2 Posts Pinned topic ClearCase troubles with cleartool edcs 2009-10-10T11:59:06Z | Tags: Answered question This question has been answered. Unanswered question This question has not been answered yet. I have a CLearCase multimsite on my CC server running Redhat 7.2: $cleartool -ver ClearCase version 2002.05.00 (Wed Jan 30 13:23:18 EST 2002) @(#) MVFS version (Fri Jan 18 03:20:39 EST 2002) cleartool 2002.05.00 (Tue Jan 22 01:13:53 EST 2002) db_server 2002.05.00 (Tue Jan 22 01:12:24 EST 2002) VOB database schema version: 53 The problem is that when I want to edit my config spec in order to select a different label for a given pattern it fails returning the error: ............ Please find attached the output of my running context: $pwd /cc/ufc/communit $ ct lsvob -l /cc/ufc/ /vobstorage/vobstg_tsd/ufc.vbs public ............... $ ct lsvob -l /cc/ufc/ Tag: /cc/ufc/ Global path: /vobstorage/vobstg_tsd/ufc.vbs Server host: balder Access: public Mount options: Region: tsd_unix Active: YES Vob tag replica uuid: bf3e2d3e.ade011de.8bf6.00:16:36:14:c6:a1 Vob on host: balder Vob server access path: /vobstorage/vobstg_tsd/ufc.vbs Vob family uuid: bf3e2d3a.ade011de.8bf6.00:16:36:14:c6:a1 Vob replica uuid: bf3e2d3e.ade011de.8bf6.00:16:36:14:c6:a1 $ct lstype -kind lbtype ............ 30-Sep.19:46 root label type "LATEST" "Predefined label type used to represent the latest version on a branch." 09-Oct.20:57 root label type "RELEASE1" ............ ct edcs element * CHECKEDOUT element /cc/ufc/communit/... .../rhel5/LATEST .............. element * /main/LATEST HERE I am trying to use a different pattern '/cc/ufc/communit/...' instead of the default one * and when I press YES
DISCLAIMER DONATE ABOUT US Who is Phil for Humanity Contact Us Write for Us Reference Us Popular Articles The Pros and Cons of Capital Punishment The Pros and Cons of Drones Reasons For and Against Human Cloning The Effects of the Black Death on the Middle Ages Latest Articles How the IoT Can Help Cities Humanities Plastic Addition Saving Our Ocean Understanding Emergency Food Supplies ClearCase Support: Common ClearCase Config Spec Error Message Here is a common ClearCase error that https://www.ibm.com/developerworks/community/forums/thread.jspa?threadID=279072 I am asked to resolve about once a month or so. $ cleartool edcs Set config spec for view "VIEW_NAME"? [yes] cleartool: Error: No registered VOB tag in path: "/VOB_NAME/...". cleartool: Error: Config spec semantic processing failed. Errors during compilation - edit config spec? [yes] The problem is that a Windows Config Spec is being http://www.philforhumanity.com/ClearCase_Support_46.html used on UNIX. Specifically, Windows VOB paths typically start with "\VOB_NAME\" or "/VOB_NAME/". For instance, a "tools" VOB will have a VOB path of "\tools\". Unfortunately, this is not a valid path for ClearCase in UNIX. On UNIX, we must use the VOB tag for the VOB path instead of just the VOB name. For example, the "tools" VOB will need to have the path of "/vob/tools/" or "/vobs/tools/". Therefore, to resolve the above error message, all you have to do is update each Windows VOB path in your config spec to use UNIX paths instead. Alternatively, the same error will happen if you try to import a UNIX config spec onto Windows. The solution is to convert the UNIX VOB paths to Windows VOB paths. by Phil for Humanityon 20081023 Related Articles» ClearCase Support: Automate Checking of ClearCase Server Log Files » ClearCase Support: Another Common ClearCase Labeling Error Message » ClearCase Support: Issue with Links and Config Specs Copyright © 2006-2016, Phil for Humanity. All Rights Reserved.
a ClearCase command in the search box. Commands Index: *intro annotate apropos catcr catcs cc.icon cc.magic http://www.ipnom.com/ClearCase-Commands/config_spec.html cd chactivity chbl checkin checkout checkvob chevent chflevel https://issues.jenkins-ci.org/browse/JENKINS-6398?page=com.atlassian.streams.streams-jira-plugin:activity-stream-issue-tab 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 error no 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 error no registered 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_manag
- 15th for workshops, presentations and all things Jenkins Learn more Export Tools JenkinsJENKINS-6398Plugin generates invalid config spec rule for rootless components.Log In ExportXMLWordPrintable Details Type: Bug Status: Closed Priority: Blocker Resolution: Fixed Component/s: clearcase-ucm-baseline-plugin Labels: None Environment: ClearCase plugin: 1.1.1 UCM Plugin: 1.5.1 Similar Issues: Show Description We are using v1.5.1 of your plugin and 1.1.1 of the ClearCase plugin. It works nicely except for one little glitch that unfortunately makes it unusable here... It is caused by the way the plugin handles rootless components. The config specs generated by the plugin adds an invalid rule in the config specs for rootless components. This breaks the config specs and stops the process right there. The plugin should ignore rootless components when composing the config specs rules. In the sample below, the VSP4 component is rootless. Here is what I get: Started by user