SYSTEM.COMMAND.* queues" /> System command objects

 

System command objects

The names of the system command objects begin with the characters SYSTEM.COMMAND. You must define these objects before we can use the WebSphere MQ operations and control panels to issue commands to a WebSphere MQ subsystem.

There are two system command objects:

  1. The system-command input queue is a local queue on which commands are put before they are processed by the WebSphere MQ command processor. It must be called SYSTEM.COMMAND.INPUT, although an alias of SYSTEM.ADMIN.COMMAND.QUEUE for it can be defined, for compatibility with non-z/OS WebSphere MQ.

  2. SYSTEM.COMMAND.REPLY.MODEL is a model queue that defines the system-command reply-to queue.

There are 2 extra objects for use by the WebSphere MQ V6 Explorer:

Commands are normally sent using nonpersistent messages so both the system command objects should have the DEFPSIST(NO) attribute so that applications using them (including the supplied applications like the utility program and the operations and control panels) get nonpersistent messages by default. If you have an application that uses persistent messages for commands, set the DEFTYPE(PERMDYN) attribute for the reply-to queue, because the reply messages to such commands are persistent.