Title: IBM MQ 9.1.0 for z/OS Upgrade Information
Filter: All User Comms
Scope: All North American SMCs
Issue Date: Immediately
Effective Date: Immediately
Group Name: Software Services Mainframe MQ
Affected Locations: All North American SMCs
Please see the contact information below if you have any questions regarding this User Communication.
Summary:
Currently, most DXC locations are running WMQ V8.0.0. This user communication provides planning information for sites in preparation for the IBM MQ 9.1.0 for z/OS upgrade.
Actual upgrade dates will be determined with each account using normal change management processes. Upgrades will be performed in an account’s test MQ subsystem prior to production to allow for application testing.
Justification:
IBM MQ 9.1.0 for z/OS will allow DXC to maintain the current level of technology.
IBM MQ V9.1.0 introduces new enhancements over IBM MQ 8.0.0, and also includes fixes for known problems.
Currently, most DXC locations are running Websphere MQ V8.0.0 for z/OS. This user communication provides planning information for sites in preparation for the 2020 rollout of IBM MQ V9.1.0 for z/OS.
Actual upgrade dates will be determined with each account using normal change management processes. MQ Capabilities will test this upgrade on a 'sandbox' system first to verify the installation and to make sure the MQ system starts and is operational. The upgrade will then be applied to the development regions where accounts should verify their applications are still functioning properly. After the application teams complete their testing, the software will be installed in production. The accounts should then verify their applications are still functioning properly in the production environment.
Benefits to Users:
This information is being communicated to ensure planning occurs and all prerequisites are addressed for a smooth and timely transition.
IBM® MQ Version 9.1.0 delivers improved scaling and flexibility, making it even better at supporting large-scale messaging enterprise solutions. Since we are directly upgrading from IBM MQ V8.0.0 to IBM MQ V9.1.0 while skipping the upgrade to V9.0.0 the section below lists new functions and changes that were introduced with both IBM MQ V9.0.0 and IBM MQ V9.1.0 that are available with the current new release of IBM MQ V9.1.0.
Details:
Accounts are responsible for verifying any Account owned and maintained software is compatible with IBM MQ 9.1.0.
V9.0 New Features z/os.
For Version 9.0.0, IBM® MQ for z/OS® delivers additional data manager pageset statistics and new IBM z/OS Management Facility (z/OSMF) workflows and templates that enable simplified queue manager and queue manager resource provisioning. Version 9.0 also delivers a number of features that were previously made available in Version 8.0 fix packs. These features include the use of JMS in a CICS® OSGi JVM server and IMS, enforcing lower expiration times in messages, and increasing the number of active log data sets.
• Data manager page set statistics
• JMS support within CICS OSGI Server
• JMS support within IMS Server
• Improved control of messages by using message expiry
• Increased number of active logs
• Using IBM z/OSMF to automate IBM MQ
Data manager page set statistics
IBM MQ Version 9.0 provides new pageset usage information within existing queue manager SMF records to facilitate better management of local queues within a queue manager by recording information such as pageset input-output rates and highest usage. For more information, see Data manager pageset data records.
JMS support within CICS OSGI Server
Standards-based messaging support for applications that run within the CICS OSGI Server (CICS Transaction Server Version 5.2 or later) environment is provided through the use of IBM MQ classes for JMS. For more information, see Using IBM MQ classes for JMS in a CICS OSGi JVM server.
JMS support within IMS Server
Standards-based messaging support within an IMS Version 13 environment is provided through the use of IBM MQ classes for JMS. For more information, see Using IBM MQ classes for JMS in IMS.
Improved control of messages by using message expiry
An override capability for message expiry within a queue manager is provided through the use of the CAPEXPRY attribute. This capability is available for point-to-point messaging or publish and subscribe. For more information, see Enforcing lower expiration times.
Increased number of active logs
The number of active logs that are available to be defined to a single queue manager is increased from 31 to up to a maximum of 310. This increases the availability of a queue manager in failure scenarios. For more information, see Log data set definitions.
Using IBM z/OSMF to automate IBM MQ
From IBM MQ Version 9.0, you can use the IBM z/OS Management Facility (z/OSMF) to more easily manage the day-to-day operations of IBM MQ. For more information, see Using IBM z/OSMF to automate IBM MQ.
V9.0 New Family Features
IBM® MQ Version 9.0.0 delivers a new mode of operation and also support for non-IBM Java™ runtime environments (JREs) for Advanced Message Security, web addressable access to the Client Channel Definition Table (CCDT), support for the IBM MQ Version 9.0 resource adapter in WebSphere® Application Server traditional, enhanced Unicode data support across all platforms, and logging enhancements for the Protocol Bridge Agent in Managed File Transfer.
• Additional quality of protection for AMS
• Web addressable access to the client channel definition table (CCDT)
• AMS supported in non-IBM JREs in Java clients
• Updated Resource Adapter for traditional WebSphere Application Server
• Enhanced Unicode data conversion support
• Managed File Transfer Protocol Bridge Agent logging enhancements
Additional quality of protection for AMS
To complement the existing Integrity and Privacy privacy policies, Advanced Message Security (AMS) provides a new, third alternative, Confidentiality (Encryption only with optional key reuse), in IBM MQ Version 9.0.
Significant CPU cost savings can be made with Confidentiality policies through symmetric key reuse. This new mode of operation continues to use the PKCS#7 format to share a symmetric encryption key. However, there is no digital signature, which eliminates some of the per message asymmetric key operations. The symmetric key still needs to be encrypted with asymmetric key operations for each recipient, but the symmetric key can be optionally reused over multiple messages that are destined for the same recipients. If key reuse is permitted by policy, then only the first message requires asymmetric key operations. Subsequent messages only need to use symmetric key operations. For more information, see Qualities of protection available with AMS.
Web addressable access to the client channel definition table (CCDT)
IBM MQ Version 9.0 improves the ability for clients to remain connected to IBM MQ queue managers by hosting the CCDT in a central location that is accessible through a URI, removing the need to individually update the CCDT for each deployed client. A client channel definition table can be located through a URL in any of the following ways:
• By programming using MQCNO
• By using environment variables
• By using mqclient.ini file stanzas.
NoteYou can use the environment variable option only for native programs connecting as clients, that is C, COBOL, or C++ applications. The environment variables have no effect for Java, JMS or managed .NET applications.
For more information, see Web addressable access to the client channel definition table.
AMS supported in non-IBM JREs in Java clients
In earlier releases, the AMS relied on IBM-provided encryption packages that were included in the Java runtime environment (JRE) or Java Secure Socket Extension (JSSE) shipped with IBM MQ and other IBM products.
From Version 9.0, the AMS has been redesigned to use an alternative crypto library, the open source Bouncy Castle implementation, which is built into the IBM MQ classes for Java and IBM MQ classes for JMS, not the JRE. This means that you can now use alternative JREs without needing to install additional libraries. For more information, see Support for non-IBM JREs.
Updated Resource Adapter for traditional WebSphere Application Server
The IBM MQ Version 9.0 resource adapter is pre-installed within WebSphere Application Server traditional Version 9.0. Therefore, there is no requirement to install a new resource adapter.
NoteAn IBM MQ Version 9.0 resource adapter can connect in CLIENT or BINDINGS transport mode to any in-service IBM MQ queue manager.
Enhanced Unicode data conversion support
From Version 9.0, IBM MQ supports all Unicode characters defined in the Unicode 8.0 standard in data conversion, including full support for UTF-16. For more information, see Data conversion.
In addition, a new file ccsid_part2.tbl is provided, which takes precedence over the ccsid.tbl file and:
• Allows you to add or modify CCSID entries
• Specify default data conversion
• Specify data for different command levels
The ccsid_part2.tbl file is applicable to the following platforms only:
• Linux - all versions
• Solaris
• Windows
For more information, see The ccsid_part2.tbl file.
Managed File Transfer Protocol Bridge Agent logging enhancements
From Version 9.0, Managed File Transfer provides a new logging feature to capture interactions between the Protocol Bridge Agent and FTP/SFTP/FTPS file servers. The agent log is set to a level that enables the collection of first hand diagnostic information. Logging is enabled and disabled by using the new command fteSetAgentLogLevel or by using the agent.properties file.
For more information, see fteSetAgentLogLevel and The agent.properties file.
V9.0 Changes:
DISPLAY SYSTEM command
The DISPLAY SYSTEM command has been changed to display the level of new functions that are available, in addition to the version of IBM MQ for z/OS® that the queue manager can fall back to.
Stabilization of IBM MQ classes for Java
IBM will make no further enhancements to the IBM MQ classes for Java and they are functionally stabilized at the level shipped in IBM MQ Version 8.0. Existing applications that use the IBM MQ classes for Java will continue to be fully supported, but this API is stabilized, so new features will not be added and requests for enhancements rejected. Fully supported means that defects will be fixed together with any changes necessitated by changes to IBM MQ System Requirements.
Removal of Managed File Transfer Web Gateway support
Before Version 9.0, the Managed File Transfer Web Gateway allowed you to transfer files to Managed File Transfer agents and retrieve transfer status using a HTTP client. The Web Gateway was deprecated at IBM MQ Version 8.0, and is removed at Version 9.0.
The fteCreateWebAgent command is removed at Version 9.0. If you attempt to migrate a web agent from an earlier release to Version 9.0, an error message is displayed to explain that the migration of a web agent is not supported (see fteMigrateAgent (migrate a WebSphere MQ File Transfer Edition Version 7.0 agent to IBM WebSphere MQ Version 7.5 or later).
Deprecation of IBM MQ transport for SOAP
From Version 9.0, the IBM MQ transport for SOAP is deprecated. This includes the following product features:
• IBM MQ Java™ Listener
• IBM MQ .NET 1 and 2 Listener
• IBM MQ Java Axis2 Client
• IBM MQ Java client (deprecation already announced in Version 8.0)
• IBM MQ .NET 1 and 2 clients (deprecation already announced in Version 8.0)
• IBM MQ bridge for HTTP (deprecation already announced in Version 8.0)
Deprecation of useJNDI activation specification property
The useJNDI property is deprecated at IBM MQ Version 9.0 as the DestinationLookup property is equivalent and is the JMS 2.0 specification defined way of implementing the same function. For more information, see Configuring the resource adapter for inbound communication.
Deprecation of IBM MQ support for MicrosoftActive X and Microsoft Visual Basic 6.0
IBM MQ support for MicrosoftActive X and Microsoft Visual Basic 6.0 is deprecated. IBM MQ classes for .NET are the recommended replacement technology. See Using the Component Object Model Interface (IBM MQ Automation Classes for ActiveX) and Coding in Visual Basic.
Removal of IBM Cloud Product Insights support
The IBM Cloud Product Insights service is no longer available. Therefore IBM MQ support for this service is no longer relevant. For more information, see this blog post: Service Deprecation: IBM Cloud Product Insights.
Prerequiste Changes For Version 9.0.
IBM® MQ for z/OS® Version 9.0 requires z/OS Version 2.1 or higher.
Advanced Message Security, when configured to use the new quality of protection, CONFIDENTIALITY, with encryption algorithm (ENCALG) AES256 requires IBM System z10 or later hardware. For more information about this new quality of protection, see Qualities of protection available with AMS.
For more information on supported operating systems, system requirements, prerequisites, and optional supported software, see the System Requirements for IBM MQ Version 9.0 web page.
From IBM® MQ for z/OS® Version 9.0.0, exits that rely upon being able to modify static storage within the load module must be modified to be reentrant.
Writing channel exit programs on z/OS stipulates that IBM MQ exits must be reentrant and capable of running anywhere in virtual storage.
Non-reentrant C programs are those that might use variables declared with the static storage class, or variables receiving the extern storage class, or might contain writable static strings.
Non-reentrant exits have, technically, never been supported in IBM MQ for z/OS, but prior to IBM MQ for z/OS Version 9.0.0, it was possible for some of these exits to process successfully
From IBM MQ for z/OS Version 9.0.0, exits that rely upon being able to modify static storage within the load module no longer function correctly. You should modify such exits to be reentrant.
You might achieve this in some cases by:
• Moving static or global variables inside the scope of a function, or
• Dynamically allocating storage used for any static variables and using, for example, the IBM MQ ExitUserArea, or other operating system facilities, such as name or token services to obtain addressability.
The DISPLAY SYSTEM command has been changed to display the level of new functions that are available, in addition to the version of IBM MQ for z/OS that the queue manager can fall back to.
Changes to CONNSWAP
From IBM® MQ Version 9.0, setting this keyword has no effect.
V9.1 New Features z/os.
For Version 9.1.0, IBM® MQ for z/OS® delivers a number of new features and enhancements that are available with base product entitlement, and with Advanced entitlement. These features include an updated IBM MQ resource adapter, improved workload balancing options for shared queues, and the ability, with the IBM MQ for z/OS Service Provider for IBM z/OS Connect Enterprise Edition, to process requests arriving through IBM z/OS Connect EE.
• Additional support for messaging within CICS Liberty JVM server
• IBM MQ for z/OS Service Provider for IBM z/OS Connect Enterprise Edition
• IBM MQ for z/OS Unix System Services Web Components feature
• Improved workload balancing options for shared queues
Additional support for messaging within CICS Liberty JVM server
Version 9.1.0 provides an updated IBM MQ resource adapter, which has support to allow connections from the CICS® JVM server Liberty profile to IBM MQ, using either client or bindings mode. This additional support for messaging that the resource adapter now provides has a dependency on the CICS Liberty JVM server profile environment. For more information, see Using IBM MQ classes for JMS in a CICS Liberty JVM server.
IBM MQ for z/OS Service Provider for IBM z/OS Connect Enterprise Edition
From Version 9.1.0, IBM MQ for z/OS Service Provider for IBM z/OS Connect Enterprise Edition (MQ Service Provider) processes requests arriving through IBM z/OS Connect Enterprise Edition (IBM z/OS Connect EE). The MQ Service Provider allows REST aware applications to interact with z/OS assets, that are exposed using IBM MQ for z/OS queues and topics. You can achieve this without having to worry about the coding required to use asynchronous messaging. For more information, see IBM MQ for z/OS Service Provider for IBM z/OS Connect EE.
IBM MQ for z/OS Unix System Services Web Components feature
From Version 9.1.0, if you want to use the IBM MQ Console, or the administrative REST API to IBM MQ for z/OS you need to install this feature.
Note that to install this feature, you must install the IBM MQ for z/OS Unix System Services Components feature.
See Create and customize the IBM WebSphere® Application Server Liberty Profile server definition and Create a procedure for the IBM WebSphere Application Server Liberty Profile server for information on how you set up the feature.
Improved workload balancing options for shared queues
IBM MQ for z/OS queue sharing groups can take advantage of a new configuration option provided by the coupling facility which can, in some configurations, improve the distribution of workload, and minimize the number of empty MQGET calls. For more details see Tuning coupling facility list monitoring.
IBM® MQ Version 9.1.0 delivers a number of new features and enhancements on z/OS® that are available with IBM MQ Advanced for z/OS Value Unit Edition entitlement. These features include Java™ and JMS client enhancements, Managed File Transfer enhancements, and blockchain connectivity.
• Java and JMS client connectivity to z/OS queue managers
• Advanced Message Security on JMS for z/OS queue managers
• Managed File Transfer enhancements
• Blockchain connectivity
Java and JMS client connectivity to z/OS queue managers
You can connect an IBM MQ classes for JMS, or IBM MQ classes for Java, application to a queue manager on z/OS, that has the ADVCAP(ENABLED) attribute, by using a client connection.
For more information, see Java and JMS client connectivity to z/OS queue managers.
Advanced Message Security on JMS for z/OS queue managers
Version 9.1.0 adds AMS support to a IBM MQ classes for JMS or IBM MQ classes for Java application, running on z/OS, using a client connection to a z/OS queue manager, licensed as IBM MQ Advanced for z/OS Value Unit Edition. For more information, see Advanced Message Security support.
Managed File Transfer enhancements
For Version 9.1.0, IBM MQ Advanced for z/OS Value Unit Edition provides the following functional enhancements to the Managed File Transfer capabilities:
Managed File Transfer agent remote connections
From Version 9.1.0, Managed File Transfer agents running on IBM MQ Advanced for z/OS Value Unit Edition can connect to a queue manager using a client connection. This means that agents that send and receive files from the local system can be deployed on a z/OS system that is remote from the queue managers responsible for routing messages that represent the file payloads. For more information, see Enabling MFT agent connectivity to remote z/OS queue managers.
Separately installable logger feature
From Version 9.1.0, the Managed File Transfer Logger is a separately installable feature that can be run remotely from an IBM MQ queue manager. This reduces the number of queue managers that are required for MFT operations, simplifying the topology for easier administration. To use the logger as a client, you must use one or more of the additional parameters in the fteCreateLogger command. There are, also, extra parameters for use in the logger.properties file.
MFT REST API
The REST API includes options to list all current Managed File Transfer transfers and to query the status of Managed File Transfer agents. For more information, see Getting started with the REST API MFT.
Blockchain connectivity
From Version 9.1.0, IBM MQ Advanced for z/OS VUE includes the IBM MQ Bridge to blockchain, which enables applications and systems to participate in a blockchain network through IBM MQ without the need to understand ledger-specific APIs, configuration, or controls. Once connection is established, IBM MQ can be used to query information from blockchain and return data via request-reply messages. IBM MQ can also drive create, read, update, and delete operations on blockchain managed assets. For more information, see Configuring IBM MQ Advanced for VUE for use with blockchain.
IBM® MQ Version 9.1.0 delivers a number of new features that are available for all supported platforms. These features include the IBM MQ Console, which provides a customizable, browser-based administration tool, a REST API for administration, and a REST API for messaging.
• The IBM MQ Console
• The administrative REST API
• The MFT REST API
• The messaging REST API
The IBM MQ Console
From Version 9.1.0, you can use a web-based user interface to administer IBM MQ. The IBM MQ Console runs in a browser and provides control over queue managers and IBM MQ objects.
To get started quickly with the IBM MQ Console, see Getting started with the IBM MQ Console.
For more information about the IBM MQ Console, see Administration using the IBM MQ Console.
The administrative REST API
From Version 9.1.0, you can use the administrative REST API to perform the following actions on MQ objects:
• Query queue managers
• Query installations
• Query subscriptions
• Query queue manager to queue manager channels and channel status
• Query queues and queue status
• Create, update, and delete queues
• Run mqsc commands
This RESTful API can help you to embed IBM MQ administration into popular DevOps and automation tooling.
You can use the administrative REST API to administer queue managers that are not in the same installation as the mqweb server. That is, you can administer remote queue managers and the IBM MQ objects that are associated with the remote queue manager. Therefore, you can use the REST API to administer your entire IBM MQ network with only one installation that runs the mqweb server. For more information, see Remote administration using the REST API.
To get started quickly with the administrative REST API, see Getting started with the administrative REST API.
For more information about the administrative REST API, see Administration using the REST API.
The MFT REST API
In Version 9.1.0, you can use the REST API for the Managed File Transfer commands for listing transfers and querying details about file transfer agents. For more information, see Getting started with the REST API MFT.
ImportantThe MFT portion of the REST API does not apply to the IBM MQ Appliance.
The messaging REST API
From Version 9.1.0, you can use the messaging REST API to send and receive IBM MQ messages. This feature is intended as a replacement for the IBM MQ bridge for HTTP:
• You can send an IBM MQ text message to a specified queue by using the HTTP POST method with the /messaging/qmgr/{qmgrName}/queue/{queueName}/message resource. For more information, see POST.
• You can receive an IBM MQ text message from a specified queue by using the HTTP DELETE method with the /messaging/qmgr/{qmgrName}/queue/{queueName}/message resource. For more information, see DELETE.
V9.1.0 Changes
A number of changes relating to authentication have been made at IBM® MQ Version 9.1.0.
• Changes to SYSTEM.DEFAULT.AUTHINFO.IDPWOS and SYSTEM.DEFAULT.AUTHINFO.IDPWLDAP connection authentication information objects
• Changes to client channel authentication for z/OS queue managers
• Changes to user authentication with the IBM MQ Explorer
• Two CipherSpecs also available on z/OS
• Deprecation of the TLS 1.0 Cipherspec protocol
• Client reason code
Changes to SYSTEM.DEFAULT.AUTHINFO.IDPWOS and SYSTEM.DEFAULT.AUTHINFO.IDPWLDAP connection authentication information objects
In earlier versions of IBM MQ, the value for the adopt context parameter of the system default connection authentication information objects was NO. That is, successful user ID and password validation did not change the security context of the connection. From Version 9.1.0, the adopt context parameters of the SYSTEM.DEFAULT.AUTHINFO.IDPWOS and SYSTEM.DEFAULT.AUTHINFO.IDPWLDAP objects is set to YES for new queue managers and when re-creating default objects. Queue managers that were created by an earlier version of IBM MQ that are started with Version 9.1 retain their existing object definitions.
For more information, see DEFINE AUTHINFO.
Changes to client channel authentication for z/OS queue managers
In earlier versions of IBM MQ, channel authentication rules are evaluated before connection authentication validation of user ID and password credentials. From Version 9.1.0, channel authentication rules are evaluated after connection authentication validation of credentials, this change in ordering allows channel authentication blocking and mapping rules to consider any changes in the client security context from a successful user ID and password validation. The previous behavior can be restored by issuing the following MQSC command:
RECOVER QMGR(TUNE CHLAUTHEARLYADOPT OFF)
For more information, see Securing remote connectivity to the queue manager.
Changes to user authentication with the IBM MQ Explorer
In earlier versions of IBM MQ, if IBM MQ Explorer required a user ID and password to connect to a queue manager, it would send that user ID and password using compatibility mode by default.
From Version 9.1.0, the default setting for IBM MQ Explorer is MQCSP authentication mode. If IBM MQ Explorer needs to connect to a queue manager using compatibility mode, for example for administering queue managers older than Version 8.0.0, the check box for enabling compatibility mode on panels where a user ID and password are entered must be selected.
For more information, see Connection authentication with the Java client.
Two CipherSpecs also available on z/OS
The following CipherSpecs, previously available only on Multiplatforms, are now also available on z/OS®:
• ECDHE_RSA_AES_128_GCM_SHA256
• ECDHE_RSA_AES_256_GCM_SHA384
For more information on platform availability for CipherSpecs, see Enabling CipherSpecs.
Deprecation of the TLS 1.0 Cipherspec protocol
From Version 9.1.0, the TLS 1.0 Cipherspec protocol is disabled by default.
See Enabling deprecated Cipherspecs for information on how you enable a deprecated CipherSpec.
Client reason code
From Version 9.1.0, where multiple client connection attempts are made, for example with a channel with a comma separated connection name and the connection sequence fails, reason codes other than MQRC_HOST_NOT_AVAILABLE and MQRC_STANDBY_Q_MGR are given priority when being returned to an application. In previous versions the last reason code encountered in the connection sequence is always returned, this could lead to configuration errors such as MQRC_NOT_AUTHORIZED encountered earlier in the connection attempt to not be returned to the application.
Db2 Universal Table Spaces
Version 9.1.0 provides additional samples, demonstrating how a queue sharing group can be set up to use Universal Table Spaces (UTS) in DB2® V12.
For more information, see Planning your Db2 environment.
Improvements to z/OSMF
From Version 9.1.0, the IBM z/OS® Management Facility (z/OSMF) workflows for provisioning IBM MQ resources have been updated to take advantage of newer Cloud Provisioning capabilities that are being made available in z/OSMF V2.2.
Additionally, the workflow to provision local queues has been enhanced to include actions to display selected attributes of a queue, and to browse or destructively get a message from a queue.
For more information on the improvements to z/OSMF, see Using IBM z/OSMF to automate IBM MQ.
Changes in z/OS product identifier (PID) recording
Version 9.1.0 introduces an improved method of including the correct PID for each of the following components:
• Base IBM MQ
• Advanced Message Security
• Managed File Transfer
• IBM MQ for z/OS Value Unit Edition (VUE)
• IBM MQ Advanced for z/OS Value Unit Edition
For more information, see Product usage recording with IBM MQ for z/OS products.
Display queue manager utility on z/OS
Version 9.1.0 provides the CSQUDSPM utility on z/OS, which displays information about queue managers, and provides the equivalent function to dspmq on Multiplatforms.
Cluster workload exits for z/OS
From Version 9.1.0, cluster workload exits run in the channel initiator address space, instead of the queue manager address space. If you have a cluster workload exit, you should remove the CSQXLIB DD statement from your queue manager started task procedure, and add the dataset containing the cluster workload exit to the CSQXLIB concatenation on your channel initiator started task procedure.
Removal of OPMODE parameter
From Version 9.1.0, the OPMODE parameter in the CSQ6SYSP macro has been removed, and no longer has any effect. See OPMODE for details.
Before migrating to Version 9.1.0, you should first start your Version 8.0.0 or Version 9.0.0 queue manager in NEWFUNC mode. That is, for Version 8.0.0, start your queue manager with OPMODE=(NEWFUNC,800), and for Version 9.0.0, start your queue manager with OPMODE=(NEWFUNC,900) or OPMODE=(NEWFUNC,800).
If you, instead, leave your Version 8.0.0 or Version 9.0.0 queue manager in COMPAT mode, and then migrate to Version 9.1.0, you will be able to enable function which is not compatible with COMPAT mode in Version 8.0.0 or Version 9.0.0, such as buffer pools with a LOCATION of ABOVE. This will cause problems if you subsequently migrate back to Version 8.0.0 or Version 9.0.0, as you will need to change to NEWFUNC mode before you start your queue manager, otherwise the queue manager might not start.
A number of changes have been made for Managed File Transfer at IBM® MQ Version 9.1.0.
New parameter for fteListMonitors command for bulk backing up of MFT resource monitors
The -od parameter is added to the fteListMonitors command. By specifying this parameter, you can back up more than one resource monitor at a time by exporting their definitions in bulk to a specified directory. Each resource monitor definition is saved to a separate XML file with a name in the format agent name.monitor name.xml.
The -od parameter is particularly useful if you have a large number of resource monitors that you want to back up because you need to run the fteListMonitors -od command once only, instead of having to run the fteListMonitors -ox command separately for each resource definition, or use a separate script to run the fteListMonitors -ox command for each resource monitor.
For more information, see Backing up and restoring MFT resource monitors and fteListMonitors: list MFT resource monitors.
Updates to fteSetAgentTraceLevel and fteSetLoggerTraceLevel commands to allow colon separated lists of trace specifications
The fteSetAgentTraceLevel and fteSetLoggerTraceLevel commands have been updated so that you can specify a colon-separated list of trace specifications with these commands in exactly the same way as you do with the agent.properties and logger.properties files. This option enables you to set tracing of different classes, and at different levels.
Managed File Transfer configurable recovery timeout for stalled transfers
From Version 9.1.0, Managed File Transfer provides a new advanced property for setting a value for the amount of time a source agent continues to try to recover a stalled transfer. You can specify that the agent continues to attempt to recover the stalled transfer until the transfer is successful, or that the agent stops the file transfer as soon as it enters recovery, or that the agent continues to attempt to recover the stalled transfer for the amount of time in seconds as set by the positive integer value specified. For more information, see Timeout option for transfers in recovery.
Change to behavior of Managed File Transfer fteDeleteAgent command
From Version 9.1.0, the fteDeleteAgent command has been updated so that any resource monitor and scheduled transfers are removed when the agent is deleted. For more information about the fteDeleteAgent, see fteDeleteAgent (delete a Managed File Transfer Agent).
New Status Age value displaying age of last reported status for Managed File Transfer agents
From Version 9.1.0 a new value, Status Age, which shows the age of the status that was last reported by an Managed File Transfer agent, is displayed for agents that are connecting to the coordination manager. The Status Age is output when you run fteListAgents and fteShowAgentDetails commands in the command line. The Status Age column can be seen in IBM MQ Explorer for agents that are listed against a coordination manager and in the individual properties for each agent. For more information, see What to do if the fteListAgents command shows an agent status as UNKNOWN.
Change to output of fteDisplayVersion -v command
From Version 9.1.0, IBM MQ Light Service for Bluemix® JMS Provider is removed from the output of fteDisplayVersion -v command. Following this removal, you should review any automation that is based on the output from the fteDisplayVersion command.
Changes to DISPLAY CHSTATUS command output values for remote Managed File Transfer agents
From Version 9.1.0, output from the DISPLAY CHSTATUS command includes values that make it clear when the application that is running at the remote end of a channel is a Managed File Transfer Agent:
• The RAPPLTAG channel attribute value that displays the remote partner application name is updated to display MFT Agent and agent name.
• A new RPRODUCT product identifier MQJF is added to indicate that the product running at the remote end of the channel is a Managed File Transfer Agent.
For more information, see Display CHSTATUS.
Changes to message to file transfers in Managed File Transfer
In a message to file transfer, the source agent now browses the messages from the source queue, unlike the destructive GET, in IBM MQ versions before Version 9.1.0. The messages are removed from the source queue after all messages (in a group if message grouping is used) have been browsed and data written to the destination file. This allows messages to remain in the source queue if a transfer fails or is canceled. Due to this change, authority to BROWSE must also be provided along with GET authority to run message to file transfers. For more information about the message-to-file feature, see Transferring data from messages to files.
Change to prefix of subscription names for subscriptions created by the IBM MQ Explorer MFT plug-in
From Version 9.1.0, the prefix to the name of a subscription created on the coordination queue manager by the IBM MQ Explorer MFT plug-in is changed to show that the subscription was created by the IBM MQ Explorer MFT plug-in and the name of the user. For more information, see Retaining progress and log messages by using the IBM MQ Explorer plug-in.
Managed File Transfer Logger database schema updates
The following data types have been altered, causing a change to various column widths in some database tables:
• LONG VARCHAR has been changed to VARCHAR in the DB2® schema
• NCLOB has been changed to NVARCHAR(Size) in the Oracle Schema
For more information, see MFT database logger tables.
Where to Find Additional Information:
IBM MQ Version 9.0 documentation on the IBM Information Center:
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com.ibm.mq.helphome.v90.doc/WelcomePagev9r0.htm
IBM MQ Version 9.1 documentation on the IBM Information Center:
https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com.ibm.mq.helphome.v91.doc/WelcomePagev9r1.htm
Primary Contact:
Sonny Smith
Software Services Mainframe IMS/MQ/DB2
856-451-1367
Secondary Contact:
Ed Gojich
Software Services Mainframe CICS/IMS/DB2/MQ
717-443-4201
|
Usercomm - IBM MQSeries V9.1.0 Upgrade Information