Reroute ACK/NACK

[Craig Weldy]

I am currently on CL 5.8.5  on AIX, soon to upgrade to CL 6.0/6.1.

I have a situation I am not sure how to solve, and need some guidance.

   SYS_A_ADTSIU_IN   ====>  SYS_B_ADTSIU_OUT

   SYS_A_DFT_OUT      <====   SYS_B_DFT_IN System A says that they only have one inbound port and one outbound port, so when I have SYS_A_DFT_OUT thread setup to wait for an ACK and send out a DFT message to SYS_A, they send the ACK back to me through the SYS_A_ADTSIU_IN thread. That is well and good, except that SYS_A_DFT_OUT is sitting there waiting for the ack and since it isn’t coming, then it dosn’t send any more message without bouncing the thread. Is there a way to take the inbound ACK/NACK message from the SYS_A_ADTSIU_IN thread and route it to the SYS_A_DFT_OUT thread to satisfy the SYS_A_DFT_OUT threads need for an ACK and get it to send the next message. Since it is a DFT feed, I don’t want to just send without an ack since I will never know if everything made it through. I can think of some ways to make it work by writing to a database outside of cloverleaf and then using the ack to verify that each message got an ack, but I am looking for a way to do this internal to the cloverleaf application if possible. That being said, I will entertain any possible solutions so don’t be shy. Thanks for your time!

Craig Weldy
Senior Interface Analyst
Beacon Health System
South Bend, In, 46615

Topic

[Brandon Grudt]

I’m a bit confused with the process.  Shouldn’t the SYS_A_DFT_OUT be generating the ACK, not waiting on it?  I’m afraid you lost me in the explanation.

One thing you can consider when there are port limitations is using a destination.  Set an OB thread as a destination for another OB “thread” (set as a destination, not as a thread), which essentially acts as a merge.  I’m not exactly sure what you’re trying to do, so I’m not sure if that is useful or not.

[Craig Weldy]

Sorry for the confusion, all of the threads (in/out) are in relation to cloverleaf.  When I have a thread with “out” in the name I am sending a message to a system outside of cloverleaf.  When I send a message out, I am expecting to get an ACK back to that thread from the external system.

The problem is that the external system is not sending the ACK back to the thread that sent it the message, it is sending the ACK in the normal data flow to a different thread that is Inbound from that same external system.  It is not coming back to the original outbound thread as an acknowledgement that they received the message I sent out.

Hope I didn’t just muddy the water even more.

Craig Weldy
Senior Interface Analyst
Beacon Health System
South Bend, In, 46615

[Author]

Replies