Troubleshooting the Connect:Direct bridge

Use the following reference information and examples to help you diagnose errors returned from the Connect:Direct bridge.

• Tracing the Connect:Direct bridge
• Log information for the Connect:Direct bridge
• Solving permissions issues with Connect:Direct nodes
• What to do if text transfers to or from Connect:Direct nodes are not converting the data correctly
• What to do if transfers to PDS or PDS members through the Connect:Direct bridge are failing
• Connect:Direct file paths specified with a double forward slash
• Increasing the number of concurrent transfers for the Connect:Direct bridge
• Debugging a Connect:Direct process that is called by a file transfer

• Tracing the Connect:Direct bridge
  We can capture trace from the Connect:Direct node that is part of the Connect:Direct bridge to help with problem determination.
• Log information for the Connect:Direct bridge
  We can use a Connect:Direct bridge agent to transfer files between MFT agents and Connect:Direct nodes. Log information about the Connect:Direct nodes and processes involved in these transfers is displayed in the IBM MQ Explorer plug-in and is stored in your log database.
• Solving permissions issues with Connect:Direct nodes
  Use the information in this topic if your transfers between Managed File Transfer and Connect:Direct fail with an error about insufficient permissions.
• What to do if text transfers to or from Connect:Direct nodes are not converting the data correctly
  When you transfer files in text mode between an MFT agent and a Connect:Direct node, code page and end-of-line character conversion is performed. The transfer uses the operating system information in the network map of the Connect:Direct bridge node to determine the end-of-line characters of a remote node. If the information in the network map is incorrect, the end-of-line character conversion might be performed incorrectly.
• What to do if transfers to PDS or PDS members through the Connect:Direct bridge are failing
  If the destination of a transfer is a Connect:Direct node on z/OS and is a PDS or PDS member, the transfer fails if the -de parameter has not been specified with a value of overwrite.
• Connect:Direct file paths specified with a double forward slash
  If, as part of a file transfer, you specify a file located on a Connect:Direct node by using a file path that starts with a double forward slash (//), the file is treated as a data set.
• Increasing the number of concurrent transfers for the Connect:Direct bridge
  To increase the number of concurrent transfers that the Connect:Direct bridge agent can process, we must change three agent properties. We must also increase the maximum number of connections that the Connect:Direct node accepts.
• Debugging a Connect:Direct process that is called by a file transfer
  We can configure the Connect:Direct bridge agent to write log information about the Connect:Direct process that is called by a file transfer to the output0.log file in the Connect:Direct bridge agent configuration directory.

Parent topic: Troubleshooting Managed File Transfer