What's changed in IBM MQ 9.2.0 Fix Pack 2

IBM® MQ 9.2.0 Fix Pack 2 includes a number of resource changes.

Java clients installed with the self-extracting JAR file can use the JMSAdmin tool
Changes to channel status attributes
JMQI updates for local address field set on an MQCD object
Channel object migration code update to fix channel definition migration issue
Change to OCSPTimeout parameter
Additional InstallPATH option for the crtmqfp command
Change to Managed File Transfer delimiter transfer error messages

Java clients installed with the self-extracting JAR file can use the JMSAdmin tool

From IBM MQ 9.2.0 Fix Pack 2, the self-extracting JAR file version-IBM-MQ-Install-Java-All.jar has been updated to include all of the files related to the JMSAdmin tool, in addition to all of the files that it did before. As a result of these changes, a client that is installed using the self-extracting JAR file can use the JMSAdmin tool installed as part of the JAR file to create JMS administered objects within a file system context (.bindings file). The client can also look up and use these administered objects. For more information, see Obtaining the IBM MQ classes for JMS separately.

Note: A client installed by unpacking the redistributable Java client does not contain the JMSAdmin tool, or its prerequisite JAR files fscontext.jar and providerutil.jar. For more information, see Limitations and other considerations for redistributable clients.

Changes to channel status attributes

From IBM MQ 9.2.0 Fix Pack 2, the following changes have been made to channel status attributes:

DISPLAY CHSTATUS command: If the value for BYTSSENT or BYTSRCVD exceeds 999999999, it wraps to zero.
Inquire Channel Status (response): If the value for BytesSent or BytesReceived exceeds 999999999, it wraps to zero.

JMQI updates for local address field set on an MQCD object

From IBM MQ 9.2.0 Fix Pack 2, the Java Message Queueing Interface (JMQI) has been updated to ensure that the local address field is set on an MQCD object after a channel instance has been created and is connected to a queue manager. This means that when a channel exit written in Java calls the method MQCD.getLocalAddress(), the method returns the local address that the channel instance is using.

Channel object migration code update to fix channel definition migration issue

Before IBM MQ 9.2.0 Fix Pack 2, if you migrate from IBM MQ 8.0.0 Fix Pack 1, IBM MQ 8.0.0 Fix Pack 2, or IBM MQ 8.0.0 Fix Pack 3 directly to IBM MQ 9.1.5 or later, channel objects are not migrated correctly when the queue manager is started at the new code level. Channels continue to work normally, but channel names are not displayed by the runmqsc command or IBM MQ Explorer.

From IBM MQ 9.2.0 Fix Pack 2, channel definitions are migrated correctly when the queue manager is started for the first time at the new code level. See also Queue manager migration.

Change to OCSPTimeout parameter

From IBM MQ 9.2.0 Fix Pack 2, if a value of 0 is set for the OCSPTimeout parameter in the SSL stanza of the qm.ini or mqclient.ini configuration file, the default timeout of 30 seconds is used.

Additional InstallPATH option for the crtmqfp command

From IBM MQ 9.2.0 Fix Pack 2, when installing a maintenance update with the crtmqfp command, you can use the additional option InstallPATH. The update is the installed directly into the directory specified by InstallPATH. For more information, see Applying maintenance level updates on Linux® using RPM.

[MQ 9.2.0 Jul 2020] From IBM MQ 9.2.0, the InstallPATH option is also available with the crtmqpkg command. For more information, see Multiple IBM MQ installations.

Change to Managed File Transfer delimiter transfer error messages

From IBM MQ 9.2.0 Fix Pack 2 only one empty message is sent when a transfer from a file fails due to a delimiter size check failure. See Failure of a file-to-message transfer for more details.