Home

 

Parameter descriptions

 

CLUSTER(clustername)

The name of the cluster for which availability is to be suspended.

CLUSNL(nlname)

The name of the namelist specifying a list of clusters to suspend availability for.

FACILITY

Specifies the facility to which connection is to be terminated.

DB2

Causes the existing connection to DB2 to be terminated. The connection is re-established when the RESUME QMGR FACILITY(DB2) command is executed. Any current or subsequent MQGET and MQPUT API requests are suspended until the DB2 connection is re-established by a RESUME QMGR FACILITY(DB2) command, or if the queue manager is stopped.

IMSBRIDGE

Stops the sending of messages from IMS™ Bridge queues to OTMA. When the tasks which transmit messages to IMS have been terminated, no further messages are sent to IMS until one of the following actions happens:

  • OTMA or IMS is stopped and restarted

  • WebSphere MQ is stopped and restarted

  • A RESUME QMGR FACILITY(IMSBRIDGE) command is processed

Return messages from IMS OTMA to the queue manager are unaffected.

If you want to monitor progress of the command, issue the following command: 

DIS Q(*) CMDSCOPE(qmgr) STGCLASS(bridge_stgclass) IPPROCS
and ensure that none of the queues are open. If any queue is open, use DISPLAY QSTATUS to verify that the MQ-IMS bridge does not have it open.

This parameter is only valid on z/OS.

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.

‘ ’

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.

We 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, or FACILITY.

 

Parent topic:

SUSPEND QMGR


sc13500_


 

Home