IBM Support

PM80693: Posted deliver fails to push stream mastership unless done by stream owner or privileged user.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In UCM Mastership, delivering from one stream to a target stream
    mastered in a different replica
     starts a 'posted' delivery which transfers mastership of the
    source stream to the same replica
     that masters the target stream.
    In Clearase 8.0 with Feature Level 7 this mastership change gets
    blocked for all but
      * stream owner (source stream)
      * VOB owner    (UCM project VOB)
      * ClearCase Admin / root
    
    Steps to reproduce:
    1. Site1 has ClearCase 7.1.2 with users vobadm01 and user01,
    both of which have ccusers01 as their primary group
    
    2. Site2 has ClearCase 7.1.2 with users vobadm02 and user02,
    both of which have ccusers02 as their primary group
    
    3. At Site1:
       a. vobadm01 creates a Project VOB, a multi-component VOB with
    component Comp01 in it, UCM Project Project01 and integration
    stream Project01_Int
       b. vobadm01 creates replica creation projects for both vobs
    and ships them to Site2
    
    4. At Site2:
       a. vobadm02 imports the replica creation packets to create
    the Project VOB and Component VOB replicas
       b. vobadm02 creates Dev stream Project01_Dev
       c. user02 add files to source control and later modifies them
    using a view attached to Project01_Dev
       d. user02 initiates a posted deliver: cleartool deliver
    -stream stream:Project01_Dev@\PVOB -target
    stream:Project01_Int@\PVOB
       e. vobadm02 generates and sends sync packets to Site1
    
    5. At Site1:
       a. vobadm01 imports the sync packets
       b. the posted deliver is completed
       c. vobadm01 generates and send sync packets back to Site2 (to
    inform them the posted deliver is completed and changed
    mastership of stream back to PVOB replica at site2)
    
    6. vobadm01 changes mastership of the Site2 replicas to
    themselves to they're self-mastering; generates and sends sync
    packets to Site2; vobadm02 imports the sync packets at Site2.
    
    7.  At both sites:
       a. reformat both VOBs to raise their schema levels to 80
       b. raise the feature levels of all replicas to 7
       c. Generate and send sync packets to the other site
       d. Import the packets sent (now all replica are seen as being
    at FL7 from both sites)
    
    8. At Site1, raise the vob family feature level of both VOBs to
    7; generate and send sync packets to Site2; and and Site2,
    import the sync packets
    
    9. At Site2:
       a. user2 further modifies the existing files using the same
    view and stream (but using new activities)
       b. user2 initiates a posted deliver: cleartool deliver
    -stream stream:Project01_Dev@\PVOB -target
    stream:Project01_Int@\PVOB
    Error message:
    Changes will be POSTED to default target stream in project
    'Projec01':
              FROM: stream 'Project01_Dev'
              TO: stream 'Project01_Int'
    Activities included in this operation:
            activity:mod_f2_01@\PVOB        user02  'mod_f2_01'
            activity:mod_f1_02@\PVOB        user02  'mod_f1_02'
    Do you wish to continue with this deliver operation?  [no] y
    cleartool: Error: No permission to perform operation 'change
    master'.
    cleartool: Error: Must be one of: object owner, VOB owner,
    member of ClearCase group
    cleartool: Error: Unable to post stream 'Project01_Dev' to the
    target stream's replica.
    
    Workaround:
    Delegate the deliver operation to the owner of the UCM Project
    VOB.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In UCM Mastership, delivering from one stream to a target
    stream mastered in a different replica starts a "posted"
    delivery which transfers mastership of the source stream to
    the same replica that masters the target stream.  In
    Clearase 8.0 with Feature Level 7 this mastership change
    gets blocked for all but
      * stream owner (source stream)
      * VOB owner  (UCM project VOB)
      * ClearCase Admin / root
    

Problem conclusion

  • A fix is available in ClearCase version 8.0.0.6
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM80693

  • Reported component name

    CLEARCASE WIN

  • Reported component ID

    5724G2900

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-15

  • Closed date

    2013-03-20

  • Last modified date

    2013-03-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    CLEARCASE WIN

  • Fixed component ID

    5724G2900

Applicable component levels

  • R800 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
20 March 2013