Conversion from v3.8.1 to v5.5

Alise,

Copy your .idx and .msg files over to the new directory/box and start SMAT (either the GUI from the desktop or the old Xterm GUI).

You can then select the wanted messages and either resend them directly from SMAT to the thread in question or resend them to a file and then resend from the NetMonitor later.

Jim Kosloskey

Alise.

Last year we migrated our 70 production sites from (AIX 4.3.3) CL 3.5.5 to (AIX 5.3) CL 5.4.1.

I’m happy to provide details/scripts that we used.

You will find some usefull scripts for this sort of thing called

ascii_smat_to_nl.ksh

ebcdic_smat_to_nl.ksh

len10_to_nl.pl

that have a posted copy of the source code at URL

https://usspvlclovertch2.infor.com/viewtopic.php?t=1539” class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?t=1539

Alise.

I am happy to talk and I am (I think) 14 hours ahead.

Obviously, we proved that the translations were fine and tested the maintenance and housekeeping scripts (we use a menu for Ops rather than the GUI).

Our setup is to have one Cloverleaf site for each hospital site/application and we have one PAS application and three LAB applications sending information to Cloverleaf.

In essence, the business wanted the ability to backout if required and we did not want to be changing NetConfigs ‘on-the-fly’. The business wanted to leave the applications communication until we had been on-line on the new server for one week and then perform migration. This would avoid the migration relying on other support groups/vendors.

The solution was to create Cloverleaf ‘pipe’ and ‘crossover’ sites…

Pipe

A pipe site sits on the ‘old’ server and connects to the new servers ‘real’ Cloverleaf site.  The pipe site performed NO processing and just communicated messages to the real site and ACKs back from the real site to the application (we logged message control IDs through which is our ‘standard’).

We used pipe sites for all applications that connected (TCP) with the application as the client.

When one of these applications migrated to the new server, the pipe site was turned off (obviously making sure all messages flowed through)

Crossover

The crossover sites connected to a Cloverleaf ‘data receiving’ site (PAS and LABS) and communicated messages to the other server.

When an an application was migrated, the cross over threads were turned off.

I created scripts to automatically create the cross over sites and, as we had control of the PAS communications, we only needed a few pipe sites which we manually created.

I also created the scripts, called from a web page, to perform the migrations etc.

If you would like to discuss this, we can organise a time to suit – richard.hart@health.wa.gov.au

Hi Alise,

Just one small reminder: don’t forget to install the CL5.5 Rev1 patch, or you won’t be able to use the (GUI) SMAT tool!

Richard,

how did you go from 3.5 to 5.5? Did you just cooy iver config files or do you have to convert them?

One of our customers is still runing 3.5.2P on DEC Alpha and now migrating to AIX with 5.5.

Dirk

We converted from 3.5.2 to 5.1 some time back.

Be aware the requirements on tcl scripts change in the conversion from 3.5 to 3.8. Which if not modified will not run correctly.  We did it the hard way and ran the 3.8 upgrade then the 5.1 upgrade. That automatically added the modification to many of the scripts we use.

Dirk.

We found that the NetConfig files worked without modification, but, for completeness I wrote a script to change the NetConfig files for the logo and pathnames that referenced the root.

The modified NetConfig files were loaded in to the GUI, validated and saved.

We use TCL extensivley and our format in probably non-standard, so we don’t run the TCL update.  I  made a change to the procs, adding the shutdown a few years ago.