TACL Reference Manual

UTILS:TACL Commands and Functions
HP NonStop TACL Reference Manual—429513-018
8-166
RUN[D|V] Command
Similarly, these commands also run a TEDIT process on the \CHICAGO system,
because the current default node name is used for file-name expansion:
14> SYSTEM \CHICAGO
15> TEDIT
A program file, however, must reside on the system where it runs; the command:
14> RUN \DETROIT.MYPROG
attempts to run a program file named:
\DETROIT. default-volume. default-subvolume.MYPROG
If no such program file exists on the remote system, a message is displayed
indicating that the file does not exist. See the Expand Management Programming
Manual for further information on creating remote processes.
•
If you specify more than one out-run-option, TACL returns “Option conflicts with
another option.”
•
If the PFS option is out of range, TACL returns “Expecting a number or an
arithmetic expression (Its value must be between 64 and 512 inclusive).”
•
Redirection abilities of the OSH command utility can be used. For more information
on redirection, see Section 6, Open System Services Shell and Utilities Reference
Manual.
These conditions apply to the use of the RUN command for starting TACL processes:
•
A TACL process starts in a logged-off state. If, however, Safeguard software
authenticates the user and starts the TACL process, that TACL process starts in a
logged-on state.
•
To run TACL as a server process, set the IN file to $RECEIVE. For more
information, see the TACL Programming Guide.
•
If the IN file is the same as the OUT file and the TACL process is not named, TACL
does not set its home terminal.
•
The OSH process should not be started with the INLINE option. If you use the
INLINE option:
•
TACL will not be able to detect the end of the INLINE process.
•
The output displayed might not be synchronized with the command entered
using the inline prefix.
Examples
1. This implicit RUN command runs the text editor program named TEDIT that
resides in the file $SYSTEM.SYSTEM.TEDIT:
14> TEDIT