TACL Reference Manual

Built-In Functions and Variables
HP NonStop TACL Reference Manual—429513-018
9-307
#PROCESSINFO Built-In Function
•
If you do not specify a system in the SEARCH PROGRAMFILE option, TACL does
not assume that you are referring to the current default system; instead, it assumes
that the program file resides on the search system.
•
The recommended way to get information about a given process is as follows:
#PROCESSINFO /RESULT, ... ,SEARCH PROCESSID [p]/ 0,0
(assuming the variable P contains the process ID). This search method says
“search for process [p], starting at CPU,PIN 0,0.” Another way of doing this:
#PROCESSINFO /RESULT, ... / [p]
This second method says “start searching for a process at the CPU,PIN of the
primary of [p],” meaning TACL finds [p] itself; but if [p] expands to a CPU,PIN
instead of a process name, and if the process at that location has terminated,
#PROCESSINFO reports on the process at the next higher CPU,PIN.
•
Use care in getting several items of information from one call to #PROCESSINFO,
especially if assigning the results to variables with #SETMANY, as some options
may return nothing:
°
EXTSWAP is empty if the process does not have an extended swap file.
°
GMOMJOBID is empty if the process has no GMOM.
°
LIBRARY is empty if the process has no library file.
°
MOM is empty if the process is an orphan.
°
SYSTEM is empty if the process is local.
List those options last to avoid loss of synchronization between destination
variables and information items.
•
To determine whether a given process exists prior to calling #PROCESSINFO, use
the #PROCESSEXISTS built-in function.
•
It is possible for a process to have more than one extended data segment.
Therefore, repeated calls to #PROCESSINFO with the EXTSWAP option may
produce different results, depending on which extended segment the process is
using when you request the information. When checking a TACL process,
TACLSEGF can be returned as an extended data segment.
•
The home terminal and GMOMJOBID for a process can reside on different
systems from the target process. The SEARCH HOMETERM and SEARCH
GMOMJOBID commands have no effect on the search system.
•
If you do not specify a node for SEARCH PROGRAMFILE file or SEARCH
PROGRAMFILE template, TACL treats the program file as if it resides on the
search system. You can qualify the file or template parameter with a node name, if
necessary.
•
An OSS program pathname cannot be used as an input file name for a TACL
command.