Home

 

Queue manager parameters

 

Queue manager parameters for the ALTER QMGR command.

ACCTCONO

Specifies whether applications can override the settings of the ACCTQ and ACCTMQI queue manager parameters:

DISABLED

Applications cannot override the settings of the ACCTQ and ACCTMQI parameters.

This is the queue manager's initial default value.

ENABLED

Applications can override the settings of the ACCTQ and ACCTMQI parameters by using the options field of the MQCNO structure of the MQCONNX API call.

Changes to this parameter are effective for connections to the queue manager that occur after the change.

This parameter is valid only on i5/OS, UNIX systems, and Windows.

ACCTINT(integer)

The time interval, in seconds, at which intermediate accounting records are written.

Specify a value in the range 1 through 604 800. The queue manager's initial default value is 1800.

Changes to this parameter are effective for connections to the queue manager that occur after the change.

This parameter is valid only on i5/OS, UNIX systems, and Windows.

ACCTMQI

Specifies whether accounting information for MQI data is to be collected:

OFF

MQI accounting data collection is disabled. This is the queue manager's initial default value.

ON

MQI accounting data collection is enabled.

If queue manager attribute ACCTCONO is set to ENABLED, the value of this parameter can be overridden using the options field of the MQCNO structure.

Changes to this parameter are effective for connections to the queue manager that occur after the change.

This parameter is valid only on i5/OS, UNIX systems, and Windows.

ACCTQ

Specifies whether accounting data is to be collected for all queues. On z/OS, the data collected is class 3 accounting data (thread-level and queue-level accounting).

OFF

Accounting data collection is disabled for all queues which specify QMGR as the value for their ACCTQ parameter. This is the queue manager's initial default value, except on z/OS where it is ON.

ON

Accounting data collection is enabled for all queues which specify QMGR as the value of their ACCTQ parameter. On z/OS systems, we need to have switched on class 3 accounting by the START TRACE command.

This is the queue manager's initial default value on z/OS.

NONE

Accounting data collection for all queues is disabled regardless of the value of the queue's ACCTQ parameter.
Changes to this parameter are effective only for connections to the queue manager occurring after the change to the parameter.
ACTCHL(integer)

The maximum number of channels that can be active at any time.

Specify a value in the range 1 through 9 999 but no greater than the value of MAXCHL. The queue manager's initial default value is 200.

For an explanation of which channel states are considered active, see WebSphere MQ Intercommunications.

If the value of this parameter is reduced, any current channels that exceed the new limit continue to run until they stop.

Changes to the ACTCHL parameter are only honored in a running channel initiator if the new value is less than or equal to the value of ACTCHL when the channel initiator was initialized. If the new value is greater than the value of ACTCHL when the channel initiator was initialized, the new value remains in the queue manager object and takes effect at the next channel initiator restart.

This parameter is valid on z/OS only.

ACTIVREC

Whether activity reports are generated if requested in the message:

DISABLED

Activity reports are not generated.

MSG

Activity reports are generated and sent to the reply queue specified by the originator in the message causing the report. This is the queue manager's initial default value.

QUEUE

Activity reports are generated and sent to SYSTEM.ADMIN.ACTIVITY.QUEUE.
For more information about activity reports, see WebSphere MQ Monitoring.
ADOPTCHK

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.

ALL

Check the queue manager name and the network address. Perform this check to prevent your channels from being inadvertently or maliciously shut down.

This is the queue manager's initial default value.

NETADDR

Check the network address.

NONE

Do no checking.

QMNAME

Check the queue manager name.

This parameter is valid on z/OS only.

Changes to this parameter take effect the next time that a channel attempts to adopt a channel.

ADOPTMCA

Whether an orphaned instance of an MCA should be restarted immediately when a new inbound channel request matching the ADOPTCHK parameter is detetcted:

ALL

Adopt all channel types.

This is the queue manager's initial default value.

NO

Adoption of orphaned channels is not required.

This parameter is valid on z/OS only

Changes to this parameter take effect the next time that a channel attempts to adopt a channel.

AUTHOREV

Whether authorization (Not Authorized) events are generated:

DISABLED

Authorization events are not generated. This is the queue manager's initial default value.

ENABLED

Authorization events are generated.

This value is not supported on z/OS.

BRIDGEEV

Whether IMS™ Bridge events are generated.

DISABLED

IMS Bridge events are not generated. This is the queue manager's initial default value.

ENABLED

All IMS Bridge events are generated.

This parameter is valid on z/OS only.

CCSID(integer)

The coded character set identifier for the queue manager. The CCSID is the identifier used with all character string fields defined by the API. It does not apply to application data carried in the text of messages unless the CCSID in the message descriptor is set to the value MQCCSI_Q_MGR when the message is put to a queue.

Specify a value in the range 1 through 65 535. The CCSID must specify a value that is defined for use on your platform, and use a character set that is appropriate to the platform.

If you use this parameter to change the CCSID, applications that are running when the change is applied continue to use the original CCSID. Because of this, stop and restart all running applications before you continue. This includes the command server and channel programs. To do this, stop and restart the queue manager after making the change.

This parameter is valid only on AIX, Compaq NSK, HP OpenVMS, HP-UX, Linux, i5/OS, Solaris, and Windows. See the WebSphere MQ Application Programming Guide for details of the supported CCSIDs for each platform.

CHAD

Whether receiver and server-connection channels can be defined automatically:

DISABLED

Auto-definition is not used. This is the queue manager's initial default value.

ENABLED

Auto-definition is used.

Cluster-sender channels can always be defined automatically, regardless of the setting of this parameter.

This parameter is valid only on AIX, HP OpenVMS, HP-UX, Linux, i5/OS, Solaris, and Windows.

CHADEV

Whether channel auto-definition events are generated.

DISABLED

Auto-definition events are not generated. This is the queue manager's initial default value.

