OSI/FTAM Configuration and Management Manual

Managing the FTAM Configuration

OSI/FTAM Configuration and Management Manual—421944-001

4-20

Aborting Processes

The ABORT command places processes in the STOPPED state without regard for the

integrity of the data being processed. The ABORT PROCESS command automatically

stops all pending requests for subdevices, stops all subdevices associated with the

process, and then stops the process. Use the ABORT PROCESS command when you

need to stop a process as quickly as possible, and the integrity of the data is less

important than stopping the process.

Deciding When to Stop and When to Abort Processes

Whether you should stop a process or abort it depends on the circumstances. Consider

two situations involving the Example FTAM Configuration on page 3-38. In the first

situation, you are planning to change the location of the MIB file using the ALTER

SUBSYS command. Before you can use the ALTER command to change SUBSYS

attributes, you must stop all processes below the APLMGR process. Since you are

planning this change, you can use the procedure described earlier to stop the process in

an orderly fashion.

For example, the command

STOP PROCESS $AMGR.#FTAMI.FTI1

stops the FTAM initiator process named FTI1. You can use this procedure for all four

processes in the example configuration to place them in the STOPPED state. You can

then suspend the APLMGR process, change the SUBSYS attribute, and restart the

processes.

In the second situation, you have discovered that the initiator FTI1 has been started

using an incorrect code file and needs to be stopped immediately, regardless of whether

or not it is servicing a request. The command

ABORT PROCESS $AMGR.#FTAMI.FTI1

stops any subdevices currently associated with FTI1, aborts all pending requests for

subdevices, and stops the process despite the fact that it may be servicing a request.

In both situations, the process named FTI1 is placed in the STOPPED state, but the

system does not delete the definition for the process. In the first situation, however, you

know that the operation of the initiator was not interrupted, so data integrity was

maintained. Using the ABORT command can leave data (for example, either local or

remote files) in an unknown condition.