Queue manager properties

The tables on this page list all the attributes that you can set for local and remote queue managers. For each attribute, there is a brief description of when you might need to configure the attribute. Where relevant, the tables also give the equivalent MQSC parameter for the ALTER QMGR and DISPLAY QMGR commands. For more information about MQSC commands, see Script (MQSC) Commands in the IBM® online IBM WebSphere® MQ product documentation.

Those attributes for a queue manager that are changed through MQSC using the ALTER QMGR commands are the ones that are shown for both local and remote queue managers. Note, that the IBM WebSphere MQ Explorer does not show all the properties for remote queue managers.

Those attributes that are defined in the qm.ini file (for UNIX systems) or in the Registry (for Windows), are the ones that are shown only for local queue managers. For example, the specification for the Recovery Logs and the XA apply to the qm.ini file, and so, is shown only for the local queue manager.

For lists of all the attributes that you can set for both local and remote queue managers in the queue manager's properties dialog see the following tables:

The attributes that are marked with an asterisk (*) update configuration files so you can view and edit them when the queue manager is stopped. If you edit the marked attributes when the queue manager is running, you must stop and restart the queue manager so that the changes take effect. You can edit the unmarked attributes only when the queue manager is running. For more information about the configuration attributes, see Changing queue manager configuration information in the IBM online IBM WebSphere MQ product documentation.

For more information, see Administering WebSphere MQ and Script (MQSC) Commands in the IBM online IBM WebSphere MQ product documentation.

General page

The following table lists the attributes that you can set on the General page of the Queue Manager properties dialog. The attributes marked with an asterisk (*) on the General page relate to stanzas in the configuration files.

Attribute Meaning MQSC parameter
*Queue manager name Read-only. You cannot change the name of the queue manager after it has been created. QMNAME
*Platform Read-only. This is the architecture of the platform on which the queue manager is running. PLATFORM
Queue manager status Read-only. This attribute shows the status of the queue manager, which can be 1 of the following options:
  1. Running
  2. Starting
  3. Quiescing
 STATUS
Coded character set ID Read-only. This is the coded character set identifier (CCSID) for the queue manager. The CCSID is the identifier that is used with all character string fields defined by the API. The value must be defined for use on your platform and must use a character set that is appropriate to the platform. CCSID
Description Type a meaningful description of the purpose of the queue manager. See Entering strings in IBM WebSphere MQ Explorer. DESCR
*Command level Read-only. This is the function level of the queue manager. CMDLEVEL
Version Read only. This is the version of IBM WebSphere MQ installed. The format is VVRRMMFF:
  • VV: Version
  • RR: Release
  • MM: Maintenance level
  • FF: Fix level
 VERSION
*Startup The Startup attribute controls how the selected queue manager is started. This attribute applies to Windows only. There are four options for the Startup attribute.

Select Automatic to start the queue manager automatically when the IBM MQ Series service starts. This is the default value.

Select Automatic, permitting multiple instances of the queue manager, to start the queue manager automatically when the IBM MQ Series service starts. For more information, see the sax option of crtmqm in the IBM online IBM WebSphere MQ product documentation.

Select Interactive (manual) to start the queue manager manually through IBM WebSphere MQ Explorer. The queue manager runs under the logged on user (the interactive user). The queue manager will automatically stop when the interactive user logs off.

Select Service (manual) to start the queue manager manually through IBM WebSphere MQ Explorer. The queue manager runs as a child of the MQ Services service. The queue manager will not automatically stop when the interactive user logs off.

 (Not applicable.)
Command server control To configure the command server so that it starts automatically when the queue manager starts, click Queue Manager; to configure the command server so that it does not start automatically and must be started manually, click Manual. SCMDSERV
Channel init control To configure the channel initiator so that it starts automatically when the queue manager starts, click Queue Manager; to configure the channel initiator so that it does not start automatically and must be started manually, click Manual. SCHINIT

Extended page

The following table lists the attributes that you can set on the Extended page of the Queue Manager properties dialog. The Default bind type attribute on the Extended page relates to the DefaultBindType stanza key in the configuration files.

Attribute Meaning MQSC parameter
Dead-letter queue Select the name of the queue that the queue manager uses as the dead-letter queue. DEADQ
Trigger interval Type the number of milliseconds, from 0 to 999999999, that the queue manager must wait between triggering messages for a queue. This attribute is used only when the Trigger type attribute in the Queue properties is set to First. TRIGINT
Max uncommitted messages Type the maximum number of uncommitted messages within a syncpoint, from 1 to 999999999, to limit the number of messages that can be retrieved and put within any single syncpoint. This attribute is not used for messages that are put or retrieved outside syncpoint. MAXUMSGS
Max handles Type the maximum number of open handles, from 0 to 999999999, that any one task can have at the same time. MAXHANDS
Max message length Type the maximum length of messages, from 32 KB to 100 MB, that is allowed on queues on the queue manager. The default value is 4 MB (4 194 304 bytes). If you reduce the maximum message length for the queue manager, you must also reduce the maximum length of the SYTEM.DEFAULT.LOCAL.QUEUE definition, and all other queues that are connected to the queue manager. This ensures that the queue manager's limit is not less than the limit of any of the queue manager's queues. If you do not do this, and applications inquire only the value of the queue's Max message length attribute, the applications might not work properly. MAXMSGL
Max properties length This value controls the size in bytes of the property data that can flow with messages in a V7 queue manager. If the size of the properties exceeds the maximum properties length then the message is rejected. MAXPROPL
Max priority Read-only. This is the maximum priority of the queue manager, which is 9. MAXPRTY
Message mark browse interval Type the time interval in milliseconds after which the queue manager automatically unmarks browsed messages. The interval can be set up to a maximum of 999999999 milliseconds. The interval can also be set to Unlimited. The default value is 5000.
Attention: You should not reduce the value below the default of 5000.
 MARKINT
