Virtual Hometerm Subsystem (VHS) Manual (H06.03+)

Installing VHS
Virtual Hometerm Subsystem (VHS) Manual—429311-001
2-5
Installing VHS for the First Time
•
Program and configuration files for the VHS and VHSCI programs and the VHS
GUI Agent facility
•
Program and configuration files for the VHS Browser facility
•
HELP text files
•
VHS Browser Pathway configuration files
The INSTVHS routine presents four options to help you install and update the VHS
components. The four options are:
1. Install or update VHS and VHSCI programs and the VHS GUI Agent facility
2. Install or update the VHS Browser facility in a running ViewPoint Pathway system
3. Install the VHS Browser facility as a stand-alone Pathway system
4. Update the VHS Browser facility in a stand-alone Pathway system
After you install the VHS and VHSCI programs and the VHS GUI Agent facility by
choosing option 1, determine how you want to install the VHS Browser facility and then
select the appropriate option (2, 3, or 4). If you wish to install the VHS GUI, refer to
Section 8, The VHS GUI, and to the Softdoc.
Installing VHS for the First Time
INSTVHS follows certain general guidelines when installing VHS for the first time:
•
VHS files—such as the VHS programs, help text, and configuration files—are
owned by the user running the installation routine; their security attributes are set
to NUNU.
•
VHS Pathway files are owned by the user running the installation routine; their
security attributes are set to the current default security values.
Updating VHS
INSTVHS follows certain general guidelines when installing a VHS software update:
•
Files released by Tandem replace older versions.
•
Files containing user data (such as VHSCSTM, VHSBCONF, and VHSGCONF)
are not replaced.
•
If the installation replaces an old copy of a VHS file, such as the VHS program or
HELP text file, the new file has the owner and security attributes of the old file.
•
If the installation replaces an old copy of an VHS configuration file, the new file has
the owner and the security attributes of the user running the installation routine.
•
If the installation creates a new file, the new file is owned by the user running the
installation routine; its security attributes are set to the current default security
values.