TACL Reference Manual

The TACL Environment
HP NonStop TACL Reference Manual—429513-018
6-11
Creating Your Own Directories
Creating Your Own Directories
You can create your own directories of variables. For more information, see Section 4,
Variables. For information about creating and attaching segment files, see Section 5,
Statements and Programs.
Directories Supplied by TACL
The UTILS directory exists in the root and contains directories for all application
products (that are part of a software RVU) on your system that use TACL, referenced
as :UTILS: product. If a product includes or consists of subproducts, each subproduct
can be considered a product in its own right and be given its own directory in :UTILS.
The :UTILS:TACL directory contains all the TACL commands, including command-
interpreter commands and additional commands, programs, and functions used by
TACL. For example, the :UTILS:TACL variable VOLUME refers to the command
named VOLUME that is executable by the TACL program.
There are also some primitive functions in :UTILS:TACL. The name of each of these
functions begins with an underscore (_), and each returns a value. Primitive functions
differ from commands, which primarily perform actions, in that the returned value, not
the action, is the primary result.
Other products that are part of the same software RVU use another directory in the
root, UTILS_GLOBALS, if they include TACL programs and need to maintain writable
global TACL variables. This use of directories achieves the following:
•
Minimizes the potential for naming conflicts among variables from various sources
Figure 6-1. TACL Segment File and Directory Relationships
Root
UTILS_GLOBALS UTILSuser-variables
ZAP TACL
zap-globals tacl-globals
ZAP TACL
zap-commands
tacl-commands
... ...
TACLSEGF Segment File
Shared/Read-Only
Shared by all TACL Processes
Private Segment File
Private/Read-Write
One per TACL Process
VST001.vsd