Datasheet

Release Notes - New Features included in Release 2.4.0
Page 82 of 89
• Continue with the standard installation of the software. Apply the changes to the
applications, etc, that are identified on the report as required.
To compare the handover cct files with the live cct files and identify the effect on the handover
database.
The report can also be run to compare the handover to the live system. This can be useful as a
‘sanity’ check before the migration, but also if the CD was installed before running the report. In
which case, log into the hand system, set your default directory to PWORK and establish the
location of the cct files for the handover and live databases.
• Ensure the PKEEP file SDK.DATA is up to date for all SDK, Browser, BLW, etc,
applications. The command format is:
cctversion new_directory old_directory language
e.g. for UNIX
cctversion /tropos/hand/tropos/screens/cct/ssi /tropos/live/tropos/screens/cct/ssi E
or for NT
cctversion \tropos\hand\tropos\screens\cct\ssi \tropos\live\tropos\screens\cct\ssi E
You will find the two output reports as before.
To compare the handover cct files with the live cct files and identify the effect on the live
database.
This is exactly as above, but you should log into the live system. This option should be run prior to
performing the migrate to establish the impact of the changes on the live database. Note that the cct
file locations are also the same, as the handover cct files are always newer (or the same) as the live
cct files.
• Ensure the PKEEP file SDK.DATA is up to date for all SDK, Browser, BLW, etc,
applications (As this file is located in PKEEP, it is database specific).
Manual Set-Up Procedures
Create the file SDK.DATA in PKEEP identifying the SDK applications etc. used.