IBM Support

PI89037: CADENCE/CLEARCASE: TRIGGER CONTEXT UNCLEAR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • It is a problem implementing certain restriction on mkelem in
    OpenAccess libraries, in contrast to restricting
    checkout/checkin in the Rational ClearCase/Cadence integration
    
    The problem is that during the initial checkin of a previously
    unmanaged cellview, the sequence of steps include:
    * checkout of parent directory
    * mkelem of the file element (e.g.: sch.oa)
    * checkout of the file element
    * checkin of the file element
    * checkin of the parent directory
    
    All these events cause the corresponding pre-operation trigger
    to fire. The environment then contains the CLEARCASE_* variables
    that show the details of the action. However, it seems
    impossible to distinguish for checkout and checkin, whether that
    was a standalone action (= user
    clicked on Checkout/Checkin in Library Manager), or it was
    triggered as part of the initial checkin (mkelem) procedure (=
    user clicked on Checkin for an unmanaged cellview).
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of the ClearCase / Cadence integration and ClearCase   *
    * triggers.                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * ClearCase trigger context isn't always clear.  The mkelem    *
    * command from the integration has no parent-op for check-in   *
    * that happens during that                                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • A fix is available in ClearCase version 9.0.1.6
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI89037

  • Reported component name

    CLEARCASE WIN

  • Reported component ID

    5724G2900

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-18

  • Closed date

    2019-03-22

  • Last modified date

    2019-03-22

  • 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

  • R801 PSN

       UP

  • R900 PSN

       UP

  • R901 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"801"}]

Document Information

Modified date:
17 June 2021