Some of the content described in this article is available in meshIQ Manage versions 12.1 and later.
For a quick overview of what's new or changed, visit the meshIQ Highlights page for a version-by-version breakdown.
Jump to Section:
Version 12.x and Later
Version 11.3 and Earlier
Version 12.x and Later
A Service object in IBM MQ allows additional processes to be managed as part of a queue manager.
With services, you can define programs that start and stop automatically when the queue manager starts and ends.
All IBM MQ services run under the user ID of the user who started the queue manager.
To stop a service:
In the Services widget, select the service you want to stop.
-
From the Selected menu, choose:
Commands > Stop -
The Confirm Stop Service Action dialog opens.
Click Yes to stop the service immediately, or click Schedule to perform the action later.
(See Scheduling Jobs for more information.)
Once stopped, the service status changes to Stopped, and the associated background process ends.
The service remains inactive until it is started again or automatically started with the queue manager, depending on its configuration.
_________________________________________________________________________________________________________________
Version 11.3 and Earlier
A Service object in IBM MQ allows additional processes to be managed as part of a queue manager.
With services, you can define programs that start and stop automatically when the queue manager starts and ends.
All IBM MQ services run under the user ID of the user who started the queue manager.
To stop a service:
In the Services viewlet, select the service you want to stop.
-
From the Selected menu, choose:
Commands > Stop -
The Confirm Stop Service Action dialog opens.
Click Yes to stop the service immediately, or click Schedule to perform the action later.
(See Scheduling Jobs for more information.)
Once stopped, the service status changes to Stopped, and the associated background process ends.
The service remains inactive until it is started again or automatically started with the queue manager, depending on its configuration.