Use the following procedure to stop the DBC subsystem through an IBM z/OS console command. You identify the DBC subsystem to stop through the subsystem ID (ssid) or XCF group value (group).
Warnings
Shutting down the DBC subsystem also shuts down all associated Subzero servers used by BMC Subsystem Optimizer for zEnterprise. If a server shuts down while active connections exist between the client and its remote subsystem, abends can occur in the Subzero, client, and subsystem address spaces.
Before you terminate the DBC subsystem or any Subzero address space, execute the processes and procedures that properly terminate a connection between a client and its connected subsystem.
Some product processes might require an extended amount of time to terminate successfully. If DBC shutdown is delayed, review DBCPRINT for the following message to determine the cause of the delay:
BMCDBC0232I... DBC is waiting for product productName to shutdown.
If the DBC does not shut down after a reasonable amount of time, you can use the following command to terminate the delayed process:
ssid STOP,FORCE
Use caution when doing so; terminating a process that is still in use can have unpredictable results. BMC recommends that you use the STOP,FORCE command only if preceding attempts to stop the DBC have failed.
Enter one of the following z/OS commands:
ssid STOP
group STOP
MODIFY ssid,STOP
Example
Assume that a DBC subsystem has an SSID of DBC1. You can stop this subsystem by issuing the STOP command as a MODIFY command: