[Todd Yingling]

Thanks Rob.  Ok, we’ll keep an eye out for a patch.

[Todd Yingling]

Hi Rob,

I def. will reach out to support.  Thanks for the reply.

Todd

[Todd Yingling]

Ha, yeah, we are finding that out 😀

I spoke to our 3 conversion analysts and found out only one of them has files with 1000 records or more per file (I thought they were all that way). The other 2 had their files built with 10 records or less from what I can tell after spot checking a few.

Thanks,

Todd

[Todd Yingling]

The folks here are using NL.  I appreciate the replies.

[Todd Yingling]

Hi Jim,

Thanks for your response.  

Yeah, we ran into that snag at first.  That was our initial change.  We now have 200 Max Messages with a Scan Interval of 15 and Read Interval of 5.  That did help greatly, but we still run into slowness issues eventually throughout the week.  I wasn’t sure what other options we had.  

Thanks again,

Todd

[Todd Yingling]

Thank you both.  That is very helpful.

[Todd Yingling]

Have you tried removing the comments from the switch command?  I believe this confuses the switch.  I understand you are commenting out the echos, but try removing them once.

[Todd Yingling]

Yes.  I built a fake msg and send it every 15 minutes via a cron job.  The vendor had to work with me to accept and actually delete the msg after they received it.

[Todd Yingling]

I moved to the option of sending a heartbeat msg every 15 minutes.  I know it’s unwanted traffic, but it seems to be working.  I haven’t had any calls since I implemented it.

[Todd Yingling]

I think I have it.  Use close after write and delay connection until needed. Also, remove the recovery procs (save, kill, resend).  There will be no validation of the ack either.

[Todd Yingling]

Hello,

Thanks again for all the replies.  

I just got this to work.

My scenario is set during downtime.  When our down stream system is down, ADT and ORM msgs will queue in our outbound thread.  We want the ADT to process before the ORM so I lower the ORM priority value.

When I first tested, I mimicked a down system by bringing the outbound thread in Cloverleaf down.  This is when I had issues.

When I brought down the system’s side and had Cloverleaf’s side up, but not connected, the priority worked.

Thanks again,

Todd

[Todd Yingling]

Thank you for your replies.

I think we’re going to escalate the issue with our vendor.  Hopefully, they can meet our needs with a mini-reg from an ORM msg.

Thanks again,

Todd

[Todd Yingling]

Jim,

No, only one outbound thread.  We have two inbound threads feeding one outbound thread.  

-Todd

[Todd Yingling]

Jim,

That’s exactly right; that’s the issue.

We’ve asked the vendor about creating a mini-reg from the ORM msg, but, of course, they said they didn’t have that option.  Before we escalated the issue, I wanted to see how the priority option worked in Cloverleaf.

Thanks,

Todd

[Todd Yingling]

Thanks Jim.  You’re right, I used tcl in the xlate’s copy to solve my issue.  

It’s nice to know about the product enhancement requests.  We are upgrading to 5.5 – maybe 5.6 in the near future – so I doubt I will request anything right now.

Thanks again,

Todd Yingling

[Author]

Replies