Command input queue Read-only. This is the name of the system-command input queue. Suitably authorized applications can put commands on this queue. COMMANDQ
Syncpoint Read-only. This attribute states whether syncpoint is available with the queue manager. On z/OS, Windows, UNIX and Linux® syncpoint is always available. SYNCPT
Distribution lists Read-only. This attribute states whether the queue manager supports distribution lists. This attribute is valid only on AIX®, HP-UX, IBM i, Solaris, and Windows. DISTL
(UNIX and Linux only) Application group The Application group option specifies the application group that clients connecting should belong to. The default is to not belong to an application group. (Not applicable.)
*Default bind type This is the default bind type that is used if the application does not specify a bind type on the MQCNO parameter of the MQCONNX call. Select SHARED, or ISOLATED. (Not applicable.)
*Error log size Specify the size of the queue manager error log at which the log is copied to the backup. The value must be 1048576 - 2147483648 bytes. The default value is 262144 bytes (256 KB). (Not applicable.)
*Excluded messages Your IBM WebSphere MQ system might produce a large number of information messages if the system is heavily used. You can therefore exclude certain messages if required. Type the message ID of each message that is not to be written to the queue manager error log. Enter a comma-separated list of message IDs from the following list:
  • 7163 - Job started message (IBM i only)
  • 7234 - Number of messages loaded
  • 9001 - Channel program ended normally
  • 9002 - Channel program started
  • 9202 - Remote host not available
  • 9524 - Remote queue manager unavailable
  • 9528 - User requested closure of channel
  • 9999 - Channel program ended abnormally
 (Not applicable.)
*Suppressed messages Your IBM WebSphere MQ system might produce a large number of information messages if the system is heavily used. You can prevent selected messages being sent to the console or to the hardcopy log if required. Type the message ID of each message that will be written to the queue manager error log only once in a specified time interval. The time interval is specified in the Suppressed Messages Interval attribute. Enter a comma-separated list of message IDs from the following list:
  • 7163 - Job started message (IBM i only)
  • 7234 - Number of messages loaded
  • 9001 - Channel program ended normally
  • 9002 - Channel program started
  • 9202 - Remote host not available
  • 9524 - Remote queue manager unavailable
  • 9528 - User requested closure of channel
  • 9999 - Channel program ended abnormally

If the same message ID is specified in both the Excluded Messages and the Suppressed Messages attributes, the message is excluded.

(Not applicable.)
*Suppressed messages interval Type the time interval, in seconds, in which messages that are specified in the Suppressed Messages attribute will be written to the queue manager error log only once. The value must be 1 - 86400 seconds. The default value is 30 seconds. (Not applicable.)
Custom The Custom parameter is reserved for the configuration of new features before separate attributes have been introduced. The possible values are a list of zero or more attributes-value pairs, in MQSC-style syntax, separated by at least 1 space.
The attribute names and values are case-sensitive, and must be specified in uppercase. The values can contain spaces and parentheses, but must not contain single quotation marks. Examples of valid syntax are:
  • CUSTOM('')
  • CUSTOM('A(B)')
  • CUSTOM('C(D) E(F)')
  • CUSTOM('G(5000) H(9.20.4.6(1415))')

The queue manager parses the value, but if the string cannot be parsed according to these rules, or if it contains attributes or values that are not recognized, the queue manager ignores the errors.

 CUSTOM
Opening shared queues (z/OS only) When a queue manager makes an MQOPEN call for a shared queue and the queue manager that is specified in the ObjectQmgrName parameter of the MQOPEN call is in the same queue-sharing group as the processing queue manager, the Opening shared queues attribute specifies whether the ObjectQmgrName is used or whether the processing queue manager opens the shared queue directly. Use the queue manager specified in ObjectQmgrName means that the ObjectQmgrName is used, and the appropriate transmission queue is opened; Use the local queue manager means that the processing queue manager opens the shared queue directly, which can reduce the traffic in your queue manager network. SQQMNAME
Intra-group queuing (z/OS only) Specify whether intra-group queuing is used. To use the shared transmission queue (SYSTEM.QSG.TRANSMIT.QUEUE) when queue managers within a queue-sharing group exchange messages, click Enabled; to use non-shared transmission queues and channels when queue managers within a queue-sharing group exchanged messages, click Disabled. If you disable intra-group queuing, the same mechanism for message transfer is used as when the queue managers are not part of a queue-sharing group. IGQ
IGQ user ID (z/OS only) Specify a user identifier to be used by the IGQ agent to establish authority to put messages to a destination queue. The queue manager must be a member of a queue-sharing group to use this attribute. To specify that the user ID of the receiving queue manager within the queue-sharing group is to be used as the IGQ user ID, leave the field blank. IGQUSER
IGQ authority check type (z/OS only) Specify the type of authority checking and, therefore, the user identifiers, to be used by the IGQ agent. This establishes the authority to put messages to the destination queue. The queue manager must be a member of a queue-sharing group to use this attribute. To specify that the default user ID is used to establish authority, click Default; to specify that the IGQ user ID and the ALT user ID is used to establish authority, click Alternate or IGQ; to specify that only the IGQ user ID is used to establish authority, click Only IGQ; to specify that the user ID from the UserIdentifier field in the message descriptor, of a message on the SYSTEM.QSG.TRANSMIT.QUEUE queue, is used to establish authority, click Context. IGQAUT
Expiry interval (z/OS only) Type the approximate value in seconds that specifies how often queues are scanned to discard expired messages. the value must be 1 - 99999999. The minimum scan interval is 5 seconds, even if you specify a lower value 1 - 4. Specify an interval of 0 to ensure that the queues are not scanned; this is the default value. EXPRYINT
Security profile case (z/OS only) Specify whether the queue manager supports security profile names in mixed case or in uppercase only. Select Mixed to specify that security names can be in uppercase or in mixed case. Select Upper to specify that security profile names must be in uppercase. This is the default value. SCYCASE

Exits page

The following table lists the attributes that you can set on the Exits page of the Queue Manager properties dialog. To configure the queue manager to run user exits, edit the attributes on the Exits page. The attributes on the Exits page relate to stanzas in the configuration files.

Attribute Meaning Stanza key
*Exit default path If the queue manager is 32 bit, type the path to the location in which exits for this queue manager are stored by default. ExitsDefaultPath
*Exit default path (64 bit) If the queue manager is 64 bit, type the path to the location in which exits for this queue manager are stored by default. ExitsDefaultPath64
*Local API Exits Add details of the local API exits that you want to use with this queue manager. ApiExitLocal
*Name Specifies the descriptive name of the API exit that is passed to the API exit in the ExitInfoName field of the MQAXP structure. This name must be unique and is limited to a length of 48 characters, and must contain only those characters that are valid for the name of IBM WebSphere MQ objects, such as queue names. Name
*Type Specifies the type of exit: queue manager, or override. (Not a separate stanza key.)
*Sequence This attribute is an unsigned numeric value that defines the sequence in which this API exit is called in comparison with other API exits. An API exit with a low sequence number is called before another API exit with a higher sequence number. The order in which different API exits with the same sequence number are called is undefined. It is perfectly valid for there to be gaps in the sequence numbers of the API exits defined for a queue manager. Sequence
*Module Specifies the module that contains the code for the API exit. If this field contains the full path name of the module it is used as is. If this field contains just the module name, the module is located using the same method as channel exits; that is, using the value in the Exit default path field on the Exits page of the queue manager properties dialog. Module
*Function Specifies the name of the function entry-point into the module that contains the code for the API exit. This entry-point is the MQ_INIT_EXIT function. The length of this field is limited to MQ_EXIT_NAME_LENGTH. Function
*Data If this attribute is specified, leading and trailing blanks are removed, the remaining string is truncated to 32 characters, and the result is passed to the exit in the ExitData field of the MQAXP structure. If this attribute is not specified, the default value of 32 blanks is passed to the exit in the ExitData field of the MQAXP structure. Data

