OSI/FTAM Configuration and Management Manual

Managing the FTAM Configuration
OSI/FTAM Configuration and Management Manual—421944-001
4-21
Suspending and Activating Processes
Because the ABORT command immediately and abruptly terminates all associations for
the process, it should be used only in emergency situations. Examples of these types of
situations include
•
A situation in which an attribute in the configuration is incorrect, and you need to
correct it quickly. In this case, the process may be servicing requests incorrectly, and
you simply want to stop the process quickly and correct the situation.
•
A case in which a process begins servicing a request that will be time-consuming,
and you realize that, due to time constraints, you are not able to wait for the services
to complete.
When you do need to place a process in the STOPPED state, it is recommended, if
possible, that you stop processes in an orderly fashion using the SCF STOP command.
Suspending and Activating Processes
A process in the STOPPED state is no longer running; you must restart it to put it back
into operation. Under certain circumstances, you might need or want to interrupt the
operation of a process without actually stopping it. To do this, you can change the state
of the process from STARTED to SUSPENDED using the SCF SUSPEND command.
The following are examples of situations that warrant suspending process activity:
•
You want to change SUBSYS configuration attributes; doing this requires that the
APLMGR process be in the SUSPENDED state.
•
You want to monitor the configuration in a completely static environment.
All subdevices associated with the target process must be discarded before the
SUSPEND PROCESS command will complete.
When you are ready to change the state of the process from SUSPENDED to
STARTED, use the ACTIVATE or START command to restart the suspended process.