TACL Reference Manual

The TACL Environment
HP NonStop TACL Reference Manual—429513-018
6-4
TACL Initialization
contains any commands you supply, can include a request to load all your personal
command definitions.
TACL passes one argument to TACLCSTM, indicating whether the loading of
TACLBASE was suppressed because you are the most recent user to log off from this
TACL and are now logging back on. (The same segment is still in effect.) The
argument is nonzero if loading was suppressed, and zero if it occurred.
The TACLLOCL of the installation or your individual TACLCSTM can also create
directories for additional segment files.
CPRULES0 and CPRULES1 define the character set in use by TACL. CPRULES0 is
the default set. When starting a TACL process, if #CHARACTERRULES is empty after
TACLLOCL has been invoked, the TACL process looks for CPRULES0. TACL
searches for CPRULES0 in $SYSTEM.SYSTEM. If CPRULES is not found there, then
TACL searches the same volume and subvolume in which the TACL program file
resides (usually, $SYSTEM.SYSnn). If a CPRULES file does not exist when a user
logs on and the TACL process tries to access a CPRULES file, the TACL process
issues a warning that it is using its own set of rules (that are encoded in the TACL
program file).
TACL sets the initial terminal state to:
•
ECHO on
•
Single spacing
•
Post spacing
•
Conversational mode
After your TACL process completes initialization and you log on, you can:
•
Issue TACL commands or other statements (supplied in :UTILS:TACL and stored
in the TACLBASE file) by typing the command
•
Store TACL programs in files and invoke the programs when needed, in one of
three ways:
°
Store a text, macro, or routine variable in its own file and invoke it by file name
°
Store one or more programmatic variables in a library file and issue a LOAD
command or #LOAD call to make the variables accessible to TACL
°
Save one or more programmatic variables in a segment file and issue an
ATTACHSEG command to bring the functions into memory
For more information about these procedures, see Section 5, Statements and
Programs.
Note. If a backup TACL process takes over at a later time, TACL initializes the terminal state
to the preceding values unless the TACL process has a descendent process that continued to
run during the processor switch. In this case, TACL does not initialize the terminal state values.