Home/ Questions/Q 9271369
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-18T15:36:14+00:00

I am trying to understand how long ClearCase operations take after performing the add

  • 0

I am trying to understand how long ClearCase operations take after performing the add to source control operations.

If I am working through a CCRC snapshot view and I add a file to source control, how long will it take for the changeset to be updated with the new line, and how long until the operation completes will the new file be available under a dynamic view pointing to the stream that the file was checked into?

Is there any way to speed up that process by invoking a manual update of the dynamic view or something?

Regards,

Andrew

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    how long will it take for the changeset to be updated with the new line

    As soon as you checkout a file, selecting an activity, it will update the chenge set of said activity immediately.

    A dynamic view would reflect that file only after you check in (through your web snapshot view in CCRC), and that update would also be near instantaneous.
    To speed up, you can refresh the dynamic view, or do a cleartool ls in the directory you want to see updated.

    In each case, when you are doing a checkout or a checkin through CCRC, you are posting an http request to the CCRC server which in turn complete the operation with the ClearCase Vob/View server.
    So once the checkout/checkin is completed, any other ClearCase view (CCRC or not) would be ready to reflect the changes.
    The only part which takes time is the communication between the CCRC client and the CCRC server. That server being usually on the same LAN as the ClearCase server, the ClearCase command itself executes fairly quickly.

    “fairly quickly” turned out too slow for the OP’s need: a postop trigger on checkin.

    That trigger use a ClearCase dynamic view on the server side, and has to introduce a sleep on the element checkin (on mkelem) in order for the second call of that trigger (on the parent directory being checked in) to properly detect the new created file.

    • 0