ENABLED

Auto-definition events are generated.

This parameter is valid only on AIX, HP OpenVMS, HP-UX, Linux, i5/OS, Solaris, and Windows.

CHADEXIT(string)

Auto-definition exit name.

If this name is nonblank, the exit is called when an inbound request for an undefined receiver, server-connection, or cluster-sender channel is received. It is also called when starting a cluster-receiver channel.

The format and maximum length of the name depends on the environment:

  • On Windows, it is of the form dllname(functionname) where dllname is specified without the suffix (".DLL"). The maximum length is 128 characters.

  • On i5/OS, it is of the form: 
          progname libname
    where program name occupies the first 10 characters and libname the second 10 characters (both blank-padded to the right if necessary). The maximum length of the string is 20 characters.

  • On AIX, HP OpenVMS, HP-UX, Linux, and Solaris, it is of the form libraryname(functionname). The maximum length is 128 characters.

  • On z/OS, it is a load module name, the maximum length is 8 characters.

This parameter is valid only on AIX, HP OpenVMS, HP-UX, Linux, i5/OS, Solaris, Windows, and z/OS. On z/OS, it applies only to cluster-sender and cluster-receiver channels.

CHIADAPS(integer)

The number of channel initiator adapter subtasks to use for processing WebSphere MQ calls.

Specify a value in the range zero through 9 999. The queue manager's initial default value is 8.

Suggested settings:

Test system 8 (default)
Production system 30

This parameter is valid on z/OS only.

Changes to this parameter take effect when the channel initiator is restarted.

For a discussion of the relationship between CHIADAPS, CHIDISPS and MAXCHL, see ALTER QMGR to customize the channel initiator to suit your requirements.">Task 18: Tailor the channel initiator parameters.

CHIDISPS(integer)

The number of dispatchers to use in the channel initiator.

Specify a value in the range 1 through 9 999. The queue manager's initial default value is 5.

Suggested settings:

Test system 5 (default)
Production system 20

This parameter is valid on z/OS only.

Changes to this parameter take effect when the channel initiator is restarted.

For a discussion of the relationship between CHIADAPS, CHIDISPS and MAXCHL, see ALTER QMGR to customize the channel initiator to suit your requirements.">Task 18: Tailor the channel initiator parameters.

CHISERVP

This parameter is reserved for use by IBM use only; it is not for general use.

This parameter is valid on z/OS only.

CHLEV

Whether channel events are generated.

DISABLED

Channel events are not generated. This is the queue manager's initial default value.

ENABLED

All channel events are generated.

EXCEPTION

All exception channel events are generated.
CLWLDATA(string)

Cluster workload exit data. The maximum length of the string is 32 characters.

This string is passed to the cluster workload exit when it is called.

This parameter is valid only on AIX, HP OpenVMS, HP-UX, Linux, i5/OS, Solaris, Windows, and z/OS.

CLWLEXIT(string)

Cluster workload exit name.

If this name is nonblank, the exit is called when a message is put to a cluster queue. The format and maximum length of the name depends on the environment:

  • On UNIX systems and HP OpenVMS, it is of the form libraryname(functionname). The maximum length is 128 characters.

  • On Windows, it is of the form dllname(functionname), where dllname is specified without the suffix (".DLL"). The maximum length is 128 characters.

  • On z/OS, it is a load module name. The maximum length is 8 characters.

  • On i5/OS, it is of the form: 
          progname libname
    where program name occupies the first 10 characters and libname the second 10 characters (both blank-padded to the right if necessary). The maximum length is 20 characters.

This parameter is valid only on AIX, HP OpenVMS, HP-UX, Linux, i5/OS, Solaris, Windows, and z/OS.

CLWLLEN(integer)

The maximum number of bytes of message data that is passed to the cluster workload exit.

Specify a value:

  • in the range zero through 100 MB on WebSphere MQ for z/OS systems

  • in the range zero through 999 999 999 on other platforms

The initial default value is 100.

This parameter is valid only on AIX, HP OpenVMS, HP-UX, Linux, i5/OS, Solaris, Windows and z/OS.

CLWLMRUC(integer)

The maximum number of most recently used outbound cluster channels.

Specify a value in the range 1 through 999 999 999.

The initial default value is 999 999 999.

For more information about this attribute, see WebSphere MQ Queue Manager Clusters.

CLWLUSEQ

For queues whose CLWLUSEQ parameter has a value of QMGR, specifies the behavior of an MQPUT operation when the target queue has a local instance and at least one remote cluster instance (except where the MQPUT originates from a cluster channel).

Specify either:

LOCAL

The local queue is the only target for MQPUT operations. This is the queue manager's initial default value.

ANY

The queue manager treats the local queue as another instance of the cluster queue for the purposes of workload distribution.

For more information about this attribute, see WebSphere MQ Queue Manager Clusters.

CMDEV

Specifies whether command events are generated:

DISABLED

Command events are not generated. This is the queue manager's initial default value.

ENABLED

Command events are generated for all successful commands.

NODISPLAY

Command events are generated for all successful commands, other than DISPLAY commands.
This parameter is valid on z/OS only.

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.

*

The command is executed on the local queue manager and is also passed to every active queue manager in the queue-sharing group. The effect of this is the same as entering the command on every queue manager in the queue-sharing group.

CONFIGEV

Whether configuration events are generated:

ENABLED

Configuration events are generated. After setting this value, issue REFRESH QMGR TYPE(CONFIGEV) commands for all objects to bring the queue manager configuration up-to-date.

DISABLED

Configuration events are not generated. This is the queue manager's initial default value.
This parameter is valid on z/OS only.
DEADQ(string)

The local name of a dead-letter queue (or undelivered-message queue) on which messages that cannot be routed to their correct destination are put.

The queue named must be a local queue. See Rules for naming WebSphere MQ objects.

