› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Cloverleaf 5.6
Thanks…
Tom Rioux
Baylor Health Care System
One of them is using 5.6 since more then 6 weeks.
Unfortunaly we do not have one running one unix. Has anyone else done this?
Dirk
Thanks….Tom Rioux
Hope I’m not stating the obvious, but have you looked through this thread?
It has the same topic title as the new one you created.
If anyone ACTUALLY IS on 5.6, then I would love to hear how they are doing in production.
I’m getting close.
I’ve installed QDX 5.6 on a new AIX 5.3 test LPAR last week.
Soon I will be proceeding to do hcilicset and start migrating our master site and some test sites.
Russ Ross
RussRoss318@gmail.com
We’ve been running baseline validation with 5.6 (running production files through and comparing output) in our DEV environment and have found no issues; so far, so good.
Yes, we are live on CL5.6 AIX 5.2 since 2/26. The application is working great. I love that we can now use the SMAT tool with the current message log. And the disable feature in the Xlate is another great tool. Once we put recover_56 in place, that doused the multiple state 14 messages. We did run into an issue with our hostserver that seems specific to our server. We have been working with R&D and tech support to resolve.
Tables now are created with .tbl extensions. Check your documentation for more information.
Hope this helps, Mary.
Mary, can you supply us with more details about your hostserver problems? We have planned to migrate to Cloverleaf 5.6 this Summer from our current 5.3 platform on AIX5.2 (eventually to AIX5.3).
We have checked all the system requirements per the documentation and set/verified the settings.
Your feedback would be most helpful.
Thanks.
We are running AIX 5.2.
We have run into two issues thus far. One is an interface with a lot of Tcl code in it that reads in and move files around. Initially this process panicked a few times. I was not able to determine why. I reworked the file and directory permissions and it has worked fine since.
the other anomaly was a seizure in the monitor daemon for one site. Had to take the site down (stopped all processes and the site daemons) and restart. No reoccurences. the processes all stopped nicely, they did not act like they were having a problem other than data was not flowing, with the monitor daemon hung it was hard to tell what was going on. I am not overly concerned about this unless it happens frequently. we have seen sites get “locked up” before in 5.3.
We’ve now been running over a week with no issues at all. Message volume is well over 1 million in the last two weeks.
Kevan Riley