Table of Contents
Advertisement
Initiating and Communicating With Processes
Using RUN and #NEWPROCESS Options
Initiating a Process
Using RUN and
#NEWPROCESS Options
5–2
Communicating with a process through $RECEIVE, using #REQUESTER,
#APPEND(V), and #EXTRACT(V).
This method uses the following type of communication:
TACL
Processing completion information
You can use the Define Process (DP) facility (not part of TACL) to communicate with
processes if your system has ViewPoint software. See "Using DefineProcess," later in
this section.
Section 6, "Running TACL as a Server," describes how to access TACL as a server
process.
The RUN command and #NEWPROCESS built-in function allow you to start a
process. For example, the following statement starts FUP:
#NEWPROCESS $SYSTEM.SYSTEM.FUP /CPU 3, NAME $FUP/
TACL provides RUN and #NEWPROCESS options that allow you to specify whether
your TACL process waits for the new process to finish or not. In addition, TACL
provides commands and a RUN and #NEWPROCESS option (IN) that send startup
information to the new process. Table 5-1 lists these options and commands.
Table 5-1. RUN and #NEWPROCESS Communication Options
Communication Requirements at Startup Time
Start a process and wait for it to finish; no communication
Start a process and return to TACL immediately; no
communication
Start a process and pass information at startup time
TACL also provides RUN and #NEWPROCESS options that support communication
to the new process. For information about these options and other related functions,
see "Communicating With a Process," later in this section.
The SPI and EMS interfaces provide programmatic interfaces to processes. For
additional information, see Section 7, "Using Programmatic Interfaces."
107365 Tandem Computers Incorporated
OPEN
WRITEREAD
REPLY
CLOSE
Associated RUN or #NEWPROCESS
Options and TACL Commands
None
NOWAIT option
ASSIGN, PARAM, and DEFINE
commands; IN option
Process such
as a device
Hide quick links:
Advertisement
Table of Contents