DEFXMITQ(string)

Local name of the default transmission queue on which messages 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. See Rules for naming WebSphere MQ objects.

DESCR(string)

Plain-text comment. It provides descriptive information about the queue manager.

It should contain only displayable characters. The maximum length of the string is 64 characters. In a DBCS installation, it can contain DBCS characters (subject to a maximum length of 64 bytes).

If characters are used that are not in the coded character set identifier (CCSID) for this queue manager, they might be translated incorrectly if the information is sent to another queue manager.

DNSGROUP(string)

The name of the group that the TCP listener handling inbound transmissions for the queue-sharing group should join when using Workload Manager for Dynamic Domain Name Services support (WLM/DNS).

The maximum length of this parameter is eighteen characters.

If this name is blank, the queue-sharing group name is used.

This parameter is valid on z/OS only.

Changes to this parameter take effect for listeners that are subsequently started. Listeners that are currently started are unaffected by changes to this parameter.

DNSWLM

Whether the TCP listener that handles inbound transmissions for the queue-sharing group should register with WLM/DNS:

NO

The listener is not to register with Workload Manager. This is the queue manager's initial default value.

YES

The listener is to register with Workload Manager.

This parameter is valid on z/OS only.

Changes to this parameter take effect for listeners that are subsequently started. Listeners that are currently started are unaffected by changes to this parameter.

EXPRYINT

Specifies how often queues are scanned to discard expired messages:

OFF

Queues are not scanned. No internal expiry processing is performed. This is the default.

integer

The approximate interval in seconds at which queues are scanned. Each time that the expiry interval is reached, the queue manager looks for candidate queues that are worth scanning to discard expired messages.

The queue manager maintains information about the expired messages on each queue, and therefore whether a scan for expired messages is worthwhile. So, only a selection of queues is scanned at any time.

The value must be in the range 1 through 99 999 999. The minimum scan interval used is 5 seconds, even if you specify a lower value.

You must set the same EXPRYINT value for all queue managers within a queue-sharing group that support this attribute. Shared queues are scanned by only one queue manager in a queue-sharing group, and this is either the first queue manager to restart or the first queue manager to have had the EXPRYINT value set.

Changes to EXPRYINT take effect when the current interval expires, unless the new interval is less than the unexpired portion of the current interval, in which case a scan is scheduled immediately and the new interval value takes immediate effect.

This parameter is valid only on z/OS.

IGQ

Whether intra-group queuing is used.

This parameter is valid only on z/OS when the queue manager is a member of a queue-sharing group.

ENABLED

Message transfer between queue managers within a queue-sharing group uses the shared transmission queue (SYSTEM.QSG.TRANSMIT.QUEUE).

DISABLED

Message transfer between queue managers within a queue-sharing group uses non-shared transmission queues and channels. This is the same mechanism used for message transfer between queue managers that are not part of a queue-sharing group. This is the default value.

If intra-group queuing has been enabled, but the intra-group queuing agent has stopped for some reason, we can issue ALTER QMGR IGQ(ENABLED) to restart it.

IGQAUT

Specifies the type of authority checking and, therefore, the user IDs, to be used by the IGQ agent (IGQA). This establishes the authority to put messages to a destination queue.

This parameter is valid only on z/OS when the queue manager is a member of a queue-sharing group.

DEF

Indicates that the default user ID should be used to establish authority to put messages to a destination queue. This is the default value.

For one user ID check, this involves using the user ID (referred to as QSGSEND) of the queue manager within the queue-sharing group that put the messages to the SYSTEM.QSG.TRANSMIT.QUEUE.

For two user ID checks, this involves using the QSGSEND user ID and the IGQ user ID.

CTX

Indicates that the user ID from the UserIdentifier field in the message descriptor, of a message on the SYSTEM.QSG.TRANSMIT.QUEUE, should be used to establish authority to put messages to a destination queue.

For one user ID check, this involves using the QSGSEND user ID.

For two user ID checks, this might involve using the QSGSEND user ID, the IGQ user ID and the alternate user id (referred to as ALT) taken from the UserIdentifier field in the message descriptor of a message on the SYSTEM.QSG.TRANSMIT.QUEUE.

ONLYIGQ

Indicates that only the IGQ user ID should be used to establish authority to put messages to a destination queue.

For all ID checks, this involves using the IGQ user ID.

ALTIGQ

Indicates that the IGQ user ID and the ALT user ID should be used to establish authority to put messages to a destination queue.

For one user ID check, this uses the IGQ user ID.

For two user ID checks, this uses the IGQ user ID and the ALT user ID.

IGQUSER

Nominates a user ID (referred to as the IGQ user ID) to be used by the IGQ agent (IGQA) to establish authority to put messages to a destination queue.

This parameter is valid only on z/OS when the queue manager is a member of a queue-sharing group. Possible values are:

Blanks

This is the default value for the IGQ user ID and indicates that the user ID of the receiving queue manager within the QSG should be used.

Specific user ID

Indicates that the user ID specified in the receiving queue manager’s IGQUSER parameter should be used.

  1. As the receiving queue manager has authority to all queues it can access, this means that security checking might not be performed for this user ID type.

  2. As the default value of blanks has a special meaning, we cannot use IGQUSER to specify a real user ID of blanks.

INHIBTEV

Whether inhibit (Inhibit Get and Inhibit Put) events are generated:

ENABLED

Inhibit events are generated.

DISABLED

Inhibit events are not generated. This is the queue manager's initial default value.
IPADDRV

Specifies which IP protocol is to be used for channel connections.

IPV4

The IPv4 IP address is to be used. This is the queue manager's initial default value.

IPV6

The IPv6 IP address is to be used.

