defaria.com/blogs/Status/archives/000239.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
   4 <head>
   5    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   6    <meta name="generator" content="Movable Type 5.2.3" />
   7
   8    <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
   9    <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
  10    <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml" />
  11
  12    <title>Status for Andrew DeFaria: Informatica/CLEARCASE_PRIMARY_GROUP</title>
  13
  14    <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
  15    <link rel="prev" href="http://defaria.com/blogs/Status/archives/000237.html" title="Permissions problems" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/000242.html" title="CLEARCASE_PRIMARY_GROUP" />
  17
  18
  19
  20
  21
  22    <script type="text/javascript" src="http://defaria.com/blogs/Status/mt-site.js"></script>
  23 </head>
  24 <body class="layout-one-column" onload="individualArchivesOnLoad(commenter_name)">
  25    <div id="container">
  26       <div id="container-inner" class="pkg">
  27
  28          <div id="banner">
  29             <div id="banner-inner" class="pkg">
  30                <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
  31                <h2 id="banner-description">Searchable status reports and work log</h2>
  32             </div>
  33          </div>
  34
  35          <div id="pagebody">
  36             <div id="pagebody-inner" class="pkg">
  37                <div id="alpha">
  38                   <div id="alpha-inner" class="pkg">
  39
  40                      <p class="content-nav">
  41                         <a href="http://defaria.com/blogs/Status/archives/000237.html">&laquo; Permissions problems</a> |
  42                         <a href="http://defaria.com/blogs/Status/">Main</a>
  43                         | <a href="http://defaria.com/blogs/Status/archives/000242.html">CLEARCASE_PRIMARY_GROUP &raquo;</a>
  44                      </p>
  45
  46                      <a id="a000239"></a>
  47                      <div class="entry" id="entry-239">
  48                         <h3 class="entry-header">Informatica/CLEARCASE_PRIMARY_GROUP</h3>
  49                         <div class="entry-content">
  50                            <div class="entry-body">
  51                               <ul>
  52
  53 <li>Rearranged Informatica script code to be more oriented to what Don needs</li>
  54
  55 <li>Helped William Dean with issues regarding Clearcase. I think we are all OK now so I closed the Paragrine ticket for this. This has, however, opened up the issue that CLEARCASE_PRIMARY_GROUP needs to be set in some cases</li>
  56
  57 </ul>
  58                            </div>
  59                            <div id="more" class="entry-more">
  60                               <p>In order to make the pushing of Rational Tools more automatic it's important to either eliminate all user specific settings or to come up with a way to determine the setting for the user at login time. As such I have been researching if the CLEARCASE_PRIMARY_GROUP needs to be set at all. In most cases it doesn't need to be. (It was thought that mkelem would make the element and that the protect trigger would -chgrp &lt;<i>vob group owner</i>&gt; of the element. But if the user does not have CLEARCASE_PRIMARY_GROUP set then they are often considered part of <i>Domain Users</i> which isn't usually on the vob's group list). However today I found out a case where it needs to be. <a href="http://www.ibm.com/support/docview.wss?rs=0&q1=CLEARCASE_PRIMARY_GROUP&uid=swg21135509&loc=en_US&cs=utf-8&cc=us&lang=en">According to What is the CLEARCASE_PRIMARY_GROUP variable used for?</a></p>
  61
  62 <blockquote>
  63   <p>If the vob is owned by <b>more than one group</b> and a user is a
  64   member of <b>more than one</b> of those groups and the user's group list
  65   does <b>not</b> exceed 32,  they need the CLEARCASE_PRIMARY_GROUP
  66   variable set in order to create elements in that vob.</p>
  67
  68   <p>If the vob is owned by <b>more than one</b> group and a user is a
  69   member of <b>more than one</b> of those groups and the user's group list
  70   <b>does</b> exceed 32, they need the CLEARCASE_PRIMARY_GROUP &
  71   CLEARCASE_GROUPS variable set in order to create elements in that vob.
  72   </p>
  73 </blockquote>
  74
  75 <p>Unfortunately this is the situation that we have. In particular Core_automation is owned by more than one group and users are members of more than one of those groups. Thus CLEARCASE_PRIMARY_GROUP needs to be set.</p>
  76
  77 <p>Also, we tend to have many groups and if we have more than 32 groups we can run into problems. Setting CLEARCASE_GROUPS helps narrow the problem down but a user can only be a member of at the maximum 33 Clearcase oriented groups or else they will need to be shifting around CLEARCASE_GROUPS in order to operate.</p>
  78
  79 <p>So what I'm proposing is that the Clearquest Tools database functionality be expanded yet again to provide for associating a userid to the appropriate CLEARCASE_PRIMARY_GROUP and appropriate CLEARCASE_GROUPS. Some of this functionality is already present in the Tools database. What it lacks is the ability to designate which of the groups is the users primary group.</p>
  80
  81 <p>There's also the issue of backfilling the Tools database and filling out the necessarily information for the users currently entered into the Tools database as well as filling the Tools database from that Access database...</p>
  82                            </div>
  83                         </div>
  84                         <p class="entry-footer">
  85                            <span class="post-footers">Posted by  on August 30, 2004  6:11 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000239.html">Permalink</a>
  86                         </p>
  87                      </div>
  88
  89
  90
  91
  92                   </div>
  93                </div>
  94             </div>
  95          </div>
  96       </div>
  97    </div>
  98 </body>
  99 </html>