TACL Reference Manual

Built-In Functions and Variables
HP NonStop TACL Reference Manual—429513-018
9-353
#SETCONFIGURATION Built-In Function
Considerations
•
If TACL cannot open or read the tacl-image-file or if it is not a TACL image,
an error message results.
•
A TACL image must be supplied for the #SETCONFIGURATION built-in function to
configure the TACL. If the TACL image name is omitted, TACL will configure itself
and the new configuration values are used for later operations that require these
configuration values.
•
TACL checks the specified image to ensure that it is a TACL image by examining
the version procedure data space within the specified TACL image.
•
Only user ID 255, 255 is allowed to modify the TACL configuration. If the user ID is
not 255, 255, the #SETCONFIGURATION built-in function returns -1.
•
If any option is not configurable, #SETCONFIGURATION terminates and leaves
the image unmodified. This can occur with older TACL images.
•
TACL configures only the specified option. Any options not specified remain
unchanged.
•
When starting a new TACL process, calls to the built-in function
#SETCONFIGURATION from $SYSTEM.SYSTEM.TACLLOCL or TACLLOCL in
the cold-loaded system, volume, and subvolume are executed regardless of the
user ID. Placement of this built-in function and securing these TACLLOCL files is
set by user ID 255, 255.
•
If you specify the same option more than once, the last specification is the one
used.
•
The built-in variable #ERRORNUMBERS is set when an error occurs while
executing the #SETCONFIGURATION.built-in function.
•
If directly connected (no Safeguard or modem port control processes) to a
NonStop system by starting a TACL process on a port (for example, a dial-in line
or X.25 connection), the TACL being started on the port should be started with the
PORTTACL startup parameter. TACL processes on all nodes that are accessible
from the port should also have the TACL configuration parameter
STOPONFEMODEMERR set to ON. This setting prevents a security breach
situation caused by the error 140 (FEMODEMERR) processing by TACL. If all
nodes do not have the TACL configuration parameter STOPONFEMODEMERR
set to ON, the security breach situation still exists.
The PORTTACL startup parameter and the STOPONFEMODEMERR TACL
configuration parameter control the behavior of the local TACL process when the
process receives an error 140 (FEMODEMERR) on its input. If TACL is not the
foreground process, it is the responsibility of the foreground process to process
the error 140 correctly. TACL cannot act on an error 140 unless it is the process
that receives error 140.