Queue manager profile fields

This topic describes the fields that you can specify for each queue manager profile.

Important

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.

Related topics

Installing

Customizing-after-installation

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 BMC AMI Ops Monitor for MQ will wait for a reply to a command	+	+
Message Priority BMC AMI Ops Monitor 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: USER - ID that is associated with the TSO session PAS - ID that is associated with the BBI-SS PAS Started Task 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, BMC AMI Ops Monitor 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 Pref 1- to 32-character string that is used as a prefix for reply queues that BMC AMI Ops Monitor 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.	+	+	+
Queue Manager Type The name associated with the platform on which the queue manager is executing. Valid values are: A–iSeries W–Windows U–Unix			+
Proxy Queue Manager MVS queue manager that is used as a proxy to communicate with the remote queue manager		+
QMGR Alias–Remote 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: There is no transmission queue with the name of the remote queue manager or its associated target name. You want to use a transmission queue that has a name that is different from that of the remote queue manager.		+
QMGR Alias–Local 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: There is no transmission queue with the name of the local queue manager. You want the reply to use a transmission queue that has a name that is different from the local queue manager.		+
Confirm Actions Allows for confirmation pop-ups when action commands that modify or delete MQ resources are issued from the product. The default is Y–Yes, and must be set to N–No if such confirmations are not required for the target Queue Manager. The following MQ resources prompt a confirmation pop-up when you perform a modify or delete action: Queue Manager Channels Channel Authentication Queues Coupling Facility Cluster Queue Managers NameLists Processes Page Set Page Set Usage Storage Classes Buffer Pools Log Information Communications Information Authentication Information Publish/Subscribe Information	+	+	+
History Collectors Whether history data is to be collected for the following objects: Queue Manager (QM) Buffer Pool (BP) Page Set Stats (PS) Log Manager (LM) Channels (CH) Queue Statistics (QS) DB2 Data (DB) Coupling Facility (CF) Application Stats (AS) Application Detail Stats (DS) 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 Y–Yes	+ + + + + + + + + +	+ +	+ + +
CONN The name of the connection as defined in MainView Middleware Administrator.			+
IP TCP/IP address or host name of the node on which the MainView Middleware Administrator agent is running.			+
Port TCP/IP Port number that is serviced by the MainView Middleware Administrator agent.			+
USER The user ID to be used for the connection with MainView Middleware Administrator (MVMA) server.			+
PSWD The password to be used for the connection with MainView Middleware Administrator (MVMA) server.			+
KEYDB The path of a key store database that contains the default certificate key used to encrypt outbound communication with the MainView Middleware Administrator.			+
KEYSTH The path of a password stash file that contains the encrypted password of the key store database.			+

Queue manager profile fields

On this page