OSI/AS SCF Reference Manual

Table Of Contents
OSI/AS SCF Commands
OSI/AS SCF Reference Manual424121-001
2-10
PROCESS Objects
PROCESS Object Wildcard Support
Wildcards are supported for indirect-process-name for the following commands:
ABORT PROCESS, ACTIVATE PROCESS, ALLOWOPENS PROCESS, DELETE
PROCESS, INFO PROCESS, NAMES PROCESS, START PROCESS, STATUS
PROCESS, STOP PROCESS, STOPOPENS PROCESS, and SUSPEND PROCESS.
Specify wildcards in the #process-type or internal-name fields. Examples of
the #process-type and internal-name fields with wildcards are
.*.E*
.#*.E*
.#TA*.*
.#NSP.N*
.#TSP.*1
PROCESS Object-Name Examples
The following are valid object-names for the PROCESS object:
$OSIM
$TAPS
$OSIM.#TAPS.TAPS1
$OSIM.#*.?1
$OSIM.#TSP.TSP1
PROCESS Object States
A TAPS or an OSI manager process can be in one of the following states:
Note. For the NAMES command, see NAMES Command Syntax on page 2-174, as wildcard
support for this command does not follow the above rules.
ABORTING The process is in transition to the STOPPED state because the
ABORT command was issued. The process is running but does not
accept new user requests.
STARTED The process is running and accepts new user requests.
STARTING The process is in transition to the STARTED state. New user
requests are not accepted until the process is in the STARTED state
STOPPED The process definition has been added to the subsystem
configuration, but the process is not running. Placing a process in
the STOPPED state causes it to stop running.