The value can be:
This is the queue manager's initial default value.
This parameter is valid only on AIX, HP-UX, Linux, i5/OS, Solaris, and Windows.
Specify a value in the range 1 through 604 000.
This parameter is valid only on AIX, HP-UX, Linux, i5/OS, Solaris, and Windows.
The value can be:
For more information about activity reports, see Monitoring WebSphere MQ.
The value can be:
This parameter applies to z/OS only.
Specify whether an orphaned MCA instance is to be adopted when a new inbound channel request is detected matching the AdoptNewMCACheck parameters.
The value can be:
This parameter applies to z/OS only.
The value can be:
The value can be:
Auto-definition for cluster-sender channels is always enabled.
This parameter is supported in the following environments: AIX, HP-UX, i5/OS, Solaris, Windows and Linux.
The value can be:
This parameter is supported in the following environments: AIX, HP-UX, i5/OS, Solaris, Windows and Linux.
The value can be:
This exit is invoked when an inbound request for an undefined channel is received, if:
This exit is also invoked when a cluster-receiver channel is started.
The format of the name is the same as for the SecurityExit parameter described in Change, Copy and Create Channel.
The maximum length of the exit name depends on the environment in which the exit is running. MQ_EXIT_NAME_LENGTH gives the maximum length for the environment in which your application is running. MQ_MAX_EXIT_NAME_LENGTH gives the maximum for all supported environments.
This parameter is supported in the following environments: AIX, HP-UX, i5/OS, Solaris, Windows, Linux, and z/OS. On z/OS, it applies only to cluster-sender and cluster-receiver channels.
The value can be:
The value can be:
This parameter is valid only on AIX, HP-UX, Linux, i5/OS, Solaris, and Windows.
The value can be:
The value can be:
This parameter is valid only on AIX, HP-UX, Linux, i5/OS, Solaris, and Windows.
The number of adapter subtasks to use for processing WebSphere MQ calls. This parameter applies to z/OS only.
Specify a value in the range 1 through 9 999. The queue manager's initial default value is 8.
The number of dispatchers to use for the channel initiator. This parameter applies to z/OS only.
Specify a value in the range 1 through 9 999. The queue manager's initial default value is 5.
This parameter applies to z/OS only.
The value can be:
This parameter applies to z/OS only.
Specify a value in the range 2 through 2048. The queue manager's initial default value is 2.
This parameter applies to z/OS only.
Specifies the value to be used for the ChannelMonitoring attribute of automatically defined cluster-sender channels. The value can be:
The value can be:
This parameter is valid only on AIX, HP-UX, Linux, i5/OS, Solaris, and Windows.
This is passed to the cluster workload exit when it is called.
The maximum length of the string is MQ_EXIT_DATA_LENGTH.
If a nonblank name is defined this exit is invoked when a message is put to a cluster queue.
The format of the name is the same as for the SecurityExit parameter described in Change, Copy and Create Channel.
The maximum length of the exit name depends on the environment in which the exit is running. MQ_EXIT_NAME_LENGTH gives the maximum length for the environment in which your application is running. MQ_MAX_EXIT_NAME_LENGTH gives the maximum for all supported environments.
This parameter is supported only in the environments in which an MQSeries(R) Version 5.1 product, or later, is available.
The maximum length of the message passed to the cluster workload exit.
The value of this attribute must be in the range 0 through 999 999 999.
The maximum number of active most recently used outbound channels.
Specify a value in the in the range 1 through 999 999 999.
Specifies whether a cluster queue manager is to use remote puts to other queues defined in other queue managers within the cluster during workload management.
Specify either:
The coded character set identifier (CCSID) for the queue manager. The CCSID is the identifier used with all character string fields defined by the application programming interface (API). It does not apply to application data carried in the text of a message unless the CCSID in the message descriptor, when the message is put with an MQPUT or MQPUT1, is set to the value MQCCSI_Q_MGR.
Specify a value in the range 1 through 65 535.
The CCSID must specify a value that is defined for use on the platform and use an appropriate character set. The character set must be:
Stop and restart the queue manager after execution of this command so that all processes reflect the changed CCSID of the queue manager.
This parameter is supported in the following environments: AIX, Compaq NonStop Kernel, HP OpenVMS, HP-UX, i5/OS, Solaris, Windows and Linux.
The value can be:
Specifies how the command is executed when the queue manager is a member of a queue-sharing group. You can specify one of the following:
The maximum length is MQ_QSG_NAME_LENGTH.
The value can be:
The value can be:
Specifies the name of the local queue that is to be used for undelivered messages. Messages are put on this queue if they cannot be routed to their correct destination. The maximum length of the string is MQ_Q_NAME_LENGTH.
This is the name of the default transmission queue that is used for the transmission of messages to remote queue managers, if there is no other indication of which transmission queue to use.
The maximum length of the string is MQ_Q_NAME_LENGTH.
Specify 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). This parameter applies to z/OS only.
The maximum length of the string is MQ_DNS_GROUP_NAME_LENGTH.
The value can be:
This parameter applies to z/OS only.
Specifies the frequency with which the queue manager scans the queues looking for expired messages. Specify a time interval in seconds in the range 1 through 99 999 999, or the following special value:
The minimum scan interval used is 5 seconds, even if you specify a lower value.
Specifies whether the command will be forced to complete if both of the following are true:
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. The value can be:
The user identifier used for authorization is the value of the UserIdentifier field in the separate MQMD that is associated with the message when the message is on the shared transmission queue. This is the user identifier of the program that placed the message on the shared transmission queue, and is usually the same as the user identifier under which the remote queue manager is running.
If the RESLEVEL profile indicates that more than one user identifier is to be checked, the user identifier of the local IGQ agent (IGQUserId) is also checked.
The user identifier used for authorization is the value of the UserIdentifier field in the separate MQMD that is associated with the message when the message is on the shared transmission queue. This is the user identifier of the program that placed the message on the shared transmission queue, and is usually the same as the user identifier under which the remote queue manager is running.
If the RESLEVEL profile indicates that more than one user identifier is to be checked, the user identifier of the local IGQ agent (IGQUserId) and the value of the UserIdentifier field in the embedded MQMD are also checked. The latter user identifier is usually the user identifier of the application that originated the message.
The user identifier used for authorization is the user identifier of the local IGQ agent (IGQUserId).
If the RESLEVEL profile indicates that more than one user identifier is to be checked, this user identifier is used for all checks.
The user identifier used for authorization is the user identifier of the local IGQ agent (IGQUserId).
If the RESLEVEL profile indicates that more than one user identifier is to be checked, the value of the UserIdentifier field in the embedded MQMD is also checked. This user identifier is usually the user identifier of the application that originated the message.
Specifies the user identifier that is associated with the local intra-group queuing agent. This identifier is one of the user identifiers that may be checked for authorization when the IGQ agent puts messages on local queues. The actual user identifiers checked depend on the setting of the IGQPutAuthority attribute, and on external security options.
The maximum length is MQ_USER_ID_LENGTH.
The value can be:
Specifies whether intra-group queuing is used. The value can be:
Specifies which IP address version, either IPv4 or IPv6, is used. The value can be:
The time interval, in seconds, between attempts by WebSphere MQ to restart the listener after an APPC or TCP/IP failure. This parameter applies to z/OS only.
Specify a value in the range 5 through 9 999. The queue manager's initial default value is 60.
The value can be:
The value can be:
This is valid only on AIX, HP-UX, i5/OS, Solaris, Linux, and Windows.
The generic LU name to be used by the LU 6.2 listener that handles inbound transmissions for the queue-sharing group. This parameter applies to z/OS only.
The maximum length of the string is MQ_LU_NAME_LENGTH.
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. This parameter applies to z/OS only.
The maximum length of the string is MQ_LU_NAME_LENGTH.
The suffix of the APPCPM member of SYS1.PARMLIB. This suffix nominates the LUADD for this channel initiator. This parameter applies to z/OS only.
The maximum length of the string is MQ_ARM_SUFFIX_LENGTH.
The maximum number of channels that can be current, or clients that can be connected, that use the LU 6.2 transmission protocol. This parameter applies to z/OS only.
Specify a value in the range zero through 9 999. The queue manager's initial default value is 200.
The maximum number of channels that can be active at any time. This parameter applies to z/OS only.
Specify a value in the range 1 through 9 999. The queue manager's initial default value is 200.
The maximum number of channels that can be current (including server-connection channels with connected clients). This parameter applies to z/OS only.
Specify a value in the range 1 through 9 999.
The maximum number of handles that any one connection can have open at the same time.
Specify a value in the range 0 through 999 999 999.
Specifies the maximum length of messages allowed on queues on the queue manager. No message that is larger than either the queue's MaxMsgLength or the queue manager's MaxMsgLength can be put on a queue.
If you reduce the maximum message length for the queue manager, you must also reduce the maximum message length of the SYSTEM.DEFAULT.LOCAL.QUEUE definition, and your other queues, to ensure that the queue manager's limit is not less than that of any of the queues in the system. If you do not do this, and applications inquire only the value of the queue's MaxMsgLength, they might not work correctly.
The lower limit for this parameter is 32 KB (32 768 bytes). The upper limit depends on the environment:
Specifies the maximum number of uncommitted messages. That is:
under any one syncpoint. This limit does not apply to messages that are retrieved or put outside syncpoint.
Specify a value in the range 1 through 10 000.
The value can be:
This parameter is valid only on AIX, HP-UX, Linux, i5/OS, Solaris, and Windows.
The value can be:
This parameter is valid only on AIX, HP-UX, Linux, i5/OS, Solaris, and Windows.
The maximum value in the range of port numbers to be used when binding outgoing channels. This parameter applies to z/OS only.
Specify a value in the range zero through 65 535. The queue manager's initial default value is zero.
Specify a corresponding value for OutboundPortMin and ensure that the value of OutboundPortMax is greater than or equal to the value of OutboundPortMin.
The minimum value in the range of port numbers to be used when binding outgoing channels. This parameter applies to z/OS only.
Specify a value in the range zero through 65 535. The queue manager's initial default value is zero.
Specify a corresponding value for OutboundPortMax and ensure that the value of OutboundPortMin is less than or equal to the value of OutboundPortMax.
The value can be:
This is text that briefly describes the object.
The maximum length of the string is MQ_Q_MGR_DESC_LENGTH.
Use characters from the character set identified by the coded character set identifier (CCSID) for the queue manager on which the command is executing, to ensure that the text is translated correctly.
The value can be:
If the QueueMonitoring queue attribute is set to MQMON_Q_MGR, this attribute specifies the value which is assumed by the channel. The value can be:
The value can be:
This parameter is valid only on AIX, HP-UX, Linux, i5/OS, Solaris, and Windows.
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 to z/OS only and only to message channels (and not to MQI channels). This number can be qualified as follows:
The minimum 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 to z/OS only.
Specify a value in the range zero through 999 999.
The qualifier to apply to ReceiveTimeoutType to calculate how long a TCP/IP channel waits to receive data, including heartbeats, from its partner before returning to the inactive state. This parameter applies to z/OS only.
The value can be:
The value can be:
The name of a cluster for which this queue manager provides a repository manager service.
The maximum length of the string is MQ_OBJECT_NAME_LENGTH.
No more than one of the resultant values of RepositoryName can be nonblank.
The name, of a namelist of clusters, for which this queue manager provides a repository manager service.
This queue manager does not have a full repository, but can be a client of other repository services that are defined in the cluster, if
No more than one of the resultant values of RepositoryNameList can be nonblank.
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. This parameter is valid only on z/OS.
The value can be:
The length of the string is MQ_NAMELIST_NAME_LENGTH.
Indicates the name of a namelist of authentication information objects to be used for CRL checking by the queue manager.
If SSLCRLNamelist is blank, CRL checking is not invoked.
Changes to SSLCRLNamelist, or to the names in a previously specified namelist, or to previously referenced authentication information objects become effective:
The length of the string is MQ_SSL_CRYPTO_HARDWARE_LENGTH.
Sets the name of the parameter string required to configure the cryptographic hardware present on the system.
This parameter is supported on AIX, HP-UX, Solaris, Linux, and Windows(R) only.
The string can have one of the following values:
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, you must 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:
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 SSLCryptoHardware value is changed, the cryptographic hardware parameters specified become the ones used for new SSL connection environments. The new information becomes effective:
The value can be:
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. This parameter applies to Windows and UNIX platforms only.
The value can be:
If the queue manager runs without using cryptographic hardware, the following CipherSpecs run using FIPS 140-2 certified cryptography:
Inbound and outbound SSL channel connections succeed only if one of the following CipherSpecs is used:
The length of the string is MQ_SSL_KEY_REPOSITORY_LENGTH.
Indicates the name of the Secure Sockets Layer key repository.
The format of the name depends on the environment:
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 you 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 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 SSLKeyRepository become effective:
Specifies when SSL channel MCAs that initiate communication reset the secret key used for encryption on the channel. The value of this parameter represents the total number of unencrypted bytes that are sent and received on the channel before the secret key is renegotiated. This number of bytes includes control information sent by the MCA.
The secret key is renegotiated when (whichever occurs first):
Specify a value in the range zero through 999 999 999. A value of zero, the queue manager's initial default value, signifies that secret keys are never renegotiated.
The number of server subtasks to use for processing SSL calls. To use SSL channels, you must have at least two of these tasks running.
Specify a value in the range zero through 9 999. However, to avoid problems with storage allocation, do not set this parameter to a value greater than 50.
The value can be:
Specify a value in the range 1 through 604 000.
This parameter is valid only on AIX, HP-UX, Linux, i5/OS, Solaris, and Windows.
Specify a value in the range zero and 9 999. The queue manager's initial default value is 200.
This parameter applies to z/OS only.
The value can be:
This parameter applies to z/OS only.
The maximum length of the string is MQ_TCP_NAME_LENGTH.
This parameter applies to z/OS only.
The value can be:
This parameter applies to z/OS only.
The value can be:
If participation in route tracing is enabled using this queue manager attribute (by the attribute being not set to MQRECORDING_DISABLED) then the value of the attribute is only important should a reply be generated. The reply should go either to SYSTEM.ADMIN.TRACE.ROUTE.QUEUE, or to the destination specified by the message itself. Provided the attribute is not disabled then messages not yet at the final destination may have information added to them. For more information about trace-route records, see Monitoring WebSphere MQ.
Specifies the trigger time interval, expressed in milliseconds, for use only with queues where TriggerType has a value of MQTT_FIRST.
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 MQTT_FIRST triggering, even if the queue was not empty. These additional trigger messages are not generated more often than every TriggerInterval milliseconds.
Specify a value in the range 0 through 999 999 999.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqzac0476 |