Can’t find file DRIVERCTL in 6.2

[Peter Heggie]

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.

Peter Heggie
PeterHeggie@crouse.org

Topic

[Peter Heggie]

Also, this outbound thread has two sources – two different inbound threads send messages to it. Not sure that makes a difference.

Peter Heggie
PeterHeggie@crouse.org

[Rob Abbott]

DRIVERCTL is populated on inbound.  I am guessing that one of the inbound threads is tcp/ip and you have “use DRIVERCTL control” selected in the protocol configuration.

It’s showing you the IP and port of the sending system.

Rob Abbott
Cloverleaf Emeritus

[Peter Heggie]

wow I had a real memory loss there. I was thinking that I could look at DRIVERCTL in some outbound proc and see the OBFILE information. I know the input thread is tcp/ip, but the output thread is Fileset-FTP, and the FTP configuration specifies a certain directory and filename. I was expecting those FTP values to populate the DRIVERCTL at some point in the processing. But maybe that is not stored in the DRIVERCTL metadata?

I know I can set the DRIVERCTL OBFILE in a proc, but I wanted to get the original, outbound DRIVERCTL value so that I could change the last node of the directory name before sending it to the protocol.

Peter Heggie
PeterHeggie@crouse.org

[Author]

Replies