Release the VOB Repair tools with ClearCase product

This RFE is requesting that the many VOB repair tools released by support be versioned and released with the product in a similar manner to how checkvob is released.
HCL support has agreed that is supported to run these repair tools before contacting support if the symptoms addressed by one of these has taken a VOB down.
It's important these tools run to correct SEV-1 situations. Known stable versions need to be available to the clients to run.
In the PMR referenced by this RFE, a SEV-1 was opened for 4.5 hours before the right combination of the repair tools was discovered by the client.

These repair tools do change and it's difficult to know if the current versions are installed. If released and installed with the product then a Cleartool lsversion would tell the client and support which versions of the utilities are installed.

There are at this time at least 8 VOB repair distributed by ClearCase Support.

PI28582_check
find_bad_activity.pl
find_bad_activity_DB.pl
find_bad_baseline_DB.pl
find_bad_timeline.pl
find_bad_timeline_DB.pl
Rebuild_timeline_DB.pl
find_bad_ucm_view_refs,pl

Usage is generally like:
cd to the vob storaged .vbs
find_bad_timeline_DB.pl -all -fix
Generally these LOCK the VOB during the run

There has been an unknown tendency for the clients to miss the "-fix -all" options during the execution of the tools.

There is confusion on what the signatures for these repair tools are. Some known are:
Error at "/vobs/atria/lib/db/db__dump.c" line 4177
can be resolved by the script:
Perl find_bad_timeline_DB.pl -all -fix

Error at "/vobs/atria/lib/db/db__dump.c" line 4055
can be resolved by the script
Perl find_bad_activity_DB.pl -all -fix


Not all signatures are as easy to detect. Usually the repair tool itself detects the signature. The question of knowing "What the signature is", becomes "Run the utility and it will look for the signature"

Errors from ClearCase release to release can change, for example:
error at "/vobs/atria/lib/db/db__dump.c" line 4177
May change to different line numbers for a new release. Which can confuse manual searching for past patterns. Other signatures may already include different line numbers.

AT times a VOB corruption may have happened years ago and sits benignly through most CC operations until a time a reformatvob, or mkreplica is needed.

For all Sev-1 and other VOB corruption situations the PMR startup time is many back and forth of the client collecting data for support. Gathering the data can be a wastes a lot of time. This data is often not used to resolved the PMR as one of the mentioned tools resolve it.