Cluster page

The following table lists the attributes that you can set on the Cluster page of the Queue Manager properties dialog. To configure the cluster attributes of the queue manager, edit the attributes on the Cluster page.

Attribute Meaning MQSC parameter
Cluster membership Read-only. This table lists the names of the clusters to which the queue manager belongs. (Not applicable.)
Cluster workload exit The exit is called when a message is put on a cluster queue. Type the name of the cluster workload exit:
  • On UNIX and Linux systems, use the format libraryname(functionname). The maximum length is 128 characters.
  • On Windows, use the format dllname(functionname), where dllname is specified without the .dll suffix. The maximum length is 128 characters.
  • On z/OS, type the load module name. The maximum length is 8 characters.
  • On IBM i, use the format progname libname, where progname occupies the first 10 characters, and libname occupies the second 10 characters; if necessary, use blanks to pad the characters to the right. The maximum length is 20 characters.
 CLWLEXIT
Cluster workload data Type the data to be passed to the cluster workload exit when the exit is called. The maximum length of the data is 32 characters. CLWLDATA
Cluster workload length Type the maximum number of bytes of message data that is passed to the cluster workload exit:
  • On Windows, type a number from 0 to 104857600 (100 MB).
  • On other platforms, type a number from 0 to 999999999.
CLWLLEN
Max outbound cluster channels Type the maximum number of outbound cluster channels. For more information, see Queue manager clusters in the IBM online IBM WebSphere MQ product documentation. CLWLMRUC
Cluster workload mode The cluster workload exit, CLWL, allows you to specify which cluster queue in the cluster is to be opened in response to an MQI call (for example MQOPEN or MQPUT). The default value is SAFE, which means that the CLWL exit is run in a separate process to the queue manager so that if there is a problem, the integrity of the queue manager is preserved. However, running the CLWL exit as a separate process can have a detrimental effect on performance. To improve performance by running the CLWL exit in the same process as the queue manager, click FAST. Use FAST mode only if you are certain that there are no problems with your CLWL exit because if there is a problem in FAST mode, the queue manager fails and the queue manager's integrity is at risk. The value set for the queue manager will override the value set for the machine-wide configuration. CLWLMode
CLWL use queue This attribute specifies whether the queue manager can choose from remote instances of cluster queues as well as local instances. If the queue manager receives a message by way of a cluster channel, the message is put on a local instance of the cluster queue; if the queue manager receives a message locally or by way of a non-cluster channel, and the value of this attribute is Any, the message is put on either local or remote instances of the cluster queue. To enable the queue manager to use remote instances of cluster queues, click Any; to prevent the queue manager using remote instances of cluster queues, click Local. For more information, see Queue manager clusters in the IBM online IBM WebSphere MQ product documentation. CLWLUSEQ
Default cluster transmission queue The default transmission queue type that is used by clustering to transfer messages to other queue managers in the cluster. Messages are transferred by cluster-sender channels.

The default value of this attribute is SCTQ. The queue manager uses a single transmission queue to transfer all cluster messages. The transmission queue is SYSTEM.CLUSTER.TRANSMIT.QUEUE.

To send messages to each queue manager, in each cluster, using a different transmission queue, set the value of Default cluster transmission queue to Queue for each channel. The queue manager automatically creates a transmission queue if it needs one to send a message to another queue manager in a cluster. The queue is permanent-dynamic. It is created from the model queue SYSTEM.CLUSTER.TRANSMIT.MODEL.QUEUE. The name of each transmission queue is SYSTEM.CLUSTER.TRANSMIT.ChannelName. ChannelName is the name of the cluster-sender channel that transfers messages from the queue.

 DEFCLXQ

Repository page

The following table lists the attributes that you can set on the Repository page of the Queue Manager properties dialog. To specify that the queue manager hosts the repository for one or more clusters, edit the attributes on the Repository page.

Attribute Meaning MQSC parameter
Not a cluster full repository To specify that the queue manager is not a full repository for a cluster, select this option. (Not applicable.)
Full repository for a cluster To make this queue manager a full repository for just one cluster, select this option, then type the name of the cluster. REPOS
Full repository for a list of clusters To make this queue manager a full repository for more than one cluster, select this option, then type the name of the cluster. REPOSNL

Communication page

The following table lists the attributes that you can set on the Communication page of the Queue Manager properties dialog. To configure how the queue manager sends and receives messages, edit the attributes on the Communication page.

Attribute Meaning MQSC parameter
Default transmission queue Type the name of the default transmission queue on which messages that are destined for a remote queue manager are put if there is no other suitable transmission queue defined. The queue named must be a local transmission queue, but not the cluster transmission queue. DEFXMITQ
Channel auto definition To enable receiver- and server-connection channels to be defined automatically, click Enabled; to prevent receiver- and server-connection channels being defined automatically, click Disabled. Cluster-sender channels can always be defined automatically, regardless of the setting of this attribute. CHAD
Channel auto definition exit The exit is called when an inbound request for an undefined receiver, server-connection, or cluster-sender channel is received. The exit is also called when starting a cluster-receiver channel. Type the name of the channel auto-definition exit:
  • On Windows, use the format dllname(functionname), where dllname is specified with the .dll suffix. The maximum length is 128 characters.
  • On IBM i, use the format progname libname, where progname occupies the first 10 characters and libname occupies the second 10 characters; if necessary, use blanks to pad the characters to the right. The maximum length is 20 characters.
  • On UNIX and Linux, use the format libraryname(functionname). The maximum length is 128 characters.
  • On z/OS, type the load module name. The maximum length is eight characters.
 CHADEXIT
