ViewPoint Manual

Process Definition Commands
ViewPoint Manual—426801-001
4-7
Define Process (DP) Command
Considerations
•
To resolve the program name for the file you specify, DP uses the current setting of
your TACL #PMSEARCHLIST. This is unlike the TACL command, RUN, which
uses your current #DEFAULTS to resolve the program name for your specified file.
•
The default symbolic name of a defined process is the file-name portion of the
process program file name. For example, this command defines a PERUSE process
with the symbolic name of PERUSE:
> DP PERUSE
It might not be desirable to use a symbolic name for a defined process that is the
same as the name of a utility, such as PERUSE, since it could interfere with your
ability to run the program normally. In the above example, the program PERUSE
would have to be run with the following command:
> $SYSTEM.SYSTEM.PERUSE
The better solution would be to use the PNAME option to assign some different
symbolic name to the defined process.
•
To run a process on a remote system, specify \system-name before the name of a
program file. For example, this command defines an EDIT process on the
\CHICAGO system:
> DP \CHICAGO.EDIT
The DP command assumes that the process is on a remote system and that the
volume and subvolume that contain the program file are $SYSTEM.SYSTEM.
•
The MACRO option allows you to keep the background process coordinated with
your environment; for instance, you can send a VOLUME command to FUP before
issuing a command. The process name is passed to the macro, so you can have an
expert macro coordinate all your defined processes that need this service.
Examples
The sample sequence of commands in Figure 4-1 defines and starts two processes: one
in the local system (command line 1) and one in a remote system (line 6). Note that
these defined processes are invoked simply by typing their symbolic names in response
to a TACL prompt. (The complete syntax for invoking a defined process is given at the
end of this section.)
Caution. Be aware that a collector process for the Spooler can have only 32 opens at a time.
If you define PERUSE processes, as in the above examples, and leave them running, you are
diminishing the effectiveness of the Spooler to process other jobs.