TACL Reference Manual

UTILS:TACL Commands and Functions
HP NonStop TACL Reference Manual—429513-018
8-164
RUN[D|V] Command
(8,000 bytes), and adds 32,000, resulting in 40,000 bytes. Ensure that your named
swap file has enough extent file space.
•
To use either the INV or the OUTV option, your TACL process (the one from which
you are starting the new process) must have a process name.
•
To use INV dynamically, you must include the NOWAIT option, so that control
returns to your TACL process. To send information, wait for the prompt variable.If
you plan to wait for more than one prompt, clear the prompt variable prior to the
next wait.
•
If you include either the IN or the INV option, you cannot use the INLINE option,
and the reverse. You cannot use the INLINE option if a process started previously
with the INLINE option still exists.
•
If you include the INLINE option, TACL waits until the newly started process
prompts for the first time; this guarantees that the initial output of the process is
available in the #INLINETO variable (if any) when TACL resumes operation.
•
When running a process that communicates with TACL (such as by setting IN or
OUT to the TACL process name, or by using TACL variables in INV or OUTV, or
by using the INLINE feature), be careful to coordinate TACL functions that enable
the communication (such as #IN or #OUT) with the matching mechanisms in that
process. Deadlock conditions can result if TACL tries to open a process for
communication at the same time that process is trying to open TACL for
communication.
•
When you include the LIB option, the operating system tries to resolve external
references to procedures in the program. It searches the library file specified with
the LIB option when the program was run. The date and time of the last
modification of LIB, as well as the disk address of the library file, are stored in the
program file. When you run a program without specifying a library with the LIB
option, the operating system compares the disk address and modification date of
the actual library file with the information about the library in the program file. If
they do not match, the message “LIBRARY FILE CONFLICT” is displayed. This
safe-guard prevents you from inadvertently running the wrong version of the
library.
•
To use LIB, the user who runs a program should have write access to the program
file. For example, assume these two users:
GROUPA.USER1 GROUPB.USER2
and two files (with security CUCU) owned by USER1:
$DATA.USER1.PROG
$DATA.USER1.LIBFILE
These two attempts to run program PROG by USER1 succeed:
14> RUN PROG
15> RUN PROG / LIB LIBFILE /