Channel authentication To exercise more precise control over the access granted to connecting systems at a channel level, you can use channel authentication records. IBM WebSphere MQ version 7.1, and later, queue managers are created using channel authentication by default. If you migrate a queue manager to IBM WebSphere MQ Version 7.1 from an earlier release, channel authentication is not enabled. To enable channel authentication, use the command ALTER QMGR CHLAUTH(ENABLED) CHLAUTH
IP address version To specify that the queue manager uses the IPv6 protocol, click IPV6; to specify that the queue manager uses the IPv4 protocol, click IPV4. IPADDRV
Activity recording If a queue manager application performs some work on behalf of a message in which activity reports were requested, the queue manager can generate an activity report. You can use this activity report to work out where the message went in the queue manager network. To prevent queue manager applications generating activity reports, click Disabled; to enable queue manager applications to generate activity reports, click Message or Queue. If you click Message, a queue manager application that generates an activity report puts the report on the queue that the originator of the message requested in the ReplyToQ and ReplyToQMgr fields of the message descriptor; if you click Queue, a queue manager application that generates an activity report puts the report on the system queue SYSTEM.ADMIN.ACTIVITY.QUEUE. If you make changes to this attribute, you must stop and restart any channels to which you want the changes to apply. ACTIVREC
Trace-Route recording You can use Trace-Route messages to determine the routes that messages take through a queue manager network. Participating queue manager applications can generate information about the route and put the information in activity reports. The queue manager applications can also add the information to the Trace-Route message itself, depending on the options set in the Trace-Route message. The Trace-Route message can then accumulate chronological information about the route. The Activity recording attribute specifies on which queue the activity reports are put. The Trace-route recording attribute controls the accumulation of information in the Trace-Route message itself. To prevent the queue manager appending route information within the Trace-Route message and from returning information in reply messages, click Disabled. To enable queue manager applications to add the route information to the Trace-Route message, click Message or Queue. If you click Message and a queue manager application generates a reply message containing the accumulated route information from the Trace-Route message, the queue manager application puts the reply message on the queue that the originator of the message requested in the ReplyToQ and ReplyToQMgr fields of the message descriptor; if you click Queue and a queue manager application generates a reply message containing the accumulated route information from the Trace-Route message, the queue manager application puts the reply message on the system queue SYSTEM.ADMIN.TRACE.ROUTE.QUEUE. If you make changes to this attribute, you must stop and restart any channels to which you want the changes to apply. ROUTEREC

Events page

The following table lists the attributes that you can set on the Events page of the Queue Manager properties dialog. To configure the queue manager to generate events in response to certain criteria, edit the attributes on the Events page.

Attribute Meaning MQSC parameter
Authority events When an application tries to open a queue for which the application does not have the required authority, the queue manager can generate an authorization event message. To generate authorization event messages, click Enabled; to prevent the queue manager generating authorization event messages, click Disabled. AUTHOREV
Inhibit events When an application tries to put a message on a queue that is put-inhibited, or to get a message from a queue that is get-inhibited, the queue manager can generate an inhibit event message. To generate inhibit event messages, click Enabled; to prevent the queue manager generating inhibit event messages, click Disabled. INHIBTEV
Local events When an application or the queue manager has not been able to access an object, for example because the object has not been defined, the queue manager can generate a local event message. To generate local event messages, click Enabled; to prevent the queue manager generating local event messages, click Disabled. LOCALEV
Remote events When an application or the queue manager cannot access a queue on another queue manager, for example the transmission queue is not correctly defined, the queue manager can generate a remote event message. To generate remote event messages, click Enabled; to prevent the queue manager generating remote event message, click Disabled. REMOTEEV
Start and stop events When a queue manager starts, or has been requested to stop or quiesce (z/OS supports only start), the queue manager can generate a start and stop event message. To generate start and stop event messages, click Enabled; to prevent the queue manager generating start and stop messages, click Disabled. STRSTPEV
Performance events When a resource reaches a threshold condition, for example a queue depth limit has been reached, the queue manager can generate a performance event message. To generate performance event messages, click Enabled; to prevent the queue manager generating performance event messages, click Disabled. PERFMEV
Command events When an MQSC command or PCF command is executed successfully, the queue manager can generate command event messages. To generate command event messages, click Enabled; to prevent the queue manager generating command events, click Disabled; to generate command event messages except DISPLAY MQSC commands and Inquire PCF commands, click No Display. CMDEV
Channel events When the queue manager detects certain conditions on a channel, for example the channel starts or stops, the queue manager can generate channel event messages. To generate channel event messages, click Enabled; to prevent the queue manager generating channel event messages, click Disabled. CHLEV
Channel auto definition events When a channel is automatically generated, the queue manager can generate a channel auto-definition event message. To generate channel auto-definition event messages, click Enabled; to prevent the queue manager generating channel auto-definition event messages, click Disabled. CHADEV
SSL events When a channel that uses Secure Sockets Layer (SSL) security fails to establish an SSL connection, the queue manager can generate an SSL event message. To generate SSL event messages, click Enabled; to prevent the queue manager generating SSL event messages, click Disabled. SSLEV
Configuration events When an object is created or modified, the queue manager can generate a configuration event message. To generate configuration event messages, click Enabled; to prevent the queue manager generating configuration event messages, click Disabled. CONFIGEV
Bridge events (z/OS only) When an IMS bridge starts or stops, the queue manager can generate a bridge event message. To generate bridge event messages, click Enabled; to prevent the queue manager generating bridge event messages, click Disabled. BRIDGEEV
Logger events When a queue manager is configured to use linear logging, the queue manager can be configured to generate a logger event message when changes are written to the IBM WebSphere MQ recovery log. To generate logger event messages, click Enabled; to prevent the queue manager generating logger event messages, click Disabled. LOGGEREV

SSL page

The following table lists the attributes that you can set on the SSL page of the Queue Manager properties dialog. To configure the queue manager and its channels to use SSL security, edit the attributes on the SSL page.

Attribute Meaning MQSC parameter
Key repository Type the full path to the key repository for the queue manager. SSLKEYR
Revocation namelist Type the name of the revocation namelist. The revocation namelist can contain a mixture of authentication information objects from either, or both, of the following types:
  • CRL LDAP authentication information objects, which store connection information for LDAP servers that contain Certification Revocation Lists (CRLs).
  • Online Certificate Status Protocol (OCSP) authentication information objects, which store connection information for OCSP responders.
 SSLCRLNL