This parameter is used only in systems running IPv4 and IPv6 and it only applies to channels defined with a TRPTYPE of TCP when either of the following two conditions is true:

  • The channel's CONNAME parameter contains a hostname that resolves to both an IPv4 and an IPv6 address, and the LOCLADDR parameter is not specified.

  • The value of the channel's CONNAME and LOCLADDR parameters is a hostname that resolves to both an IPv4 and IPv6 address.

LOCALEV

Whether local error events are generated:

ENABLED

Local error events are generated.

DISABLED

Local error events are not generated. This is the queue manager's initial default value.

LOGGEREV

Whether recovery log events are generated:

DISABLED

Logger events are not generated. This is the queue manager's initial default value.

ENABLED

Logger events are generated.

This parameter is valid only on AIX, HP-UX, Linux, i5/OS, Solaris, and Windows.

LSTRTMR(integer)

The time interval, in seconds, between attempts by WebSphere MQ to restart a listener after an APPC or TCP/IP failure. When the listener is restarted on TCP/IP, it uses the same port and IP address as it used when it first started.

Specify a value in the range 5 through 9 999. The queue manager's initial default value is 60.

This parameter is valid on z/OS only.

Changes to this parameter take effect for listeners that are subsequently started. Listeners that are currently started are unaffected by changes to this parameter.

LUGROUP(string)

The generic LU name to be used by the LU 6.2 listener that handles inbound transmissions for the queue-sharing group. The maximum length of this parameter is 8 characters.

If this name is blank, the listener cannot be used.

This parameter is valid on z/OS only.

Changes to this parameter take effect for listeners that are subsequently started. Listeners that are currently started are unaffected by changes to this parameter.

LUNAME(string)

The name of the LU to use for outbound LU 6.2 transmissions. Set this to be the same as the name of the LU to be used by the listener for inbound transmissions. The maximum length of this parameter is 8 characters.

If this name is blank, the APPC/MVS default LU name should be used. This is variable, so LUNAME should always be set if you are using LU 6.2

This parameter is valid on z/OS only.

Changes to this parameter take effect when the channel initiator is restarted.

LU62ARM(string)

The suffix of the APPCPM member of SYS1.PARMLIB. This suffix nominates the LUADD for this channel initiator. When automatic restart manager (ARM) restarts the channel initiator, the z/OS command SET APPC=xx is issued.

If you do not provide a value for this parameter, no SET APPC=xx command is issued.

The maximum length of this parameter is 2 characters.

This parameter is valid on z/OS only.

Changes to this parameter take effect when the channel initiator is restarted.

LU62CHL(integer)

The maximum number of channels that can be current, or clients that can be connected, that use the LU 6.2 transmission protocol.

Specify a value in the range zero through 9 999 but no greater than the value of MAXCHL. If you specify zero, the LU 6.2 transmission protocol is not used. The queue manager's initial default value is 200.

This parameter is valid on z/OS only.

If the value of this parameter is reduced, any current channels that exceed the new limit continue to run until they stop.

MAXCHL(integer)

The maximum number of channels that can be current (including server-connection channels with connected clients).

Specify a value in the range zero through 9 999. The queue manager's initial default value is 200. Suggested settings:

Test system 200 (default)
Production system 1000

For an explanation of which channel states are considered current, see WebSphere MQ Intercommunications.

If the value of this parameter is reduced, any current channels that exceed the new limit continue to run until they stop.

Changes to the MAXCHL parameter are only honored in a running channel initiator if the new value is less than or equal to the value of MAXCHL when the channel initiator was initialized. If the new value is greater than the value of MAXCHL when the channel initiator was initialized, the new value remains in the queue manager object and takes effect at the next channel initiator restart.

This parameter is valid on z/OS only.

For a discussion of the relationship between CHIADAPS, CHIDISPS, and MAXCHL, see ALTER QMGR to customize the channel initiator to suit your requirements.">Task 18: Tailor the channel initiator parameters.

MAXHANDS(integer)

The maximum number of open handles that any one connection can have at the same time.

This is a value in the range zero through 999 999 999.

On WebSphere MQ for Compaq NonStop Kernel, this parameter is ignored.

MAXMSGL(integer)

The maximum length of messages allowed on queues for this queue manager.

This is in the range 32 KB through 100 MB. The default is 4 MB (4 194 304 bytes).

You can use any queue as a shared queue for storing long messages, if its MAXMSGL attribute is set to a value greater than 63 KB. The CFLEVEL parameter of an associated coupling facility structure does not impose any restrictions.

If you reduce the maximum message length for the queue manager, also reduce the maximum message length of the SYSTEM.DEFAULT.LOCAL.QUEUE definition, and all other queues connected to the queue manager. This ensures that the queue manager’s limit is not less than that of any of the queues associated with it. If you do not do this, and applications inquire only the value of the queue’s MAXMSGL, they might not work correctly.

This parameter is valid only on AIX, HP OpenVMS, HP-UX, Linux, i5/OS, Solaris, and Windows.

MAXUMSGS(integer)

The maximum number of uncommitted messages within a syncpoint.

This is a limit on

  • The number of messages that can be retrieved, plus

  • The number of messages that can be put

within any single syncpoint. It does not apply to messages that are put or retrieved outside syncpoint.

The number includes any trigger messages and report messages generated within the same unit of recovery.

Be aware that reducing the value of MAXUMSGS may cause problems to existing applications and queue manager processes, such as clustering on z/OS, if they are already using a higher value.

Specify a value in the range 1 through 999 999 999.

On WebSphere MQ for Compaq NonStop Kernel, this parameter is ignored.

MONACLS

Controls the collection of online monitoring data for auto-defined cluster-sender channels:

QMGR

Collection of online monitoring data is inherited from the setting of the queue manager's MONCHL parameter. This is the queue manager's initial default value.

OFF

Monitoring for the channel is switched off.

LOW

Unless MONCHL is NONE, monitoring is switched on with a low rate of data collection with a minimal impact on system performance. The data collected is not likely to be the most current.

