Can’t find file DRIVERCTL in 6.2

I have a tcp/ip inbound thread sending messages to a Fileset FTP outbound thread. When I look at the outbound thread outbound SmatDB, the DRIVERCTL lists a client IP address and client port number, not a FILESET OBFILE name/value. What is the client IP address and port number? It is not one of our tcp/ip port numbers.

For this logical path, the message was not updated in content or metadata when it went through the outbound thread and its TCL procs. However, there is a Send OK proc. But I thought the Smat DB for outbound is written to after the protocol is used, and before the Send OK proc is invoked..?

I do have other interfaces with a fileset-FTP outbound where I do see the DRIVERCTL with file configuration data instead of tcp/ip configuration data. So this interface must be different somehow but I don’t know what is different. Could it be that I am resending test messages through it, and not getting new messages from the source system? I looked at the protocol configuration and it looks the same as the other outbound fileset-local threads.