TACL Reference Manual

Built-In Functions and Variables
HP NonStop TACL Reference Manual—429513-018
9-342
#SERVER Built-In Function
KILL
specifies that the indicated server is to be deleted. You must specify a server-
name for this option. If a server is deleted, any processes that still have the
server open receive file-system error 66 (device downed) on subsequent I/O
operations to the named server.
name
is the access name of your TACL process. This argument is optional unless you
specify the KILL option. The name consists of your TACL process name followed
by a period, a number sign, a letter, and zero to six alphanumeric characters
($D127.#K39, for example); if you want, that can be followed by another period, a
letter, and zero to seven alphanumeric characters ($D127.#K39.ACM48, for
example). If you specify a create option and do not specify a name, TACL creates
one, of the form:
$your-tacl-name.#Snn
where nn is the next available server number.
Result
•
If you supply one or more create options, #SERVER returns a name for your TACL
process.
•
If you specify the KILL option, #SERVER returns nothing.
Considerations
•
When a process writes to your TACL process, the line is appended to the end of
the OUT variable of the server. When a process prompts for input, the prompt is
stored in your PROMPT variable, destroying all previous contents. When a process
reads a line from your TACL process, TACL removes the first line of the IN variable
and passes it to the process. If the IN variable is empty, the requesting process
waits until you put more data into the IN variable.
•
A TACL process can have a maximum of 100 simultaneous openers, but only one
process can read from it at a time. If one process has requested data from the IN
variable and a second process tries to retrieve data from the IN variable, the
second process receives a file-system error 28 (attempt to open a disk file or
$RECEIVE with maximum number of concurrent operations greater than one).
•
You can use the create options-IN, OUT, and PROMPT-in combination, but KILL
must be used alone.
•
There is a potential deadlock situation when using #SERVER to control DEBUG
and INSPECT for a process started by the same TACL. The deadlock occurs
because TACL waits for the program to read its startup messages, which it cannot
do because it is waiting for an R command from DEBUG or INSPECT, which in
turn is waiting for input from a TACL variable. To avoid this situation, before issuing