Cryptographic hardware To configure your cryptographic hardware, click Configure In the Cryptographic hardware settings dialog, enter the details of your cryptographic hardware. SSLCRYP
SSL Reset Count Type the number of unencrypted bytes, from 0 to 999999999, that are sent and received within an SSL conversation before the secret key is renegotiated. A value of 0 means that the secret key is never renegotiated. The number of bytes includes control information that is sent by the message channel agent (MCA). If the value of this attribute is greater than 0 and the value of the Heartbeat interval attribute in the Channel properties is greater than 0, the secret key is also renegotiated before message data is sent or received following a channel heartbeat. SSLRKEYC
SSL FIPS required To specify whether only FIPS-certified cryptographic algorithms are to be used (if the cryptography is performed in IBM WebSphere MQ rather than cryptographic hardware), click Yes. To specify that any cryptographic algorithm can be used, click No. SSLFIPS
OCSP authentication The OCSP authentication setting dictates the outcome of a connection in the event of an 'Unknown' response from the OCSP call.
  • Required: IBM WebSphere MQ rejects the connection.
  • Optional: The connection is allowed to succeed.
  • Warn: The connection is also allowed to succeed and IBM WebSphere MQ issues a message of type AMQ9717 into the error logs.
 N/A
OCSP check extensions The OCSP check extensions attribute controls whether the OCSP server details in AuthorityInfoAccess certificate extensions, are used to perform a digital revocation check. There are 2 possible values for the attribute:
  • Yes: A digital certificate revocation check is performed. This is the default value.
  • No: A digital certificate revocation check is not performed.
 N/A
SSL HTTP proxy name The SSL HTTP proxy name is either the host name or network address of the HTTP proxy server which is to be used by GSKit for OCSP checks. This address can optionally be followed by a port number, enclosed in parentheses. If you do not specify the port number, the default HTTP port, 80, is used. N/A
Suite B strength The Suite B strength attribute controls whether Suite B encryption is used. There are four possible values for the attribute:
  • 128-bit
  • 192-bit
  • none
  • 128-bit and 192-bit
 SUITEB
Certificate validation policy The certificate validation policy attribute controls which SSL/TLS certificate validation policy is used to validate digital certificates received from remote partners. There are two possible values for the attribute:
  • ANY
  • RFC5280
Changes to this attribute take effect only after a refresh security command has been issued. For information about how to refresh security in the MQ Explorer, see Refreshing SSL or TLS security.		 CERTVPOL

Statistics page

The following table lists the attributes on the Statistics page of the Queue Manager properties dialog. The Statistics page displays the information about the history of the queue manager. You cannot edit any of these attributes.

Attribute Meaning MQSC parameter
Creation date Read-only. This is the date on which the queue was created. CRDATE
Creation time Read-only. This is the time at which the queue was created. CRTIME
Alteration date Read-only. This is the date on which the queue's attributes were last altered. ALTDATE
Alteration time Read-only. This is the time at which the queue's attributes were last altered. ALTTIME
QMID Read-only. This is the internally-generated unique name of the queue manager. QMID

Online monitoring

The following table lists the attributes that you can set on the Online monitoring page of the Queue Manager properties dialog. To collect data about the current performance of the queue manager's channels and queues, edit the attributes on the Online monitoring page.

Attribute Meaning MQSC parameter
Channel monitoring This attribute specifies whether to collect online monitoring data about the current performance of channels hosted by the queue manager. To switch off online monitoring data collection for the queue manager's channels that have the value Queue Manager in their Channel monitoring attribute, click Off; to switch off online monitoring data collection for all the queue manager's channels regardless of the setting of the channel's Channel monitoring attribute, click None. To specify a low rate of data collection, with a minimal effect on system performance, for channels that have the value Queue Manager in their Channel monitoring attribute, click Low; to specify a moderate rate of data collection, with limited effect on system performance, for channels that have the value Queue Manager in their Channel monitoring attribute, click Medium; to specify a high rate of data collection, with a likely effect on system performance, for channels that have the value Queue Manager in their Channel monitoring attribute, click High. MONCHL
Queue monitoring This attribute specifies whether to collect online monitoring data about the current performance of queues hosted by the queue manager. To switch off online monitoring data collection for the queue manager's queues that have the value Queue Manager in their Queue monitoring attribute, click Off; to switch off online monitoring data collection for all the queue manager's queues regardless of the setting of the queue's Queue monitoring attribute, click None. To specify a low rate of data collection, with a minimal effect on system performance, for queues that have the value Queue Manager in their Queue monitoring attribute, click Low; to specify a moderate rate of data collection, with limited effect on system performance, for queues that have the value Queue Manager in their Queue monitoring attribute, click Medium; to specify a high rate of data collection, with a likely effect on system performance, for queues that have the value Queue Manager in their Queue monitoring attribute, click High. MONQ
Auto CLUSSDR monitoring This attribute specifies whether to collect online monitoring data about the current performance of auto-defined cluster-sender channels. To inherit from the value of the queue manager's Channel monitoring attribute, click Queue Manager; to switch off data collection for auto-defined cluster-sender channels on the queue manager, click None; to specify a low rate of data collection with a minimal effect on system performance, click Low (the data that is collected is unlikely to be the most current); to specify a moderate rate of data collection with limited effect on system performance, click Medium; to specify a high rate of data collection with a likely effect on system performance, click High (the data that is collected is the most current available). MONACLS
Activity trace override This attribute specifies whether applications can override the value of the queue manager attribute ACTVTRC. Valid values are Enabled and Disabled. When Enabled is selected, applications can override the settings of the ACTVTRC parameter by using the options field of the MQCNO structure of the MQCONNX API call. When Disabled is selected, applications cannot override the settings of the ACTVTRC parameter. Disabled is the default value for this parameter. Changes to this parameter are effective for connections to the queue manager that occur after the change. This parameter is valid only on IBM i, UNIX and Windows systems. ACTVCONO
Activity trace This attribute specifies whether MQI application activity tracing information is to be collected. Valid values are On and Off. When On is selected, MQI application activity tracing information collection is enabled. If queue manager attribute ACTVCONO is set to Enabled, the value of this parameter can be overridden using the options field of the MQCNO structure. When Off is selected, MQI application activity tracing information collection is disabled. Off is the default value for this parameter. Changes to this parameter are effective for connections to the queue manager that occur after the change. This parameter is valid only on IBM i, UNIX and Windows systems. ACTVTRC

Statistics monitoring

The following table lists the attributes that you can set on the Statistics monitoring page of the Queue Manager properties dialog. To collect statistical data on the activity of the queue manager, edit the attributes on the Statistics monitoring page.

