Status for Andrew DeFaria

• Had a problem with Clearquest, something about m_pPerl != 0. Got it when trying to create a UCM project. Traced that down to not being able to create the UCM Project in Clearquest. Then I couldn't even complete a Clearquest activity! I was able to do so over on Omair's machine so we suspected my install was somehow corrupted. Ended up uninstalling and reinstalling Clearquest
• Created new UCM Project for Nancy

Posted by at 6:41 PM | Permalink | TrackBacks (0)

• Met with Jodi, Lyle, etc. Decided to go with the proposed solution of making BF jobs to do the deliveries as Lyle or designate. Sent him instructions on how to set up the BF part. Unco should be simple.
• Worked with Sherri to get her going with starting a view. They seem to have been told to go through Eclipse to start the view and mount the vob. Odd.

Posted by at 3:28 PM | Permalink | TrackBacks (0)

• Created 3 UCM Projects/streams - one including an Import Project component
• Investigated what causes users to be considered Clearcase Admins

A question was asked about what causes users to be considered Clearcase admins:

From About ClearCase permissions on Windows:

ClearCase Administrative Access

Privileged users in ClearCase have rights to create, modify, and delete any ClearCase object. Access to these permissions should be restricted to ClearCase Administrators and the ClearCase Process Account (Atria Location Broker Service - ALBD). Access is controlled by membership in the ClearCase Administrators group.

This group which is designated during the setup and installation of ClearCase is referred to as the ClearCase privileged group. By default, this group is called clearcase. Some defining characteristics of the ClearCase (or privileged) group are:

• The account under which whose identity Atria Location Broker Daemon (ALBD) runs has to be a member of this group, such as clearcase_albd.
  
• This group has Full Control of the view and VOB storage directories.
  
• Members of this group are considered ClearCase Administrators.

Note: The ClearCase privileged group must never be used as the primary group on a VOB or set as a primary group for ClearCase access.

The ClearCase administrator is the most powerful user having full control of a site installation. On Unix, this would be the superuser, UID=0, on the VOB server. On Windows, it is any user who is a member of the clearcase domain group.

Posted by at 4:34 PM | Permalink | TrackBacks (0)

Need to keep status if even to remind myself what I'm doing.

• Fixed case #9225676 for Kemyss about evil twins - turns out there was no twin
• Closed case #9214530 regarding evil twins for Curtis
• Attended meeting about MQC
• Submitted ticket to get a MQC account
• Weekly high level status meeting with Dave and Rob. Focusing on SDDLS & Uncheckout problem
• Solved another evil twin case with Marlene
• Submitted helpdesk ticket to get Anthony added to the proper NIS group. They can have a Unix account but not be given access to Unix itself. So, ypmatch <username> passwd will show them but id will not. This is because they are not in the users_seattle_clearcase_users NIS netgroup so thus they are not considered a user on this Unix system. Still have yet to figure out how they do Samba here...

Posted by at 5:47 PM | Permalink | TrackBacks (0)