jobs currently issue an unfiltered cleartool lsview when kicked off. This can take some time in an environment where a large number of views exist.

I see two possible solutions
1. allow users to optionally specify a pattern to filter the search

cleartool lsview <pattern>

2. use the job's view name as a parameter

cleartool lsview <viewname>

In either case, it appears that the following error would need to be handled.

cleartool: Error: No matching entries found for view tag "<pattern|viewname>"