Attribute Meaning MQSC parameter
MQI Statistics To collect MQI statistics data for the queue manager, click On; to prevent MQI statistics monitoring data collection for the queue manager, click Off. STATMQI
Queue Statistics This attribute specifies whether to collect statistics data about the activity of queues hosted by the queue manager. To switch on statistics data collection for the queue manager's queues, click On; to switch off statistics data collection for the queue manager's queues that have the value Queue Manager in their Queue statistics attribute (see Queue properties), click Off; to switch off statistics data collection for all the queue manager's queues regardless of the setting of the queue's Queue statistics attribute, click None. STATQ
Channel Statistics This attribute specifies whether to collect statistics data about the activity of channels hosted by the queue manager. To switch off statistics data collection for the queue manager's channels that have the value Queue Manager in their Channel statistics attribute (see Channel properties), click Off; to switch off statistics data collection for all the queue manager's channels regardless of the setting of the channel's Channel statistics attribute, click None. To specify a low rate of data collection, with a minimal effect on system performance, for channels that have the value Queue Manager in their Channel statistics attribute, click Low; to specify a moderate rate of data collection, with limited effect on system performance, for channels that have the value Queue Manager in their Channel statistics attribute, click Medium; to specify a high rate of data collection, with a likely effect on system performance, for channels that have the value Queue Manager in their Channel statistics attribute, click High. STATCHL
Auto CLUSSDR Statistics This attribute specifies whether to collect statistics data about the activity of auto-defined cluster-sender channels. To inherit from the value of the queue manager's Channel statistics attribute, click Queue Manager; to switch off data collection for auto-defined cluster-sender channels on the queue manager, click None; to specify a low rate of data collection, click Low (the data that is collected is unlikely to be the most current); to specify a moderate rate of data collection, click Medium; to specify a high rate of data collection, click High (the data that is collected is the most current available). STATACLS
Statistics Interval Type the interval, in seconds, between writing the statistics monitoring data to the monitoring queue. The default value is 1800 seconds (30 minutes). STATINT

Accounting monitoring

The following table lists the attributes that you can set on the Accounting monitoring page of the Queue Manager properties dialog. To collect data about the activity of a connection, edit the attributes on the Accounting monitoring page.

Attribute Meaning MQSC parameter
MQI accounting To collect MQI accounting data for the queue manager, click On; to prevent MQI accounting monitoring data collection for the queue manager, click Off. ACCTMQI
Queue accounting This attribute specifies whether to collect accounting data about the activity of connections for queues hosted by the queue manager. To switch on accounting data collection for the queue manager's queues, click On; to switch off accounting data collection for the queue manager's queues that have the value Queue Manager in their Queue accounting attribute (see Queue properties), click Off; to switch off accounting data collection for all the queue manager's queues regardless of the setting of the queue's Queue accounting attribute, click None. ACCTQ
Accounting interval Type the interval, in seconds, between writing the accounting monitoring data to the monitoring queue. The default value is 1800 seconds (30 minutes). ACCTINT
Accounting conn override Applications can override the MQI accounting attribute and the Queue accounting attribute using the Connect options in MQCONNX calls. To enable applications to override the attributes, click Enabled; to prevent applications overriding the attributes, click Disabled. ACCTCONO

Log page

The following table lists the attributes that you can set on the Log page of the Queue Manager properties dialog. To configure the log settings for the queue manager, edit the attributes on the Log page. The attributes on the Log page relate to stanzas in the configuration files.

Attribute Meaning Stanza key
*Log type Read-only. This attribute shows the type of logging that the queue manager uses. You cannot change the type of logging after the queue manager is created. LogType
*Log path Read-only. This attribute shows the location of the queue manager's logs. You cannot change the value of the Log path attribute after the queue manager is created. LogDefaultPath
*Log file pages Read-only. This attribute shows the number of 4 KB pages in the log file. For example, if the value is 256, the file size is 1 MB.

The default value is 4096, the file size 16 MB.

 LogFileSize
*Log primary files These are the log files that are allocated when the queue manager is created.

On Windows, type the number, from 2 to 254, of primary log files. The default value is 3. The total number of primary and secondary log files must not exceed 255 and must not be less than 3.

On UNIX and Linux, type the number, from 2 to 510, of primary log files. The default value is 3. The total number of primary and secondary log files must not exceed 511 and must not be less than 3.

The value is examined when the queue manager is created or started. You can change the value after the queue manager has been created but the change is not effective until the queue manager is restarted.

 LogPrimaryFiles
*Log secondary files These are the log files that are allocated when the primary files are exhausted.

On Windows, type the number, from 1 to 253, of secondary log files. The default value is 3. The total number of primary and secondary log files must not exceed 255 and must not be less than 3.

On UNIX and Linux, type the number, from 1 to 509, of secondary log files. The default value is 3. The total number of primary and secondary log files must not exceed 511 and must not be less than 3. 		LogSecondaryFiles
*Log buffer pages Type the number, from 0 to 4096, of 4 KB buffer pages for writing. If you type a number from 1 to 17, the minimum of 18 (72 KB) is used. If you type a number from 18 to 4096, that number of pages is used. If you type 0, the queue manager selects the size. In IBM WebSphere MQ for Windows Version 7.0 and alter, this is 512 (2048 KB).