MEDIUM

Unless MONCHL is NONE, monitoring is switched on with a moderate rate of data collection with limited impact on system performance.

HIGH

Unless MONCHL is NONE, monitoring is switched on with a high rate of data collection with a likely impact on system performance. The data collected is the most current available.

A change to this parameter takes effect only on channels started after the change occurs. Any channel started before the change to the parameter continues with the value in force at the time that the channel started.

MONCHL

Controls the collection of online monitoring data for channels.

OFF

Online monitoring data collection is turned off for channels specifying a value of QMGR in their MONCHL parameter. This is the queue manager's initial default value.

NONE

Online monitoring data collection is turned off for channels regardless of the setting of their MONCHL parameter.

LOW

Online monitoring data collection is turned on, with a low ratio of data collection, for channels specifying a value of QMGR in their MONCHL parameter.

MEDIUM

Online monitoring data collection is turned on, with a moderate ratio of data collection, for channels specifying a value of QMGR in their MONCHL parameter.

HIGH

Online monitoring data collection is turned on, with a high ratio of data collection, for channels specifying a value of QMGR in their MONCHL parameter.

A change to this parameter takes effect only on channels started after the change occurs. Any channel started before the change to the parameter continues with the value in force at the time that the channel started.

MONQ

Controls the collection of online monitoring data for queues.

OFF

Online monitoring data collection is turned off for queues specifying a value of QMGR in their MONQ parameter. This is the queue manager's initial default value.

NONE

Online monitoring data collection is turned off for queues regardless of the setting of their MONQ parameter.

LOW

Online monitoring data collection is turned on, with a low ratio of data collection, for queues specifying a value of QMGR in their MONQ parameter.

MEDIUM

Online monitoring data collection is turned on, with a moderate ratio of data collection, for queues specifying a value of QMGR in their MONQ parameter.

HIGH

Online monitoring data collection is turned on, with a high ratio of data collection, for queues specifying a value of QMGR in their MONQ parameter.

Changes to this parameter take immediate effect on the collection of monitoring data for the affected queues.

OPORTMAX(integer)

The maximum value in the range of port numbers to be used when binding outgoing channels. When all the port numbers in the specified range have been used, outgoing channels bind to any available port number.

Specify a value in the range zero through 65 535. The queue manager's initial default value is zero and this means that all outgoing channels bind to any available port number.

Specify a corresponding value for OPORTMIN to define a range of port numbers and ensure that the value you specify for OPORTMAX is greater than or equal to the value you specify for OPORTMIN.

This parameter is valid on z/OS only.

Changes to this parameter take effect for channels that are subsequently started. Channels that are currently started are unaffected by changes to this parameter.

OPORTMINinteger)

The minimum value in the range of port numbers to be used when binding outgoing channels. When all the port numbers in the specified range have been used, outgoing channels bind to any available port number.

Specify a value in the range zero through 65 535. The queue manager's initial default value is zero.

Specify a corresponding value for OPORTMAX to define a range of port numbers and ensure that the value you specify for OPORTMIN is less than or equal to the value you specify for OPORTMAX.

This parameter is valid on z/OS only.

Changes to this parameter take effect for channels that are subsequently started. Channels that are currently started are unaffected by changes to this parameter.

PERFMEV

Whether performance-related events are generated:

ENABLED

Performance-related events are generated.

DISABLED

Performance-related events are not generated. This is the queue manager's initial default value.

On WebSphere MQ for z/OS all the queue managers in a queue-sharing group must have the same setting.

RCVTIME(integer)

The approximate length of time that a TCP/IP channel waits to receive data, including heartbeats, from its partner before returning to the inactive state. This parameter applies only to message channels (and not to MQI channels).

This number can be qualified as follows:

  • To specify that this number is a multiplier to be applied to the negotiated HBINT value to determine how long a channel is to wait, set RCVTTYPE to MULTIPLY. Specify an RCVTIME value of zero or in the range 2 through 99. If you specify zero, the channel does not time out its wait to receive data from its partner.

  • To specify that this number is a value, in seconds, to be added to the negotiated HBINT value to determine how long a channel is to wait, set RCVTTYPE to ADD. Specify an RCVTIME value in the range 1 through 999 999.

  • To specify that this number is a value, in seconds, that the channel is to wait, set RCVTTYPE to EQUAL. Specify an RCVTIME value in the range zero through 999 999. If you specify zero, the channel does not time out its wait to receive data from its partner.

The queue manager's initial default is zero.

This parameter is valid on z/OS only.

Changes to this parameter take effect for channels that are subsequently started. Channels that are currently started are unaffected by changes to this parameter.

RCVTMIN(integer)

The minimum length of time that a TCP/IP channel waits to receive data, including heartbeats, from its partner before returning to an inactive state. This parameter applies only to message channels (and not to MQI channels).

If you use RCVTTYPE to specify that the TCP/IP channel wait time is relative to the negotiated value of HBINT and the resultant value is less than the value of this parameter, then the value of this parameter is used.

Specify a value, in seconds, between zero and 999 999. The queue manager's initial default is zero.

This parameter is valid on z/OS only.

Changes to this parameter take effect for channels that are subsequently started. Channels that are currently started are unaffected by changes to this parameter.

RCVTTYPE

The qualifier to apply to the value in RCVTIME.

MULTIPLY

Specifies that RCVTIME is a multiplier to be applied to the negotiated HBINT value to determine how long a channel will wait. This is the queue manager's initial default.

ADD

Specifies that RCVTIME is a value, in seconds, to be added to the negotiated HBINT value to determine how long a channel will wait.

EQUAL

Specifies that RCVTIME is a value, in seconds, representing how long the channel will wait.

This parameter is valid on z/OS only.

Changes to this parameter take effect for channels that are subsequently started. Channels that are currently started are unaffected by changes to this parameter.

REMOTEEV

