TACL Reference Manual

The TACL Environment
HP NonStop TACL Reference Manual—429513-018
6-7
Customizing the TACL Environment
To check the setting of the #HIGHPIN variable from an interactive terminal, type
SHOW HIGHPIN. To check the setting of the BINDER HIGHPIN option for an object
file (type 100 or 700), enter:
BIND; SHOW SET * FROM file-name
For additional information about the BINDER HIGHPIN option, see the Binder Manual.
Customizing the TACL Environment
TACL supports two types of customization:
•
Personal customization for one user, through the use of the TACLCSTM file
•
Local customization, through use of the TACLLOCL file
Customization affects all uses of TACL, not just interactive TACL sessions started from
TELNET or SSH. Customization of TACLCSTM and TACLLOCL must allow server
programs to start TACL processes without interference.
Standard server programs using background TACL processes do not tolerate
interactive queries when TACL starts. Arbitrary redefinition of standard TACL
commands or environment might also cause difficulties.
Examples of products that start background TACL processes include some HP OSM
program files, NonStop Essentials, and the SeeView Server Gateway. These products
start TACL processes either on behalf of a command from a human-computer interface
or for unattended background activities.
Customization of a particular user ID’s TACLCSTM for security auditing might require
special care. A TACLCSTM file for a particular user can check the ancestor process of
the TACL process for special exceptions. For an example of this customization for a
particular user in the SUPER group, see the OSM Configuration Guide.
Personal Customization
To customize your TACL environment, you can add the following to your TACLCSTM
file:
•
Function-key definitions, command aliases, macros, or routines in edit-format files.
•
LOAD commands or #LOAD functions to load files into variables in your home
directory (the root directory, by default). When TACL invokes the TACLCSTM file
as you log on, it loads the files.
•
ATTACHSEG and USE commands to gain access to a segment file. Segment files
are described in Section 5, Statements and Programs
.
•
Commands such as TIME or SETPROMPT, or your own programs, to be invoked
when you log on.
TACLCSTM can also change your saved defaults by assigning volume and subvolume
names to the variable :UTILS_GLOBALS:TACL:_DEFAULTS_INITIAL.