TACL Reference Manual

The TACL Environment
HP NonStop TACL Reference Manual—429513-018
6-10
Using Directories
TACL sends these types of messages to $CMON:
•
A CMON configuration message, which establishes the TACL configuration for the
new process or user.
•
A pre-LOGON message, which allows $CMON to invoke additional security
provisions (for example, requiring a user to log on under one ID before being able
to log on under some other ID).
If the $CMON process is not running, TACL uses stored defaults.
For a description of the communication between TACL and a command interpreter
monitor process, see the Guardian Programmer’s Guide.
Using Directories
TACL organizes its variables according to purpose or product; it keeps your variables
separate from TACLBASE variables (commands) and helper variables that are used by
the TACLBASE variables and are not intended for direct use. This organization called
a directory, and is hierarchical, similar to a tree. The root of the tree is the :directory.
Directories organize variables in a hierarchy and take advantage of operating system
features that support segment files.
A Sample Directory Structure
Figure 6-1 on page 6-11 demonstrates the structure of variables and segment files in a
running TACL process. ZAP is an example of an application product (that are part of a
software RVU); each application product that releases TACL programs has a directory
equivalent to those shown for ZAP. Any segment file that you create would be attached
among the user-vars.