Whether remote error events are generated:

DISABLED

Remote error events are not generated. This is the queue manager's initial default value.

ENABLED

Remote error events are generated.
If you are using the reduced function form of WebSphere MQ for z/OS supplied with WebSphere Application Server, only DISABLED is valid.
REPOS(clustername)

The name of a cluster for which this queue manager provides a repository manager service. The maximum length is 48 characters conforming to the rules for naming WebSphere MQ objects.

No more than one of the resultant values of REPOS can be nonblank.

If you use the REPOS parameter to create a full repository queue manager, use cluster-sender channels to connect it to at least one other full repository queue manager in the cluster. See the information in WebSphere MQ Queue Manager Clusters for details about using cluster-sender channels with full repository queue managers.

This parameter is valid only on AIX, HP OpenVMS, HP-UX, Linux, i5/OS, Solaris, Windows, and z/OS.

REPOSNL(nlname)

The name of a namelist of clusters for which this queue manager provides a repository manager service.

No more than one of the resultant values of REPOSNL can be nonblank.

If both REPOS and REPOSNL are blank, or REPOS is blank and the namelist specified by REPOSNL is empty, this queue manager does not have a full repository, but might be a client of other repository services that are defined in the cluster.

If you use the REPOSNL parameter to create a full repository queue manager, use cluster-sender channels to connect it to at least one other full repository queue manager in each cluster specified in the namelist. See the information in WebSphere MQ Queue Manager Clusters for details about using cluster-sender channels with full repository queue managers.

This parameter is valid only on AIX, HP OpenVMS, HP-UX, Linux, i5/OS, Solaris, Windows, and z/OS.

ROUTEREC

Whether trace-route information is recorded if requested in the message. If participation in route tracing is enabled by this queue manager parameter not being set to DISABLED, the value of the parameter is only important should a reply be generated. The reply goes either to SYSTEM.ADMIN.TRACE.ROUTE.QUEUE, or to the destination specified by the message itself. Provided ROUTEREC is not DISABLED, messages not yet at the final destination may have information added to them.

DISABLED

Trace-route information is not recorded.

MSG

Trace-route information is recorded and sent to the destination specified by the originator of the message causing the trace route record. This is the queue manager's initial default value.

QUEUE

Trace-route information is recorded and sent to SYSTEM.ADMIN.TRACE.ROUTE.QUEUE.
For more information about trace-route records, see WebSphere MQ Monitoring.
SCHINIT

Whether the channel initiator should start automatically when the queue manager starts.

QMGR

The channel initiator will start automatically when the queue manager starts.

This is the default value.

MANUAL

The channel initiator will not start automatically.

This parameter is valid only on AIX, HP-UX, Linux, i5/OS, Solaris, and Windows.

SCMDSERV

Whether the command server should start automatically when the queue manager starts.

QMGR

The command server will start automatically when the queue manager starts.

This is the default value.

MANUAL

The command server will not start automatically.

This parameter is valid only on AIX, HP-UX, Linux, i5/OS, Solaris, and Windows.

QQMNAME

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 SQQMNAME attribute specifies whether the ObjectQmgrName is used or whether the processing queue manager opens the shared queue directly.

USE

The ObjectQmgrName is used, and the appropriate transmission queue is opened.

IGNORE

The processing queue manager opens the shared queue directly. This can reduce the traffic in your queue manager network.

This parameter is valid only on z/OS.

SSLCRLNL(nlname)

The name of a namelist of authentication information objects to be used for Certificate Revocation List (CRL) checking by the queue manager.

If SSLCRLNL is blank, CRL checking is not invoked.

Changes to SSLCRLNL, or to the names in a previously specified namelist, or to previously referenced authentication information objects become effective either:

SSLCRYP(string)

Sets the name of the parameter string required to configure the cryptographic hardware present on the system.

The string can have one of the following values:

  • GSK_ACCELERATOR_RAINBOW_CS_OFF

  • GSK_ACCELERATOR_RAINBOW_CS_ON

  • GSK_ACCELERATOR_NCIPHER_NF_OFF

  • GSK_ACCELERATOR_NCIPHER_NF_ON

  • GSK_PKCS11=<the PKCS #11 driver path and filename>;<the PKCS #11 token label>;<the PKCS #11 token password>;<symmetric cipher setting>;

The strings containing RAINBOW enable or disable the Rainbow CryptoSwift cryptographic hardware.

The strings containing NCIPHER enable or disable the nCipher nFast cryptographic hardware.

To use cryptographic hardware which is accessed using the PKCS #11 interface, specify the string containing PKCS11. The PKCS #11 driver path is an absolute path to the shared library providing support for the PKCS #11 card. The PKCS #11 driver filename is the name of the shared library. An example of the value required for the PKCS #11 driver path and filename is /usr/lib/pkcs11/PKCS11_API.so

To access symmetric cipher operations through GSKit, specify the symmetric cipher setting parameter on the PKCS11 string. The value of this parameter is either:

SYMMETRIC_CIPHER_OFF

Do not access symmetric cipher operations.

SYMMETRIC_CIPHER_ON

Access symmetric cipher operations.
If the symmetric cipher setting parameter is not specified, this has the same effect as specifying SYMMETRIC_CIPHER_OFF.

The maximum length of the string is 256 characters. The default value is blank.

If you specify a string that does not begin with one of the cryptographic strings listed above, you get an error. If you specify the GSK_PKCS11 string, the syntax of the other parameters is also checked.

When the SSLCRYP value is changed, the cryptographic hardware parameters specified become the ones used for new SSL connection environments. The new information becomes effective:

  • When a new channel process is started.

  • For channels that run as threads of the channel initiator, when the channel initiator is restarted.

  • For channels that run as threads of the listener, when the listener is restarted.

  • When a REFRESH SECURITY TYPE(SSL) command is issued.

SSLEV

