ViewPoint Manual

Installation, Configuration, and Startup
ViewPoint Manual—426801-001
7-16
Running ViewPoint
In addition, anyone starting up ViewPoint must have read or write access to the collector
process $0 (or any EMS Alternate Collector which might be configured) and must have
read access to PATHDEFS, PATHCONF, and PATHSTRT. Security settings in
PATHDEFS and PATHCONF should be checked and changed, if necessary, so that they
reflect the person starting up ViewPoint. You can change these security settings by
running the Install routine and changing the values for the following security options:
Pathway-OWNER, Pathway-SECURITY, and PROGRAM-SECURITY. (Remember to
specify the CONFIGURE option when you first run Install, so that the program changes
these option values without also installing new program and data files.)
Pathway-SECURITY should be restricted to the user or group who administers the
NonStop™ TS/MP system and must include the user who starts the ViewPoint Pathway
system. By default, after installation, it is set to “C” for network community group
member.
The user who starts up the ViewPoint applications can also alter the Pathway aspects of
the ViewPoint configuration (such as adding, starting, or stopping servers and terminals)
while ViewPoint is running. This is done using PATHCOM or the Subsystem
Programmatic Interface (SPI) in a Pathway management application.
Running ViewPoint
To run ViewPoint, a user must have write access to the TERMTACL file, which is
located on $volume.data-subvolume and must have read access to the system
TEMPLATE file located on $SYSTEM.SYSnn (where nn is a 2-digit octal number.
The OSIMAGE and many other operating system files reside in this subvolume).
PROGRAM-SECURITY should be set to the user or group who will be running
ViewPoint. By default, after installation, it is set to “N” for anyone on the network.
Additionally, anyone planning to run ViewPoint must have read access to an
initialization file VPTCSTM (if it exists) in the ViewPoint data subvolume. This file is
optional; it consists of a user-written macro that is executed before the ViewPoint
application is entered. This macro can implement further security checks. Safeguard
can be used to secure this file; you can thus implement requirements for access list-type
authorization to ViewPoint.
Users attempting to run the ViewPoint application without proper Pathway program
security authorization, see an error message similar to the following:
Pathway error 1090 returned from $zvpt.
PATHMON ERROR - *1090* SECURITY VIOLATION
Initialization failed.
Exiting from ViewPoint.
Users attempting to run the ViewPoint application without proper authorization to the
VPTCSTM file see an error message similar to the following:
VIEWPT
\CITY.$DISCZ.VPTANNA.vptcstm
Note. If the ViewPoint Pathway system is started by a user with the SUPER.SUPER ID,
Pathway
-SECURITY should be set to “U” or “O”.