3.3 HP-UX Functionality

This section describes ClearCase functionality specific to the HP-UX 10 (hp10_pa) and HP-UX 11 (hp11_pa) platforms, with references to other places in the documentation set where more information can be obtained. This information was previously in the Release Notes.

Modifying a crontab Entry

The chapter Preventing Accidental Deletion of Data by crontab Entries in the Administrator's Guide discusses modifying crontab entries or other scripts to prevent infinite looping of scripts. In particular, the chapter discusses altering scripts using the find / command. On an HP-UX system, no crontab entry is provided by default. The following entry does not search file systems of type nfs, nor does it search the viewroot directory:

NOTE: In the example above, long lines are broken for readability. In actual crontab files, each entry must be contained on a single physical text line.

Moving a VOB

The chapter on VOB maintenance in the Administrator's Guide describes how to move a VOB to another host. When moving a VOB, whether or not the hosts have different architectures, one required step is to copy the VOB storage directory. For most architectures, we recommend using the command tar -xBpf - as part of the command line. However, the -B option to tar is not supported on HP-UX hosts. Instead of the command lines given in the chapter, use these:

• On the same host to a different disk partition:

# tar -cf - libpub.vbs | ( cd /src_2/vobstore ; tar -xpf - )

• On a different host with the same architecture:

# tar -cf - libpub.vbs | remsh ccsvr04 'cd /src_2/vobstore ; tar -xpf -'

• On a different host with a different architecture:

# tar -cf - libpub.vbs | remsh ccsvr04 'cd /src_2/vobstore ; tar -xpf -'

Moving a View

The chapter on VOB maintenance in the Administrator's Guide describes how to move a view from one host to another. Moving a view also requires using a tar command to move the storage directory. On an HP-UX system, which does not support the -B option to tar, substitute the following commands for the commands in the chapter:

• On the same host:

% tar -cf - gomez.vws | (cd /public; tar -xpf -)

• On a different host with the same architecture:

% tar -cf - gomez.vws | remsh ccsvr04 'cd /public; tar -xpf -'

• On a different host with a different architecture:

# tar -cf - gomez.vws | remsh ccsvr04 'cd /public; tar -xpf -'

Manipulating the Block Buffer Cache

The functioning of the block buffer cache has a significant effect on VOB host performance; for more information, see the chapter on VOB performance in the Administrator's Guide.

HP-UX provides the glance tool for monitoring buffer cache performance. It also provides user-level control over the frequency of flushing the cache to disk through the syncer(1M) utility.

Increasing the MVFS Cache Size

In its chapters on performance tuning, the Administrator's Guide discusses changes you can make to improve performance of ClearCase clients. Use the information in this section in conjunction with that material.

The instructions that follow increase the size of the MVFS cache, in such a way that the changes are persistent.

Setting Individual Cache Sizes on HP-UX 10.x and HP-UX 11.x

On each ClearCase client:

1. Become the root user.

2. Change to the directory /usr/conf/mvfs.

3. Edit mvfs_param.c and set the MVFS configuration parameters.

4. Rebuild the MVFS parameters. (This command builds mvfs_param.c and adds the newly rebuilt mvfs_param.o file to /usr/conf/libusrdrv.a.)

# make -f mvfs_param.mk regen

5. Save the old kernel; then rebuild and install a new one:

# cd /stand/build
# mv /stand/vmunix /stand/vmunix.prev
# /usr/sbin/mk_kernel -o /stand/vmunix

NOTE: Without the -o option, mk_kernel leaves the kernel in the spot named by the config.mk file, by default /stand/build/vmunix_test. If you build that way, do the following:

# mv vmunix_test /stand/vmunix

6. Reboot the system:

# /etc/shutdown

Optionally, Change All Clients Before Installing ClearCase on HP-UX 10.x and HP-UX 11.x

If you want to make these changes on all your clients before you install this release of ClearCase, you can edit the configuration files in the ClearCase release area. If you do this, you can avoid an extra reboot of each client host. The ClearCase installation process from the release area to the client host will include the customized parameters when it rebuilds the system kernel.

1. Become the root user.

2. Change to the ClearCase release area directory.

3. Edit hp10_pa/usr/conf/mvfs/mvfs_param.c or hp11_pa/usr/conf/mvfs/mvfs_param.c (matching the system type you are installing). Set the MVFS configuration parameters as described in the chapter Improving Client Host Performance in the Administrator's Guide.

4. Install ClearCase from the release area onto the client hosts.

Enable Transitional Links on HP-UX 10.x and HP-UX 11.x

ClearCase relies on transitional links supplied by Hewlett-Packard to handle the relocation of operating system components between HP-UX 9.x and HP-UX 10.x/11.x. HP-UX 10.x and HP-UX 11.x systems must be installed with transitional links enabled. These links are enabled by selecting the UPG-TLINK fileset on installation.

SoftBench Installation and Configuration

Because of changes to SoftBench in version 6.x, it is no longer possible to create a ClearCase menu item on the SoftBench Development Manager file browser. Setting up the ClearCase/SoftBench integration, as described in the online help under the topic of third-party integration, enables you to use ClearCase as the Configuration Manager for your SoftBench files. However, it does not rename the Configuration Manager menu item to ClearCase on the SoftBench file browser as it did with SoftBench 4 or 5, and it does not add ClearCase functionality to that ClearCase menu.

For information about installing and configuring SoftBench to work with ClearCase on HP-UX computers, see the online information on ClearCase integrations with third-party products.