Whether SSL events are generated.

DISABLED

SSL events are not generated. This is the queue manager's initial default value.

ENABLED

All SSL events are generated.
SSLFIPS

This parameter is valid only on Windows and UNIX platforms.

SSSLFIPS specifies whether only FIPS-certified algorithms are to be used if cryptography is carried out in WebSphere MQ. If cryptographic hardware is configured, the cryptographic modules used are those provided by the hardware product, and these may, or may not, be FIPS-certified to a particular level. This depends on the hardware product in use. For more information about FIPS, see the WebSphere MQ Security manual.

NO

WebSphere MQ provides an implementation of SSL cryptography which supplies FIPS-certified modules for all V6.0 platforms. If you set SSLFIPS to NO, any CipherSpec supported on a particular platform can be used. This is the queue manager's initial default value.

If the queue manager runs without using cryptographic hardware, the following CipherSpecs run using FIPS 140–2 certified cryptography:

  • TLS_RSA_WITH_DES_CBC_SHA

  • TLS_RSA_WITH_3DES_EDE_CBC_SHA

  • FIPS_WITH_DES_CBC_SHA

  • FIPS_WITH_3DES_EDE_CBC_SHA

  • TLS_RSA_WITH_AES_128_CBC_SHA

  • TLS_RSA_WITH_AES_256_CBC_SHA

YES

Specifies that only FIPS-certified algorithms are to be used in the CipherSpecs allowed on all SSL connections from and to this queue manager.

Inbound and outbound SSL channel connections succeed only if one of the following CipherSpecs is used:

  • TLS_RSA_WITH_DES_CBC_SHA

  • TLS_RSA_WITH_3DES_EDE_CBC_SHA

  • FIPS_WITH_DES_CBC_SHA

  • FIPS_WITH_3DES_EDE_CBC_SHA

  • TLS_RSA_WITH_AES_128_CBC_SHA

  • TLS_RSA_WITH_AES_256_CBC_SHA

SSLKEYR(string)

The name of the Secure Sockets Layer key repository.

The maximum length of the string is 256 characters.

The format of the name depends on the environment:

  • On z/OS, it is the name of a key ring.

  • On i5/OS, it is of the form pathname/keyfile, where keyfile is specified without the suffix (.kdb), and identifies a GSKit key database file. The default value is /QIBM/UserData/ICSS/Cert/Server/Default.

    If you specify *SYSTEM, WebSphere MQ utilizes the system certificate store as the key repository for the queue manager. As a result, the queue manager is registered as a server application in Digital Certificate Manager (DCM) and we can assign any server/client certificate in the system store to this application.

    If you change the SSLKEYR parameter to a value other than *SYSTEM, WebSphere MQ deregisters the queue manager as an application with DCM.

  • On UNIX it is of the form pathname/keyfile and on Windows pathname\keyfile, where keyfile is specified without the suffix (.kdb), and identifies a GSKit key database file. The default value for UNIX platforms is /var/mqm/qmgrs/QMGR/ssl/key, and on Windows it is C:\\IBM\WebSphere MQ\qmgrs\QMGR\ssl\key, where QMGR is replaced by the queue manager name (on UNIX and Windows).

On i5/OS, Windows and UNIX systems, the syntax of this parameter is validated to ensure that it contains a valid, absolute, directory path.

If SSLKEYR is blank, or is set to a value that does not correspond to a key ring or key database file, channels using SSL fail to start.

Changes to SSLKEYR become effective either:

SSLRKEYC(integer)

The number of unencrypted bytes to be sent and received within an SSL conversation before the secret key is renegotiated. The number of bytes includes control information.

This value is used only by SSL channels which initiate communication from the queue manager (for example, the sender channel in a sender and receiver channel pairing).

If a value greater than zero is specified and channel heartbeats are enabled for the channel, the secret key is also renegotiated before message data is sent or received following a channel heartbeat. The count of bytes until the next secret key renegotiation is reset after each successful renegotiation.

