SUSPEND QMGR

Use SUSPEND QMGR to inform other queue mangers in a cluster that the local queue manager is not available for processing and cannot be sent messages, or to suspend logging and update activity for the queue manager until a subsequent RESUME QMGR command is issued. Its action can be reversed by the RESUME QMGR command.

Notes:

  1. On UNIX systems, the command is valid only on AIX, HP-UX, Linux, and Solaris.

  2. On z/OS, if you define CLUSTER or CLUSNL, the command fails if the channel initiator has not been started.

  3. On z/OS, if you define CLUSTER or CLUSNL, any errors are reported to the console on the system where the channel initiator is running; they are not reported to the system that issued the command.

  4. This command, with the CLUSTER and CLUSNL parameters, is not available on the reduced function form of WebSphere MQ for z/OS supplied with WebSphere Application Server.

Synonym: None 

SUSPEND QMGR
 
>>-SUSPEND QMGR--+-CLUSTER(clustername)-+----------------------->
                 +-CLUSNL(nlname)-------+
                 |     (1)              |
                 '-LOG------------------'
 
   .-CMDSCOPE(' ')------------. (2)   .-MODE(QUIESCE)-.
>--+--------------------------+-------+---------------+--------><
   |                     (1)  |       '-MODE(FORCE)---'
   '-CMDSCOPE(qmgr-name)------'

Notes:

  1. Valid only on z/OS.

  2. Valid only on full function WebSphere MQ for z/OS when the queue manager is a member of a queue-sharing group.

 

Parameter descriptions

CLUSTER(clustername)
The name of the cluster to suspend availability for.

CLUSNL(nlname)
The name of the namelist specifying a list of clusters to suspend availability for.

LOG
Suspends logging and update activity for the queue manager until a subsequent RESUME request is issued. Any unwritten log buffers are externalized, a system checkpoint is taken (non-data sharing environment only), and the BSDS is updated with the high-written RBA before the update activity is suspended. A highlighted message (CSQJ372I) is issued and remains on the console until update activity has been resumed. Valid on z/OS only. If LOG is specified, the command can be issued only from the z/OS console.

This option is not allowed when a system quiesce is active by either the ARCHIVE LOG or STOP QMGR command.

Update activity remains suspended until a RESUME QMGR LOG or STOP QMGR command is issued.

This command should not be used during periods of high activity, or for long periods of time. Suspending update activity can cause timing related events such as lock time outs or WebSphere MQ diagnostics dumps when delays are detected.

CMDSCOPE
This parameter applies to z/OS only and specifies how the command is executed when the queue manager is a member of a queue-sharing group.

CMDSCOPE cannot be used for commands issued from the first initialization input data set CSQINP1.

' '
The command is executed on the queue manager on which it was entered. This is the default value.

qmgr-name
The command is executed on the queue manager you specify, providing the queue manager is active within the queue-sharing group.

You can specify a queue manager name, other than the queue manager on which the command was entered, only if you are using a queue-sharing group environment and if the command server is enabled.

MODE
Specifies how the suspension of availability is to take effect:

QUIESCE
Other queue managers in the cluster are advised that the local queue manager should not be sent further messages.

FORCE
All inbound channels to other queue managers in the cluster are stopped forcibly. This occurs only if the queue manager has also been forcibly suspended from all other clusters to which the channel belongs.

The MODE keyword is allowed only with CLUSTER or CLUSNL. It is not allowed with LOG.

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.