TACL Reference Manual

The TACL Environment
HP NonStop TACL Reference Manual—429513-018
6-8
Local Customization
Local Customization
The TACLLOCL file provides a mechanism for environment customization for all users
on a given system (you might think of TACLLOCL as the system manager’s version of
TACLCSTM). This example shows a sample TACLLOCL file:
?TACL MACRO
== TACLLOCL sets up variables, macros needed for operations
RUN $system.system.opertool == defines _oper^tools variables
[#IF %1% |THEN|
== A fast logon
|ELSE|
== A slow logon
SINK [#LOAD /KEEP 1/ [_oper^tools].macrolib]
]
In the preceding example, the dummy argument %1% refers to an argument provided
by TACL when you log on; you can use this same construct in your TACLCSTM file.
The argument is true (a nonzero value) if the default segment file containing TACL
variables exists, false (zero) if TACL created a new segment file when you logged on.
If the segment file exists, loading library files is unnecessary.
Managing the BREAK Key
When you first log on, TACL initializes #BREAKMODE to POSTPONE (see
#BREAKMODE Built-In Variable on page 9-36). The standard TACL logon support sets
#BREAKMODE to ENABLE just before invoking your TACLCSTM. This prevents you
from breaking out of operations needed to configure your TACL when you log on, yet
allows you to break out of TACLCSTM if it becomes necessary.
Thereafter, you can set #BREAKMODE to enable, disable, or postpone the action of
the BREAK key as needed to ensure that any given sequence of TACL statements can
be free of interruption. This feature should be used with caution, however, because it
removes user control of the BREAK key. If you use a TACL with a customized version
of TACLINIT or TACLSEGF, you must ensure that #BREAKMODE is set to ENABLE at
some point during initialization if you want users to be able to use the BREAK key to
interrupt TACL processing.
Security
There exists a potential breach of security if other TACL users open your TACL
process. To limit access to your TACL process, use the #TACLSECURITY built-in
variable, described in #TACLSECURITY Built-In Variable
on page 9-402.