The default value is 0 (Which the queue manager selects as 512 (2048 KB). If you change the value of this property, restart the queue manager to apply the change.

 LogBufferPages
*Log write integrity This is the method that the logger uses to reliably write log records. If you are using a non-volatile write cache (for example, ssa write cache enabled), it is safe for the logger to write log records in a single write, so click SingleWrite; if you need to write log records with more integrity, click DoubleWrite to use an additional write; if you need to write log records with complete integrity but at the cost of performance, click TripleWrite to use another additional write. LogWriteIntegrity

XA resource managers

The following table lists the attributes that you can set on the XA resource manager page of the Queue Manager properties dialog. The XA resource manager page displays attributes to edit if the queue manager coordinates its own units of work along with database updates; for example, the name of the resource manager (the database) and the location of the switch file, which helps the IBM WebSphere MQ communicate with the database. The attributes on the XA resource manager page relate to the XAResourceManager stanza in the configuration files.

Attribute Meaning Stanza key
*Name Type the name of the resource manager (the database). Name
*SwitchFile Type the location of the switch file, which helps IBM WebSphere MQ to communicate with the database. SwitchFile
*XAOpenString You can type a string of data that IBM WebSphere MQ passes in its calls to the database manager's xa_open function. IBM WebSphere MQ and the queue manager call the xa_open function when the queue manager starts and when you make the first call to MQBEGIN in your IBM WebSphere MQ application process. The default is a zero-length string. XAOpenString
*XACloseString You can type a string of data that IBM WebSphere MQ passes in its calls to the database manager's xa_close function. IBM WebSphere MQ and the queue manager call the xa_close function when the queue manager starts and when you make a call to MQDISC in your IBM WebSphere MQ application process, having earlier made a call to MQBEGIN. The default is a zero-length string. It is common to have a zero-length string. XACloseString
*ThreadOfControl The queue manager uses this value for serialization purposes. If the database client allows threads to call the XA functions without serialization, the value for ThreadOfControl can be THREAD. If the database client does not allow threads to call its XA functions in this way, the value for ThreadOfControl must be PROCESS. The default is PROCESS. ThreadOfControl

Installable services page

The following table lists the attributes on the Installable services page of the Queue Manager properties dialog. The Installable services page displays information about the installable services installed on your computer. By default, only the authorization service, OAM, is shown. The attributes on the Installable services page relate to the Service stanza in the configuration files. For more information, see Configuring services and components in the IBM online IBM WebSphere MQ product documentation.

Attribute Meaning Stanza key
*Service name Read-only. This is the name of the service. Name
*Service entry points Read-only. This is the number of entry points that are defined for the service, including the initialization and termination entry points. EntryPoints
*Security policy Read-only. This is the security policy for the queue manager. Default means that the default security policy is used; NTSIDs Required means that a Windows security identifier is passed to the OAM when performing security checks. SecurityPolicy
*ServiceComponents Read-only. This is a list of the service components installed on your computer. ServiceComponents
*Name Read-only. This is the name of the component. component_name
*Service Read-only. This is the name of the installable service. service_name
*Data size Read-only. This is the size, in bytes, of the component data area passed to the component on each call. A value of 0 is used if no component data is required. size
*Module Read-only. This is the path to the module that contains the code for the component. module_name

Channels page

The following table lists the attributes that you can set on the Channels page of the Queue Manager properties dialog. To configure the behavior of the queue manager's channels, edit the attributes on the Channels page.

Distributed platforms, such as Windows, UNIX and Linux (x86 and x86-64 platforms)

On distributed platforms, the attributes on the Channels page relate to stanzas in the configuration files. You cannot edit this attributes on remote distributed queue managers.

Attribute Meaning Stanza key
*Max channels Type the maximum number of channels, from 1 to 9 999, that can be current (including server-connection channels with connected clients). For z/OS, the value must be between 1 and 9999, with a default value of 200. For all other platforms, the value must be between 1 and 65535, with a default value of 100. On a production system, you could use, for example, the value 1000. If the value of this attribute is reduced, any current channels that exceed the new limit continue to run until they stop. MaxChannels
*Max active channels Type the maximum number of channels that can be active at any one time. The default is the value specified for the MaxChannels attribute. For z/OS, the value must be between 1 and 9999. For all other platforms, the value must be between 1 and 65535. MaxActiveChannels
*Max initiators Type the maximum number of initiators allowed. The default and maximum value is 3. MaxInitiators
*MQI bind type Select the type of connection that channels use to connect to applications. To connect using a standard connection, click STANDARD; to connect without using an agent process, click FASTPATH. MQBindType
*Adopt new MCA This attribute specifies whether an orphaned MCA instance is adopted (restarted) when a new inbound channel request is detected that matches the value of the Adopt new MCA check attribute.

To adopt all channel types, type All. If a FASTPATH channel cannot be safely ended, it is not ended and the adoption fails.

If you do not require orphaned channels to be adopted, type No.		 AdoptNewMCAType
*Adopt new MCA check This attribute specifies which elements are checked to determine whether an MCA should be adopted when a new inbound channel is detected with the same name as an already active MCA. Type one or more of the following values separated by commas:
  • To check the queue manager name and the network address to prevent your channels from being inadvertently shut down, type ALL
  • To check the network address, type ADDRESS
  • To check the queue manager name, type NAME
  • To check the user ID that the queue manager is running under, type QM
  • To do no checking, type NONE
 AdoptNewMCACheck
*Adopt new MCA timeout Type the number of seconds, from 1 to 3600, that the new process must wait for the old process to end. The default value is 60. AdoptNewMCATimeout
*Pipeline length To allow an MCA to transfer messages using multiple threads, type the number of concurrent threads that the channel will use. The default is 1; if you type a value greater than 1, it is treated as 2. Make sure that you configure the queue manager at both ends of the channel to have a Pipeline length that is greater than 1. Pipelining is effective only for TCP/IP channels. PipeLineLength

TCP

The following table lists the attributes that you can set on the TCP page of the Queue Manager properties dialog. If the queue manager uses the TCP/IP transport protocol to communicate with other queue managers, edit the attributes on the TCP page. The attributes on the TCP page relate to stanzas in the configuration files.

Attribute Meaning Stanza key
*TCP port Type the port number for TCP/IP sessions. The default is 1414.
The TCP port setting sets the qm.ini TCP port stanza for the queue manager. This is used to control the two following things:
  1. A channel with a CONNAME that does not specify a port number uses this port number.
  2. The command: runmqlsr -t tcp -m YOUR_QM_NAME uses this port number where YOUR_QM_NAME is the name of your queue manager.
 Port
*TCP library 1 Type the name of the TCP/IP socket's DLL. The default is WSOCK32. Library1
*TCP library 2 If there are two TCP/IP sockets, type the name of the second TCP/IP socket's DLL; if there is only one TCP/IP socket, type the same name as for the TCP library 1 attribute. The default is WSOCK32. Library2
*TCP keepalive TCP can check periodically that the other end of the connection is still available. If the connection is not still available, the connection is closed. To configure TCP to perform these checks, click YES; to prevent TCP performing these checks, click NO. The default is YES. KeepAlive
*TCP listener backlog Type the maximum number of outstanding connection requests. The default value is -1 which resolves to the default value on the operating system. The default is 100 on Windows and Linux (x86 and x86-64 platforms). ListenerBackLog

LU6.2

The following table lists the attributes that you can set on the LU6.2 page of the Queue Manager properties dialog. If the queue manager uses the LU 6.2 transport protocol to communicate with other queue managers, edit the attributes on the LU6.2 page. The attributes on the LU6.2 page relate to stanzas in the configuration files.

Attribute Meaning Stanza key
*LU6.2 TP name Type the TP name to start on the remote site. TPName
*LU6.2 library 1 Type the name of the APPC DLL. The default is WCPIC32. Library1
*LU6.2 library 2 If there are two APPCs, type the name of the second APPC DLL; if there is only one APPC, type the same name as for the LU6.2 library 1 attribute. The default is WCPIC32. Library2
*LU6.2 local LU Type the name of the logical unit to use on local systems. LocalLU

NetBIOS

The following table lists the attributes that you can set on the NetBIOS page of the Queue Manager properties dialog. If the queue manager uses the NetBIOS transport protocol to communicate with other queue managers, edit the attributes on the NetBIOS page. The attributes on the NetBIOS page relate to stanzas in the configuration files.

Attribute Meaning Stanza key
*NetBIOS local name Type the name by which this computer will be known on the local area network (LAN). LocalName
*NetBIOS number of sessions Type the number of sessions to allocate. The default is 1. NumSession
*NetBIOS number of names Type the number of names to allocate. The default is 1. NumNames
*NetBIOS adapter number Type the number of the LAN adapter to use. The default is 0. AdapterNum
*NetBIOS number of commands Type the number of commands to allocate. The default is 1. NumCommands
*NetBIOS library 1 Type the name of the NetBIOS DLL. The default is NETAPI32. Library1

SPX

The following table lists the attributes that you can set on the SPX page of the Queue Manager properties dialog. If the queue manager uses the SPX transport protocol to communicate with other queue managers, edit the attributes on the SPX page. The attributes on the SPX page relate to stanzas in the configuration files.

Attribute Meaning Stanza key
*SPX socket Type the SPX socket number in hex. The default is SE86. Socket
*SPX library 1 Type the name of the SPX DLL. The default is WSOCK32. Library1
*SPX library 2 If there is a second SPX, type the name of the second SPX DLL; if there is only one SPX, type the same name as for the SPX library 1 attribute. The default is WSOCK32. Library2
*SPX keepalive SPX can check periodically that the other end of the connection is still available. If the connection is not still available, the connection is closed. To configure SPX to perform these checks, click YES; to prevent SPX performing these checks, click NO. The default is YES. KeepAlive
*SPX board number Type the number of the LAN adapter to use. The default is 0. BoardNum

Publish/Subscribe

The following table lists the attributes that you can set on the Publish/Subscribe page of the Queue Manager properties dialog. The Publish/Subscribe page replaces the cfgmqbrk application that was supplied with previous versions of IBM WebSphere MQ. To configure the queue manager for publish/subscribe messaging, edit the attributes on the Publish/Subscribe page. The attributes on the Publish/Subscribe page relate to stanzas in the configuration files. For more information about the individual stanzas, see Configuring services and components in the IBM online IBM WebSphere MQ product documentation.

Attribute Meaning MQSC Parameter
Publish/Subscribe mode The Publish/Subscribe mode is used to allow coexistence with Publish/Subscribe engines in IBM WebSphere MQ Version 6.0, WebSphere Message Broker V6, and WebSphere Event Broker V6. The three options are:

Compatibility which means that the V7 Publish/Subscribe engine is enabled, but the queued Publish/Subscribe interface is disabled. This means that the Publish/Subscribe engine can coexist with the Publish/Subscribe engines listed above. This is the default value for existing queue managers.

Enable which means that the V7 Publish/Subscribe engine is enabled and the queued Publish/Subscribe interface is enabled. This is the default value for newly created queue managers.

Disabled which means that all Publish/Subscribe functions are disabled.

 PSMODE
Message Retry Count The number of times that the channel retries to connect to the remote queue manager before it decides that it cannot deliver the message to the remote queue. This attribute controls the action of the MCA only if the Message retry exit name attribute is blank. If the Message retry exit name attribute is not blank, the value of the Message retry count attribute is passed to the exit for the exit's use but the number of times that the channel retries to connect is controlled by the exit, not by the Message retry count attribute. The maximum value is 999999999, and the default value is 5. MRRTY
Publish/Subscribe syncpoint This option defines whether messages will be processed under syncpoint. The two options are:

If persistent. The message is processed under syncpoint if the message is persistent. This is the default value.

Yes. All messages are processed under syncpoint.

 PSSYNCPT
Undelivered non-persistent input message This property defines what the Pub/Sub engine should do with non-persistent input messages that are not delivered. The two options are:

Discard. The undelivered non-persistent message is discarded. This is the default value.

Keep. The undelivered non-persistent message is not discarded. The Pub/Sub Engine will continue to retry to process this message at appropriate intervals and does not continue processing subsequent messages.

 PSNPMSG
Undelivered non-persistent response This property defines what the Pub/Sub engine should do with non-persistent responses that are not delivered. The four options are:

Discard. The undelivered non-persistent response is discarded if it cannot be placed on the reply queue.

Keep. The undelivered non-persistent response is not discarded or put on the dead-letter queue. The Pub/Sub Engine will back out the current operation and then retry it at appropriate intervals and does not continue processing subsequent messages.

Normal. Non-persistent responses which cannot be placed on the reply queue are put on the dead-letter queue. If they cannot be placed on the DLQ then they are discarded. This is the default value.

Safe. Non-persistent responses which cannot be placed on the reply queue are put on the dead-letter queue. If the response cannot be sent and cannot be placed on the dead-letter queue then the Pub/Sub Engine will back out of the current operation and then retry at appropriate intervals and does not continue processing subsequent messages.

 PSNPRES
Tree lifetime The lifetime, in seconds of non-administrative topics. When this non-administrative node no longer has any active subscriptions, this parameter determines how long the queue manager will wait before removing that node.

Only non-administrative topics that are in use by a durable subscription remain after the queue manager is recycled. Specify a value in the range 0 through 604000. A value of 0 means that non-administrative topics are not removed by the queue manager. The queue manager's initial default value is 1800.

TREELIFE
Parent The name of the parent queue manager to which the local queue manager is to connect as its child in a hierarchy. If the field is left empty, then the queue manager has no parent queue manager, and if there is an existing parent queue manager it is disconnected.

Before a queue manager can connect to a queue manager as its child in a hierarchy, channels must exist in both directions, between the parent queue manager and the child queue manager.

 PARENT
Publish exit path The module name containing the publish exit code. The maximum length of this field is 128 characters. The default is no publish exit. N/A
Publish exit function The name of the function entry point into the module containing the publish exit code. The maximum length of this field is 128 characters. N/A
Publish exit data If the queue manager is using a publish exit, it invokes the exit passing an MQPSXP structure as input. The data specified using this attribute is provided in the ExitData field. The maximum length of this field is 128 characters. The default is 32 blank characters. N/A
Publish/Subscribe clustering Controls whether this queue manager participates in Publish/Subscribe clustering. The two options are:

Enabled which means that this queue manager can participate in Publish/Subscribe clustering. This is the default value for newly created queue managers.

Disabled which means that this queue manager cannot participate in Publish/Subscribe clustering.

 PSCLUS