IBM Support

PM48088: Post-op triggers on rebase_complete fail to populate some ClearCase environment variables

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When attempting to capture IBM Rational ClearCase environment
    variables in a rebase_complete post-op trigger, the following
    variables fail to populate: CLEARCASE_MTYPE, CLEARCASE_PPID,
    CLEARCASE_USER, CLEARCASE_VOB_PN, CLEARCASE_XN_SFX.
    
    This only occurs if both of the following conditions are true:
    
    A) The view being rebased to is already set to an activity prior
    to performing the rebase.
    
    AND
    
    B) There is also a trigger on the setactivity operation.
    
    
    Steps to reproduce the issue:
    
    1) Create a IBM Rational ClearCase Unified Change Management
    (UCM) Project with one integration stream and one development
    stream.
    
    2) From a Microsoft Windows command prompt, navigate to the
    integration view and CD into the pvob.
    
    3) Create a setactivity post-op trigger, similar to the
    following:
    
    cleartool mktrtype -nc -all -ucm -postop setactivity -exec
    'ccperl -e print('setact-trigger-fired')' setactTR
    
    4) Create a rebase_complete post-op trigger, similar to the
    following:
    
    cleartool mktrtype -nc -all -ucm -postop rebase_complete -exec
    'ccperl -e system(set)' rebaseTR
    
    5) Add a file to source control on the integration stream,
    create a new baseline, and rebase the change to the development
    stream.
    
    6) Navigate into the development stream.
    
    7) Create and set to an activity on the development stream.
    
    8) Perform a 'cleartool rebase -recommended -complete'.
    
    9) Observe the five environment variables referenced above are
    not present.
    
    10) Repeat steps 5-8, substituting 'cleartool setact -none' for
    step 7.
    
    11) Observe the five environment variables referenced above are
    present.
    
    
    WORKAROUND:
    
    - Use 'cleartool setact -none' prior to rebasing to ensure the
    environment variables will populate.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When attempting to capture IBM Rational ClearCase
    environment variables in a rebase_complete post-op trigger,
    the following variables fail to populate: CLEARCASE_MTYPE,
    CLEARCASE_PPID, CLEARCASE_USER, CLEARCASE_VOB_PN,
    CLEARCASE_XN_SFX.
    
    This only occurs if both of the following conditions are
    true:
    
    A) The view being rebased to is already set to an activity
    prior to performing the rebase.
    
    AND
    
    B) There is also a trigger on the setactivity operation.
    
    
    Steps to reproduce the issue:
    
    1) Create a IBM Rational ClearCase Unified Change Management
    (UCM) Project with one integration stream and one
    development stream.
    
    2) From a Microsoft Windows command prompt, navigate to the
    integration view and CD into the pvob.
    
    3) Create a setactivity post-op trigger, similar to the
    following:
    
    cleartool mktrtype -nc -all -ucm -postop setactivity -exec
    "ccperl -e print('setact-trigger-fired')" setactTR
    
    4) Create a rebase_complete post-op trigger, similar to the
    following:
    
    cleartool mktrtype -nc -all -ucm -postop rebase_complete
    -exec "ccperl -e system(set)" rebaseTR
    
    5) Add a file to source control on the integration stream,
    create a new baseline, and rebase the change to the
    development stream.
    
    6) Navigate into the development stream.
    
    7) Create and set to an activity on the development stream.
    
    8) Perform a "cleartool rebase -recommended -complete".
    
    9) Observe the five environment variables referenced above
    are not present.
    
    10) Repeat steps 5-8, substituting "cleartool setact -none"
    for step 7.
    
    11) Observe the five environment variables referenced above
    are present.
    
    
    WORKAROUND:
    
    - Use "cleartool setact -none" prior to rebasing to ensure
    the environment variables will populate.
    

Problem conclusion

  • A fix is available in ClearCase versions 7.1.1.8, 7.1.2.5
    and 8.0.0.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM48088

  • Reported component name

    CLEARCASE WIN

  • Reported component ID

    5724G2900

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-09-16

  • Closed date

    2011-12-16

  • Last modified date

    2011-12-16

  • 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

  • R710 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":"7.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
16 December 2011