How can I save ACK messages into a file

If you turn on the ‘Save Inbound’ on your outbound thread, your ACKs (inbound messages) should be saved in the SMAT DB you specify, just like your outbound.

Hope that helps.

Doesn’t the SmatDB provide a method for searching for messages then extracting those messages to a file?

I don’t have hands on experience or a Cloverleaf environment at hand but I think the User Doc combined with some ‘poking around’ should confirm that.

Jim:

I would have to check or test that.  ACK messages are received as ack messages not IB messages.  If you enable OB ONLY on an outbound thread, it blocks IB messages but still receives ACKs.

Not where CL readily available now.  How about you test it and let me know?

What I do when I need to find a reply(ack) sent back to me for a message I sent OB:

On 19.1 with SMATDB turned on:

Right click on your OB thread->SMAT->Open Inbound(i.e. for IB replies)

There you can search message content and metadata, such as Control ID

To save to a file:

Select the messages that met your search criteria then select the ‘resend marked messages’ button

Change the ‘resend Selected messages To:’ from ‘thread’ to ‘file’

Give it a file name, format and directory to send to, then hit apply

There are a few ways to be able to search a SMATDB file with smat msgs saved.  I have written a script for our company that works really well from the command line.   I believe somewhere in the Forums that Charlie put some code out there.  I used some logic from his programming to add to mine to make it better (thanks Charlie).

Using sqlite from the linux command line and choosing your SMATDB file, you can use something like this:

select MessageContent,DestConn,DriverCtl,UserData,SourceConn,Time,TimeIn,TimeOut from smat_msgs where UPPER(MessageContent) like ‘%$whatToFind%’;

Of course if you have your SMATDB files encrypted, that will present some other challenges.

Why not use Tcl to check the acknowledgment and if it is a NAK flip the message over to the IB side and route the ACK (now a message) to a Fileset Protocol to save it (could also send an email indicating a NAK was received).

Or in the Tcl reply handling proc save to a file directly (still sending an email so you know right away a NAK occurred).

I realize the methodology is ingrained to use SMAT but this is an opportunity to rethink the situation.

Am I missing something here?  If you are worried about receiving a NAK the existing cl_check_ack in $HCIROOT/tclprocs/recover.tcl should handle this for you.

The proc will check for a NAK and attempt to resend the message three times.  If it still fails the message is sent to the ERROR DB with the error message from the NAK, if any, in the user metadata field.

If you need more. simply copy the proc, rename it to whatever, and modify it.  You could modify it to send email or whatever else you need.  The message that was NAKed is in the ERROR DB for you to handle as you see fit.