Specify a value in the range zero through 999 999 999. A value of zero (the queue manager's initial default value) means that the secret key is never renegotiated.

Attention: Non-zero values less than 4096 (4Kb) may cause channels to fail to start, or may cause inconsistencies in the values of SSLKEYDA, SSLKEYTI, and SSLRKEYS.

SSLTASKS(integer)

The number of server subtasks to use for processing SSL calls. To use SSL channels, have at least two of these tasks running.

This parameter is valid only on z/OS.

This is in the range zero through 9999. To avoid problems with storage allocation, do not set the SSLTASKS parameter to a value greater than 50.

Changes to this parameter will be effective when the channel initiator is restarted.

STATACLS

Whether statistics data is to be collected for auto-defined cluster-sender channels:

QMGR

Collection of statistics data is inherited from the setting of the queue manager's STATCHL parameter. This is the queue manager's initial default value.

OFF

Statistics data collection for the channel is switched off.

LOW

Unless STATCHL is NONE, statistics data collection is switched on with a low ratio of data collection with a minimal impact on system performance.

MEDIUM

Unless STATCHL is NONE, statistics data collection is switched on with a moderate ratio of data collection.

HIGH

Unless STATCHL is NONE, statistics data collection is switched on with a high ratio of data collection.

This parameter is valid only on i5/OS, UNIX systems, and Windows.

A change to this parameter takes effect only on channels started after the change occurs. Any channel started before the change to the parameter continues with the value in force at the time that the channel started.

STATCHL

Whether statistics data is to be collected for channels:

NONE

Statistics data collection is turned off for channels regardless of the setting of their STATCHL parameter. This is the queue manager's initial default value.

OFF

Statistics data collection is turned off for channels specifying a value of QMGR in their STATCHL parameter.

LOW

Statistics data collection is turned on, with a low ratio of data collection, for channels specifying a value of QMGR in their STATCHL parameter.

MEDIUM

Statistics data collection is turned on, with a moderate ratio of data collection, for channels specifying a value of QMGR in their STATCHL parameter.

HIGH

Statistics data collection is turned on, with a high ratio of data collection, for channels specifying a value of QMGR in their STATCHL parameter.

This parameter is valid only on i5/OS, UNIX systems, and Windows.

A change to this parameter takes effect only on channels started after the change occurs. Any channel started before the change to the parameter continues with the value in force at the time that the channel started.

STATINT(integer)

The time interval, in seconds, at which statistics monitoring data is written to the monitoring queue.

Specify a value in the range 1 through 604 800. The queue manager's initial default value is 1800.

This parameter is valid only on AIX, HP-UX, Linux, i5/OS, Solaris, and Windows.

Changes to this parameter take immediate effect on the collection of monitoring and statistics data.

STATMQI

Whether statistics monitoring data is to be collected for the queue manager:

OFF

Data collection for MQI statistics is disabled. This is the queue manager's initial default value.

ON

Data collection for MQI statistics is enabled.

This parameter is valid only on i5/OS, UNIX systems, and Windows.

Changes to this parameter take immediate effect on the collection of monitoring and statistics data.

STATQ

Whether statistics data is to be collected for queues:

NONE

Statistics data collection is turned off for queues regardless of the setting of their STATQ parameter. This is the queue manager's initial default value.

OFF

Statistics data collection is turned off for queues specifying a value of QMGR in their STATQ parameter.

ON

Statistics data collection is turned on for queues specifying a value of QMGR in their STATQ parameter.

This parameter is valid only on i5/OS, UNIX systems, and Windows.

Changes to this parameter take immediate effect on the collection of statistics data for the affected queues.

STRSTPEV

Whether start and stop events are generated:

ENABLED

Start and stop events are generated. This is the queue manager's initial default value.

DISABLED

Start and stop events are not generated.
TCPCHL(integer)

The maximum number of channels that can be current, or clients that can be connected, that use the TCP/IP transmission protocol.

The maximum number of sockets used is the sum of the values in TCPCHL and CHIDISPS. The z/OS OpenEdition MAXFILEPROC parameter (specified in the BPXPRMxx member of SYS1.PARMLIB) controls how many sockets each task is allowed, and thus how many channels each dispatcher is allowed. In this case, the number of channels using TCP/IP is limited to the value of MAXFILEPROC multiplied by the value of CHIDISPS.

Specify a value in the range zero through 9 999 but no greater than the value of MAXCHL (although note that TCP/IP might not support as many as 9 999 channels). If you specify zero, the TCP/IP transmission protocol is not used. The queue manager's initial default is 200.

If the value of this parameter is reduced, any current channels that exceed the new limit continue to run until they stop.

This parameter is valid on z/OS only.

TCPKEEP

Specifies whether the KEEPALIVE facility is to be used to check that the other end of the connection is still available. If it is not available, the channel is closed.

NO

The TCP KEEPALIVE facility is not to be used. This is the queue manager's initial default value.

YES

The TCP KEEPALIVE facility is to be used as specified in the TCP profile configuration data set. The interval is specified in the KAINT channel attribute.

This parameter is valid on z/OS only.

Changes to this parameter take effect for channels that are subsequently started. Channels that are currently started are unaffected by changes to this parameter.

TCPNAME(string)

The name of either the only, or default, TCP/IP system to be used, depending on the value of TCPSTACK. This is the name of the z/OS OpenEdition stack for TCP/IP, as specified in the SUBFILESYSTYPE NAME parameter in the BPXPRMxx member of SYS1.PARMLIB. The queue manager's initial default value is 'TCPIP'.

The maximum length of this parameter is 8 characters.

This parameter is valid on z/OS only.

Changes to this parameter take effect when the channel initiator is restarted.

TCPSTACK

Specifies whether the channel initiator may use only the TCP/IP address space specified in TCPNAME, or may optionally bind to any selected TCP/IP address.

SINGLE

The channel initiator may only use the TCP/IP address space specified in TCPNAME. This is the queue manager's default value.

MULTIPLE

The channel initiator may use any TCP/IP address space available to it. It defaults to the one specified in TCPNAME if no other is specified for a channel or listener.

This parameter is valid on z/OS only.

Changes to this parameter take effect when the channel initiator is restarted.

TRAXSTR

Specifies whether the channel initiator trace should start automatically:

YES

Channel initiator trace is to start automatically. This is the queue manager's default value.

NO

Channel initiator trace is not to start automatically.

This parameter is valid on z/OS only.

Changes to this parameter take effect when the channel initiator is restarted. If you wish to start or stop channel initiator trace without restarting the channel initiator, use the START TRACE or STOP TRACE commands after the channel initiator has started.

TRAXTBL(integer)

The size, in megabytes, of the channel initiator's trace data space.

Specify a value in the range 2 through 2048. The queue manager's initial default value is 2.

This parameter is valid on z/OS only.

  1. Changes to this parameter take effect immediately; any existing trace table contents are lost.

  2. When you use large z/OS data spaces, ensure that sufficient auxiliary storage is available on your system to support any related z/OS paging activity. You might also need to increase the size of your SYS1.DUMP data sets.

TRIGINT(integer)

A time interval expressed in milliseconds.

The TRIGINT parameter is relevant only if the trigger type (TRIGTYPE) is set to FIRST (see DEFINE QLOCAL for details). In this case trigger messages are normally generated only when a suitable message arrives on the queue, and the queue was previously empty. Under certain circumstances, however, an additional trigger message can be generated with FIRST triggering even if the queue was not empty. These additional trigger messages are not generated more often than every TRIGINT milliseconds. See the WebSphere MQ Application Programming Guide for more information.

Specify a value in the range zero through 999 999 999.

 

Parent topic:

Parameter descriptions


sc10620_


 

Home