Restrictions of the Connect:Direct bridge agent

The Connect:Direct® bridge agent is configured to transfer files to and from Connect:Direct nodes. There are some functions that the Connect:Direct bridge agent is not capable of performing.

• The Connect:Direct bridge agent cannot read messages from a queue or write messages to a queue. It cannot act as the destination agent in a file-to-message transfer or as the source agent in a message-to-file transfer.
• We cannot define a resource monitor on the Connect:Direct bridge agent.
• We cannot have a Connect:Direct bridge agent as both the source and destination of a transfer. We cannot transfer from Connect:Direct node to Connect:Direct node through the Connect:Direct bridge.
• The Connect:Direct bridge agent does not support user exits that are called before or after the transfer. The Connect:Direct bridge agent does support a credential mapping exit. For more information, see Mapping credentials for Connect:Direct by using exit classes.
• We cannot define presrc or postsrc program invocations for a transfer that has the Connect:Direct bridge agent as the source agent. For more information, see Program invocation nested elements.
• We cannot define predst or postdst program invocations for a transfer that has the Connect:Direct bridge agent as the destination agent. For more information, see Program invocation nested elements.
• We cannot specify a wildcard character in the source specification if the source agent is the Connect:Direct bridge agent.
• If you specify a source disposition (-sd) of delete when transferring a file or data set from a Connect:Direct node, the behavior is different to the usual source disposition behavior. One of the following cases occurs:
  • If Connect:Direct uses a process that is generated by Managed File Transfer to move the file or data set from the source, specifying the delete option causes the transfer to fail. To specify that the source file is deleted, you must submit a user-defined Connect:Direct process. For more information, see Submitting a user-defined Connect:Direct process from a file transfer request.
  • If Connect:Direct uses a user-defined process to move the file or data set from the source, this parameter is passed to the process through the %FTEFDISP intrinsic symbolic variable. The user-defined process determines whether the source is deleted. The result that the transfer returns depends on the result that is returned by the user-defined process.