Queue manager profile fields
Note
In the following table, a local queue manager is one that is on the same MVS system as the PAS that is specified in the associated queue manager target definition.
Queue manager profile fields
Field descriptions | MVS | Proxy | Agent |
---|---|---|---|
Target queue manager target name to which the profile applies The name can contain wildcards (? or *) for MVS and PROXY queue managers. Each AGENT queue manager must have a unique profile. | + | + | + |
Reply Timeout maximum length of time, in seconds, that MainView for MQ will wait for a reply to a command | + | + | + |
Connect Timeout number of seconds MainView for MQ will wait for a TCP/IP connection with the Node Manager to be completed before canceling the request A connect timeout can be from 5 to 180 seconds. The default value is 30. | + | ||
KeepAlives Sockets number of sockets MainView for MQ will keep alive with the Node Manager to improve the response time KeepAlives sockets can be from 0 to 10 sockets. The default value is 0. Note: Setting KeepAlives Sockets above 0 leaves the connections to the Node Manager open and can greatly improve response time, but it might increase the usage of TCP resources. | + | ||
Message Priority MainView for MQ priority set for query messages to the queue manager | + | + | + |
Security UserID ID that is passed to the queue manager for security checks The values are
For more information, see Passing user IDs to IBM MQ. | + | + | + |
Heartbeat Interval number of minutes between the pings that are issued by the BBI-SS PAS to the queue manager If the queue manager does not respond to the pings, requests for data are not made to that queue manager. If 0 is specified, no pings are issued before making data requests to the queue manager. | + | + | + |
Event PUB/SUB history of event messages If another process is running the BMC Integrated Event Listener, MainView for MQ can subscribe to the Event Listener. The messages are nonpersistent but do not have an expiration time. For information about subscribing to the Event Listener by using a batch job, see Subscribing to the Event Listener. The default value is Yes. | + | ||
Reply-to Queue Prefix 1- to 32-character string that is used as a prefix for reply queues that MainView for MQ creates to communicate with local queue managers If the queue manager serves as a proxy for a remote queue manager, the prefix is also used for the reply queue for the remote queue manager. The default prefix value is BBSMVMQS. | + | ||
Queue Manager Name 1- to 48-character string that specifies the name of the queue manager Specify this parameter when the queue manager name is longer than eight characters or contains lowercase characters. When specified, messages use the transmission queue with this name unless a remote queue manager alias is specified. | + | + | + |
IP Address IP address or host name of the node on which the Node Manager is running | + | ||
Service TCP/IP port number that is serviced by the Node Manager | + | ||
Proxy Queue Manager MVS queue manager that is used as a proxy to communicate with the remote queue manager | |||
Remote Qmgr Alias optional 1- to 48-character string that specifies the transmission queue name or queue manager alias to be used when a message is sent to the remote queue manager If not specified, messages are sent to a transmission queue with the name of the remote queue manager; if the remote queue manager is not specified, the target name is used. Specify a remote queue manager alias when one of the following situations occurs:
| |||
Local Qmgr Alias optional 1- to 48-character string that specifies the reply to a queue manager name When an alias is not specified, replies are directed to a transmission queue that has the name of the local queue manager. Specify a local queue manager alias when one of the following situations occurs:
| + | ||
History Collectors whether history data is to be collected for the following objects:
This field allows history collection to be turned off for a queue manager. BMC does not recommend disabling history collection. If history collection is disabled, API counts change on the statistics views but are not accumulated for interval or session data. The default value is ON. Note:
| + | + | + |
Comments