A fix is available
APAR status
Closed as program error.
Error description
The FTE installation is present on a system where there are considerable network delays when doing DNS reverse lookups. The fteCreateTransfer command performs a reverse DNS lookup to determine the hostname of the system where the command was run, for auditing purposes. It is not possible to prevent the command from doing the reverse lookup, and so the creation of the transfer request takes a considerable amount of time to complete, due to the DNS lookup.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users who are running on a system where a DNS lookup takes a considerable amount of time to complete, for example by not having the system configured for or access to a DNS server. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The FTE agent and its commands perform reverse DNS lookups supplying host IP addresses. For example this occurs when a transfer command request completes, where an attempt is made to translate the IP addresses of the of the systems involved into hostnames for displaying in the transfer audit report log. This DNS lookup request typically requires the presence of a DNS server, if it is unavailable or not configured on the system then the reverse DNS lookup times out, which can significantly delay the operation depending on how long the system takes to timeout the lookup.
Problem conclusion
A new FTE/MFT installation property has been added which permits the switchable configuration of whether DNS lookups should be performed or not. By default the behaviour of the agent is unchanged, meaning that this property has the default value which instructs the DNS lookups to be requested. To change this default to prevent DNS lookups from taking place, use the installation property and value: enableReverseDNSLookups=false This property controls the behaviour when put in the FTE/MFT system's installation property file. This installation property file name is called one of the following names depending on the version of the product: For MQ-MFT 7.5/8.0 ================== "installation.properties" The installation.properties file is located in the MQ_DATA_PATH directory. For example on Windows, the default file location is: MQ_DATA_PATH\mqft\installations\installation_name On UNIX and Linux systems, the default file location is /var/mqm/mqft/installations/installation_name For MQ-FTE 7.0.4 ================ "wmqfte.properties" The wmqfte.properties file is located in the config_directory directory. For example on Windows, the default file location is: C:\Documents and Settings\All Users\Application Data\IBM\WMQFTE\config On UNIX and Linux systems, the default file location is /var/IBM/WMQFTE/config Also contained within this APAR's code change, when migrating from earlier versions of the product using the 'fteMigrateAgent' command, any properties defined in the previous version will now be migrated to the new installation properties file except for the enableFunctionalFixPack and defaultProperties properties, which are not applicable to later versions. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.4.6 v7.5 7.5.0.6 v8.0 8.0.0.5 The latest available FTE maintenance can be obtained from 'Fix List for WebSphere MQ File Transfer Edition 7.0' http://www-01.ibm.com/support/docview.wss?uid=swg27015313 The latest available MQ maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT09167
Reported component name
WMQ FILE TRANSF
Reported component ID
5724R1000
Reported release
704
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-05-28
Closed date
2015-10-30
Last modified date
2015-11-10
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WMQ FILE TRANSF
Fixed component ID
5724R1000
Applicable component levels
R704 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEP7X","label":"WebSphere MQ File Transfer Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 November 2015