Common MFT problems

Common problems that might occur in your Managed File Transfer network.

  • If a text transfer fails with the following error:
    BFGIO0060E: Text data conversion has failed
    This can occur for one of two reasons:
    1. One or more characters in the source file cannot be converted from the source file code page to the destination file code page. This problem can occur when code pages have different character sets and certain characters cannot be converted between them.
      If it is acceptable for conversion of some characters to not be converted, a replacement character sequence can be defined at the destination agent so that the transfer does not fail. Specify the agent property textReplacementCharacterSequence to define a replacement character sequence. For more information, see Table 2.
    2. The source file encoding does not match the default encoding of the source agent. In this case performing a text transfer by using the default settings corrupts the character data. To transfer a source file that does not have the same encoding as the source agent, perform one of the following steps:
      1. Specify the file encoding in a transfer definition file. For more information, see Using transfer definition files.
      2. Specify the file encoding by using the -sce parameter with the fteCreateTransfer command. For more information, see the topic fteCreateTransfer: start a new file transfer.
      3. Specify the file encoding as part of an Ant move or copy task. For more information, see Using Apache Ant with MFT.
    To check that you have selected the correct source file encoding for a transfer perform the following steps:
    1. Set the destination file encoding to UTF-8.
    2. Transfer the file in text mode.
    3. Use a UTF-8 file viewer to view the contents of the file. If all characters in the file are correctly displayed, the source file encoding is correct.
  • If you see the following output from the fteCreateAgent command:
    BFGMQ1007I: The coordination queue manager cannot be contacted or has refused a 
  connection attempt.
The IBM MQ reason code was 2058. The agent's presence will not be published.
    it indicates that the coordination queue manager cannot be contacted and provides the IBM® MQ reason code for why. This information message can indicate that the coordination queue manager is currently unavailable or that you have defined the configuration incorrectly.
  • If you are using user exit routines and there is a failure while the user exit is being called or just after the exit has been called, for example a product failure or power cut, it is possible the user exit will be called more than once.
  • If you have an agent with a queue manager on a system with an IP address that is assigned by DHCP (rather than a static IP address), and the agent connects to that system by using a client TCP/IP connection, you must start the agent with the following system environment variable set:
    • [Windows]On Windows: 
      set BFG_JVM_PROPERTIES="-Dsun.net.inetaddr.ttl=value"
    • [UNIX]On UNIX: 
      export BFG_JVM_PROPERTIES="-Dsun.net.inetaddr.ttl=value"
    where value is the time interval in seconds between each flush of the cached DNS values of the JVM. If the IP address of the queue manager system is reassigned for any reason (for example, because of a network outage, an IP lease expiry, or a system reboot), the agent reports its lost connection to the queue manager. After the JVM DNS cache is flushed, the agent can successfully reconnect. If this environment variable is not set, the agent cannot reconnect in this scenario without a JVM restart. This behavior is because the JVM internally caches the IP addresses of host names and does not refresh them by default.
  • If you run the fteStartAgent command and see the following error message, your environment probably has additional library paths that conflict with Managed File Transfer: 
    BFGCL0001E: An internal error has occurred. The exception was: 'CC=2;RC=2495;AMQ8568:
 The native JNI library 'mqjbnd' was not found. [3=mqjbnd]
    If the LD_LIBRARY_PATH or LIBPATH environment variable is set to reference a 64-bit version of the library before the 32-bit version when the agent is running with a 32-bit version of Java (as is currently the case for most platforms), this error occurs.

    To resolve this issue, set the Managed File Transfer agent property javaLibraryPath to reference the correct location for the library. For example, for mqjbnd on AIX®, set to: /usr/mqm/java/lib. For mqjbnd on Linux®, set to: /opt/mqm/java/lib

  • If you have enabled user authority checking by specifying authorityChecking=true in the agent property file and all authority checks are failing even if the user has the required authority on the relevant authority queue:
    • Ensure that the user that runs the agent has ALT_USER access control on the agent queue manager.
  • If you have enabled user authority checking by specifying authorityChecking=true in the agent property file and IBM MQ error messages are written to the agent output0.log file perform one of the following actions:
    • Ignore the messages, the agent is not affected.
    • Grant the user who runs the agent GET authority on the SYSTEM.FTE.AUTH* queues belonging to the agent.
  • If you have edited the agent property file and the agent has not picked them up:
    • Restart the agent, to ensure that the agent reads the new properties.
[z/OS]

z/OS

  • If you are using the agent on z/OS® to transfer to a PDS or PDSE data set and an abend occurs, your system might have limited disk space. The abend is likely to have a system completion code of B14 with a return code of 0C, indicating there is no space left.

    If you are transferring to a sequential data set, the transfer fails and indicates the out-of-space condition, but the agent remains operational.

  • If you are using the agent on z/OS, and the WMQFTEP task generates some Java core dumps before becoming unresponsive, apply OMVS system services APAR OA43472.
  • If you see the following output when running a configuration or administration script on z/OS: 
    FSUM7332 syntax error: got (, expecting Newline
    this output indicates that the environment variable _BPXK_AUTOCVT=ON has not been set in the environment where the configuration or administration script is being run. For more information about this environment variable and how to set it, see Environment variables for MFT on z/OS.