Resending SMAT

Mark,

I usualy cycle the SMAT file; leave the thread up; select messages of interest from the .old SMAT file(s); then resend.

Don’t forget to make sure you have inbound or outbound appropriately selected.

Jim Kosloskey

Mark,

One thing to be aware of is that starting up a thread while you have the active .idx opened in SMAT can cause a problem with initiating the saved message process.  Since you have the active .idx opened in SMAT, cloverleaf cannot open it for writing.  The thread will still start up but without writing to the saved message file.  Not a good thing.  You might have to refer to the saved message file and find out it was never saving the messages.

Best method is the manner in which Jim K, indicated.

It depends on the OS. For Solaris you can keep the thread running and use the same idx file, no problems. With AIX you need to cycle the smats. Not sure about others.

When you try to resend a message to a down thread it isn’t put into the recovery database so nothing happens.  I want to emphasize the earlier warning about cycling the smat and not using the current SMAT file.  If you get into the habit of playing with current SMAT files it’s just a matter of time before you forget to close the SMAT file before you turn the thread back on again.  And when this happens…bye bye SMATT logging.  (Does this sound like it’s coming from someone who’s done it before?  🙄 )

Don’t know what’s up with the unlock error, but your 2nd screenshot clearly indicates the successful resend of the message…

I find it easier oftentimes to save the message to a file using SMAT, then use the monitor GUI to resend the file to whichever thread needs it – it’s way too easy to turn a thread back on before closing the SMAT down otherwise…

Is this an inbound thread?  If so you need to resend it to the ib_pre instead of the ob_post.

Mark,

Based on your last reply, it looks like you are trying to create a file with the desired resend message.  This is not required if you are resending through smat.  Just select the actual message (using the toggle “select” toggle button) and then resend by clicking selected/resend menu item.  As Daniel indicated above, select the inbound thread name and IB Pre TPS.  The last screen print you posted looks like you sent it via OB post TPS.  That would sent the message BACK to the source system.

If you choose to select and create a resend file, the created file will need to be sent via the actual thread on NetMonitor.  Right click inbound thread and select “resend”.  Feel free to email me if my reply is confusing.  My replies will confuse me at times..🙂   Hope this helps.

When you’ve saved your file to resend, you no longer need to use the SMAT tool to actually resend it.  Go to the Network Monitor GUI, right-click the thread, control -> full -> resend -> (select TPS: ib pre, ib post, ob pre, etc.) -> (msg type: data) -> (can specify priority of message, or leave it at the default 5120 setting) -> (browse for your file using the ‘list’ button)

And you’re correct about being careful where you place the file you’re attempting to resend.  If you place it in the wrong TPS direction, it’s obviously not going to process anywhere…

Mark,

I just took another look at your screen print.  You selected copath_in.old.idx. Sounds like a inbound message save message file.  It this correct?