view_scrubber

When a clearmake or omake build winks in a shareable DO for the first time, the DO's data container is copied from the private storage area of the view in which it was built to the VOB storage pool. At this point:

• The view where the DO was originally built continues to use the data container in view storage.
• Any other view to which the DO is subsequently winked in uses the data container in VOB storage.

Running view_scrubber in the view where the DO was built simplifies the situation. view_scrubber performs the following steps:

1. Removes the DO with an operating system command. This deletes the data container from view storage.
2. Winks in the DO to the view, which establishes a link to the data container in VOB storage.

Now, all views that share the DO access the data container in VOB storage, which eliminates the redundant, space-consuming data container in view storage.

By default, the data container for a nonshareable DO or an unshared DO remains in view storage until the DO is deleted or overwritten. view_scrubber –p transfers the data container to VOB storage, thus freeing space in the view storage area. In essence, this involves winking in the DO to the same view. view_scrubber –p performs the following steps:

1. (Nonshareable DO only) Converts the DO to a shareable DO by writing information about the DO into the VOB.

   If the DO has any sub-DOs or siblings, view_scrubber –p or view_scrubber –a makes them shareable. view_scrubber –a stops after this step is complete. view_scrubber –p executes the following additional steps:

2. Promotes the data container from view storage to VOB storage.
3. Removes the DO with an operating system command, which deletes the data container from view storage.
4. Winks in the DO to the view, which establishes a link to the data container in VOB storage.

You can also use the winkin command to accomplish this scenario.

Default

view_scrubber removes view-resident data containers, then restores the derived objects to the view through winkin. Requirement: The derived objects' data containers must already be in VOB storage.

–a

Before performing the default processing described above, writes information about the DO to the VOB to advertise its availability for winkin, but does not copy the DO to the VOB.

–p

Before performing the default processing described earlier, writes information about the DO to the VOB to advertise its availability for winkin, then promotes (copies) the derived objects' data containers from view storage to VOB storage. This removes the requirement that the data containers be in VOB storage. (view_scrubber –p implies execution of view_scrubber –a.)

Default

view_scrubber aborts if it is unable to complete its work on any derived object.

–k

Keeps going, even if one or more derived objects cannot be processed successfully.

Default

view_scrubber performs its work and displays appropriate messages.

–n

Suppresses the actual processing of data containers. view_scrubber displays messages describing the work it would have performed.

Default

If you do not specify any DOs as command arguments, view_scrubber reads a one-per-line list of pathnames from stdin, which must be a pipe.

DO-pname ...

One or more standard pathnames of derived objects.