Space announcement


This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

STOP command

You use the STOP command to stop XBM subsystems and components.


The STOP command cannot be used on the snapshot component.

Syntax for the STOP command

The following table lists the keywords that you can use with this command.

Keywords for the STOP command




Stops the XBM subsystem identified by the subsystem identifier ( ssid)


Stops the specified XBM component provided no busy condition exists (such as a currently active snapshot job)

If a busy condition exists, XBM will not process the command but does issue error messages that explain why the component could not be stopped.

You can specify the following values for the COMPONENT keyword:

  • An asterisk (*) stops all XBM components except for those in a busy condition. Components that are not busy stop, but components in a busy condition do not stop.

  • The name value identifies the XBM component (DB2, IMS, PSS, SSI, VSAM, or ZIIP) to stop. You can use pattern-matching characters in the name.


If you use the STOP command to stop a component, the component will remain in that state until you restart it with the START command. If you stop and restart the XBM subsystem, the components will resume the state they were in when the XBM subsystem was stopped.


Forces the XBM subsystem to terminate immediately, regardless of what jobs it may be supporting

FORCE can be issued against an XBM subsystem only; FORCE cannot be issued against components. However, issuing FORCE against an XBM subsystem also stops the components on that subsystem.

Was this page helpful? Yes No Submitting... Thank you