thanks for the reply.  If by some miracle I come across a definitive answer on the use of interface engines for CCD documents for future stages, I’ll post it on Clovertech.

But I was wondering if using Cloverleaf 5.7 to move CCD data between other ‘CCD certified’ systems meets the certification requirements.

I’ve not been able to find a definitive answer…Read more

I emailed the remote system’s network admin guy, to see if they can release the port.  We agree that the admins of the VPN/firewall should fix the problem, but cannot count on that happening.

We haven’t ruled out simply bouncing the thread via a ksh script scheduled in cron, or through a qdx alert.  But the other options will be…Read more

we’re going to get with the vendor system’s Cloverleaf programmer and hash out the options.  

Hope

I have read that using Muli-Server can solve this problem in some of the other posts.  However, I’m concerned that this will create a new connection but leave the “hung/stale” connection out there.  Am I thinking correctly about this?  Or, will Cloverleaf or the OS eventually time-out and close the previous TCP connection that was…Read more

in your response, you mentioned the Close After Write protocol option, and other posts involving problems with VPN’s.

We are receiving results from another Cloverleaf engine through a VPN, which closes the connection after 1 hour of inactivity.  The result is that our inbound thinks it’s still connected, while their outbound goes to…Read more

I’m calling a tcl proc to shut down the process using the system command:
 set stopProc [catch [system hcienginestop -p $process]]

Then in shutdown mode, a different tcl proc is kicked off in the background to start the process when certain conditions are met:

     shutdown {
        echo “starting shutdown mode”
       # check to see…Read more

I’m working on a tps pre-proc to stop a process when certain conditions are met.  I want to keep the current message in the recovery database, but haven’t figured out how to do so without creating broken pipes and/or leaked handles in the TPS interpreter.  

This happens when I use return 0 to exit the proc (after issuing the…Read more