ViewPoint Manual

Installation, Configuration, and Startup
ViewPoint Manual—426801-001
7-14
Restrictions When TACL is Not Present
terminal where you want ViewPoint to run, the Pathway configuration might include the
following PATHCOM commands:
SET TERM INITIAL ZVPT-MAIN
SET TERM TCP ZVPT-TCP
SET TERM FILE network-file-name-of-terminal
SET TERM AUTORESTART 5 <--or whatever value is appropriate
SET TERM BREAK ON <--if the BREAK key is to be disabled
SET TERM TYPE T16-6530:0
SET TERM PRINTER print-device-name
SET TERM MAXINPUTMSGS 1
ADD TERM logical-terminal-name <--Pathway name of terminal
START TERM logical-terminal-name
The following commands terminate a ViewPoint application running on a dedicated
ViewPoint terminal:
STOP TERM terminal-name
DELETE TERM terminal-name
Refer to the NonStop™ TS/MP System Management Reference Guide for detailed
information about these commands.
When ViewPoint is not initiated from TACL, the ViewPoint data subvolume is used as
the operator logon subvolume to find the EVNTDFLT and STATDFLT files. If default
files ZZVPEVNT and ZZVPSTAT exist, they are on the PATHMON user ID default
logon subvolume; these files are always used in preference to the EVNTDFLT and
STATDFLT files when they exist.
Restrictions When TACL is Not Present
Certain restrictions apply when TACL is not present and integrated with ViewPoint:
•
Subsystem commands cannot be issued from within ViewPoint.
•
Although the Clip function key can be used to add lines to the Clipboard, its
contents are not available from ViewPoint screens.
•
File I/O for clipping and printing is performed using the PATHMON user ID instead
of the current user ID.
•
Screens cannot be printed to a disk file, only to a terminal, process, or printer (this is
a Pathway restriction).
•
Pressing the TACL function key causes an error message to be displayed.
•
The COLOR option is unavailable because TACL provides the color map.
•
VPTCSTM is not invoked and cannot be used as a security mechanism.
Security Considerations
ViewPoint implements no new security checking but relies on the checking already
provided by the subsystems it uses. Users who install ViewPoint must assign security
values to achieve the desired protection.