Datasheet

Release Notes - New Features included in Release 2.4.0
Page 80 of 89
5.1.1.2 Customisation – Impact Analysis of Screen (‘cct’ File) Changes (SR4359)
The program cctupdate has been enhanced to produce a summary report. The report details the
impact of cct’s that are being delivered on a CD and it should be used when planning the tasks
involved in implementing a Standard or Patch Release.
This report is produced in transaction code order (thus one cct file is likely to reflect into several
transactions), and shows the effect of each changed cct file. No entry is present if the two cct files
are identical.
The report is called CCTIMPACT_lang_detail.LIS, e.g. CCTIMPACT_E_F.LIS for full details for
English cct files.
Each line will show which cct might be affected by a particular type of change:
• Version Error: This indicates that a change has been detected in the cct files and an
inappropriate change applied to the Major and / or Minor version numbers. This should be
reported to SSI.
• SDK change: A change may be required to an SDK, Webcall or Batch Load Wizard
program.
• TIGI change: A change may be required to a TIGI interface. Also included in this category
are Application Designer transactions and TROPOS Active events.
• AUDM change: A change may be required to an AUDM auditing facility.
• Deferred Queue: A change may be required to a Deferred Queue entry.
• Customised Template: A change may be required to a globally customised cct file.
If a level of change might be required, then this is indicated by a ‘Y’ in the appropriate column. In
addition, the database is interrogated to determine whether a change is actually required. If actually
required, then the ‘Y’ will be followed by a ‘*’, and details of the actual entry requiring change is
given at the end of the report. Note that this will show those entries which must be reviewed. It is
possible that although a particular transaction is used, it does not actually use any of the datanames
that have changed.
The utility will access the TROPOS database when identifying the impact on TIGI, AUDM,
Deferred Queue and Customised Templates. Currently, there is no definition of the transactions that
are used by SDK’s, Batch Load Wizard or other applications written by the user, such as Browser
Interfaces. To enable this, the program makes use of a text file that can be maintained by a text
editor and stored in the ‘PKEEP’ location of the relevant database. The file is called SDK.DATA.
To identify which transactions are used by which SDK's or other applications, each line should
contain the transaction code, a space and then a descriptive entry which will identify the actual SDK
etc. application.
There is a script supplied (cctversion) which takes 3 parameters:
• New directory
• Old directory – optional defaulting to CCT_CCT_PATH (If entering a variable, then it must
be entered in UNIX format even when running on NT (e.g. $CCT_SSI))
• Language – optional, defaulting to E for English