TS/MP 2.5 Release Supplement

START ACS $ZACS
b. Use the SCF STATUS command to verify that the ACS subsystem has started. For more
information on this command, see “STATUS Command” (page 80). For example:
STATUS ACS $ZACS, DETAIL
Stopping the ACS Subsystem
If you are stopping the subsystem to change the configuration, you need to perform Step 2 only.
If you want to remove the TS/MP 2.5 from your system, perform the following steps.
1. Stop the Pathsend Requestors
For information on stopping Pathsend Requestors, see the TS/MP 2.5 System Management
Manual.
2. Stop the ACS Subsystem
a. Use the SCF STOP command to stop the ACS subsystem. For more information on this
command, see “STOP Command” (page 82). For example:
STOP ACS $ZACS, FORCED
b. Use the SCF STATUS command to verify that the ACS subsystem has stopped. For more
information on this command, see “STATUS Command” (page 80). For example:
STATUS ACS $ZACS, DETAIL
3. Stop the $ZACS Process
a. Use the SCF STATUS PROCESS command to check whether the $ZACS process has
stopped. For example:
STATUS PROCESS $ZZKRN.#ZACS, DETAIL
b. Use the SCF ABORT command interactively or in an OBEY file to abnormally terminate
it. The ABORT PROCESS command stops the $ZACS process but does not delete the
process configuration. Therefore, you can use the SCF START command to start the
$ZACS process again:
ASSUME PROCESS $ZZKRN
ABORT #ZACS
c. Use the SCF STATUS command, described in Step 1, to verify whether the $ZACS process
has stopped.
4. Delete the $ZACS Process Configuration
Use the SCF DELETE PROCESS command interactively or in an OBEY file to delete the ACS
domain coordinator process ($ZACS):
ASSUME PROCESS $ZZKRN
DELETE #ZACS
The DELETE PROCESS command removes the $ZACS configuration. Therefore, before you
can start the $ZACS process again, you must use the SCF ADD command to add the ACS
subsystem to your system configuration.
Stopping the ACS Subsystem 61