Using the auto upgrade method

This section shows you how you can expedite the Temenos Transact upgrade process.

Overview

This is an optional procedure. The auto upgrade process is activated by setting the Auto Upgrade field in the SPF SYSTEM record.

Impacts of auto upgrade

Activation of auto upgrade affects the following changes:

• The T24.PRE.RELEASE routine does not prompts for a user ID, instead it uses the pre-existing user ID set in the TSM record (in TSA.SERVICE).
• New TSA.SERVICE records have the same user added to the record, so that it can be auto authorised.
• The RUN.CONVERSION.PGMS records are released as LIVE records.
• Any unauthorised CONVERSION.ROUTINE records that needs to be replaced are deleted and the new released version is placed in the LIVE file to avoid conflicts.
• A copy of the list of records that are released is kept separately. This enables to view the list of records selected by the upgrade process even after the upgrade is completed. The F.RELEASED.RECORDS.LIST system file provides a key list for any user defined enquiry or investigation reports.
• The multi-job services (such as T24.FULL.UPGRADE) calls the standard processing stages in a sequential basis. The first job runs the upgrade, the second runs the conversions and the third runs the auto- authorise stage.
• The auto- authorise only attempts to authorise the records, which are in the release control list. The records left in IHLD status cannot be authorised, and hence, you need to authorise them manually.
• The logging process of individual stages continue to be written in &COMO& and to screen. But for auto processing, they are written to the Temenos Transact logging files (which can be used by external monitoring software, such as Splunk). This provides the ability to monitor the start and finish stages externally .

Prerequisites

Read the following prerequisites before you start with the auto upgrade process:

• Ensure that you read the release notes and technical highlights of the release, as it may ask you to perform some key procedures before starting with the upgrade process.
• The release highlight details the changes made in the release. You should read them as it provides information on the scope of the changes to the system in areas which may be of particular interest to you.

Extracting Temenos Transact temporary release package

For more information, see Extracting Temenos Transact temporary release package.

Creating the temp.release record

For more information, see Creating the temp.release record.

Pre-upgrade checks

For more information, see Pre-upgrade checks.

Updating T24 libraries

For more information, see Updating Temenos Transact libraries.

T24.PRE.RELEASE

T24.PRE.RELEASE runs the pre-release updates. You can execute T24.PRE.RELEASE in TAFJ command shell by typing tRun T24.PRE.RELEASE.

T24.PRE.RELEASE has the following properties:

• When you activate auto upgrade in SPF, T24.PRE.RELEASE logs into Temenos Transact automatically using the user ID attached to the upgrade service.
• After logging into Temenos Transact, T24.PRE.RELEASE upgrades a set of data records as shown below.

  

• T24.PRE.RELEASE releases the following service records:
  • TSM
  • T24.UPGRADE

  The service control of these service records are set to START so that these services can start automatically when required.

• T24.PRE.RELEASE also releases the following supplementary records for the above services:
  • PGM.FILE
  • BATCH
  • TSA.WORKLOAD.PROFILE

Auto upgrade service

This section shows you the different stages of auto upgrade service.

You need to run one of the TSA.SERVICE listed below for auto upgrade.

The BATCH records with multiple jobs are listed in the below screen.

The BATCH records in the above screen contains combination of jobs such as upgrade, pre-conversion, conversion and authorisation. Therefore, it reduces the need of running separate services for each of these jobs.

Sample screens of the BATCH records with multiple jobs.

Below is the sample of running agent.

 COMO tSA_6_20160412_16-51-29 established Tue Apr 12 16:51:30 IST 2016
<como>
<agent>6</agent>
<processid>171176290</processid>
<portno>4</portno>
Agent 6 started 12 APR 16 16-51-29
Agent's Process id 171176290
<servername>LF3PG152</servername>
Running on server LF3PG152 PortNumber 4
Next Service Current Service
_0__6_12 APR 2016_16:51:30:768_SELECT F.COMPANY WITH CONSOLIDATION.MARK EQ "N" Selected=8 time=0secs
<service name = BNK/T24.FULL.UPGRADE>
<process name = BNK/T24.FULL.UPGRADE>
<job name = T24.UPGRADE> 
_BNK/T24.FULL.UPGRADE_T24.UPGRADE_6_12 APR 2016_16:51:31:070_Standard multi-thread job
_BNK/T24.FULL.UPGRADE_T24.UPGRADE_6_12 APR 2016_16:51:31:070_Calling load routine
JEDIFILENAME_SYSTEM is set to: SYSTEM
_BNK/T24.FULL.UPGRADE_T24.UPGRADE_6_12 APR 2016_16:51:31:100_SELECT F.COMPANY Selected=10 time=0secs
_BNK/T24.FULL.UPGRADE_T24.UPGRADE_6_12 APR 2016_16:51:31:100_Starting job
_BNK/T24.FULL.UPGRADE_T24.UPGRADE_6_12 APR 2016_16:51:31:110_Allocating List File for BNK/T24.FULL.UPGRADE-T24.UPGRADE-1
_BNK/T24.FULL.UPGRADE_T24.UPGRADE_6_12 APR 2016_16:51:31:120_Updating the Locking with BNK/T24.FULL.UPGRADE-T24.UPGRADE-1 and F.JOB.LIST.2
_BNK/T24.FULL.UPGRADE_T24.UPGRADE_6_12 APR 2016_16:51:31:130_Calling..T24.UPGRADE.SELECT
_BNK/T24.FULL.UPGRADE_T24.UPGRADE_6_12 APR 2016_16:51:31:130_Control list..
_BNK/T24.FULL.UPGRADE_T24.UPGRADE_6_12 APR 2016_16:51:31:140_Using list file F.JOB.LIST.2
_BNK/T24.FULL.UPGRADE_T24.UPGRADE_6_12 APR 2016_16:51:31:140_Control list processed
</job>
<job name = PRE.RUN.CONVERSION> 
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:31:160_Standard multi-thread job
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:31:170_Calling load routine
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:31:190_SELECT F.CONVERSION.PGMS Selected=24 time=0secs
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:31:210_Starting job
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:31:220_Allocating List File for BNK/T24.FULL.UPGRADE-PRE.RUN.CONVERSION-2
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:31:220_Updating the Locking with BNK/T24.FULL.UPGRADE-PRE.RUN.CONVERSION-2 and F.JOB.LIST.2
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:31:230_Calling..PRE.RUN.CONVERSION.SELECT
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:31:230_List starting from 0 keys processed so far 0
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:31:240_Building from list passed
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:31:280_List starting from 68 keys processed so far 68
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:36:925_ Checking the routines of CONV.EB.UNAUTH.TXN.POSITION in R14
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:36:935_ Checking the routines of CONV.REPO.R14 in R14
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:36:935_ Checking the routines of CONV.DX.ORDER.201307 in R14
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:36:945_ Checking the routines of CONV.DX.TRADE.201307 in R14
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:36:945_ Checking the routines of CONV.FACILITY in R14
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:37:375_ Checking the routines of CONV.AA.ARR.CHARGE.201405 in R15
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:37:375_ Checking the routines of CONV.AA.PRD.CAT.CHARGE.201405 in R15
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:37:385_ Checking the routines of CONV.AA.PRD.DES.CHARGE.201405 in R15
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:37:385_ Checking the routines of CONV.AA.PRD.PRF.CHARGE.201405 in R15
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:37:395_ Checking the routines of CONV.AA.SIM.CHARGE.201405 in R15
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:37:405_ Checking the routines of CONV.AA.ARR.BALANCE.MAINTENANCE.201403 in R15
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:38:235_ Checking the routines of CONV.USCORE.PARAMETER.201505 in R16
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:38:245_ Checking the routines of CONV.AA.ARR.ACCOUNTING.201505 in R16
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:38:245_ Checking the routines of CONV.AA.PRD.CAT.ACCOUNTING.201505 in R16
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:38:255_ Checking the routines of CONV.AA.PRD.DES.ACCOUNTING.201505 in R16
_BNK/T24.FULL.UPGRADE_PRE.RUN.CONVERSION_6_12 APR 2016_16:51:38:265_ Checking the routines of CONV.AA.PRD.PRF.ACCOUNTING.201505 in R16
</job>
<job name = RUN.CONVERSION> 
_BNK/T24.FULL.UPGRADE_RUN.CONVERSION_6_12 APR 2016_16:51:41:615_Standard multi-thread job
_BNK/T24.FULL.UPGRADE_RUN.CONVERSION_6_12 APR 2016_16:51:41:615_Calling load routine
_BNK/T24.FULL.UPGRADE_RUN.CONVERSION_6_12 APR 2016_16:51:42:005_Starting job
_BNK/T24.FULL.UPGRADE_RUN.CONVERSION_6_12 APR 2016_16:51:42:005_Allocating List File for BNK/T24.FULL.UPGRADE-RUN.CONVERSION-3
_BNK/T24.FULL.UPGRADE_RUN.CONVERSION_6_12 APR 2016_16:51:42:005_Updating the Locking with BNK/T24.FULL.UPGRADE-RUN.CONVERSION-3 and F.JOB.LIST.2
_BNK/T24.FULL.UPGRADE_RUN.CONVERSION_6_12 APR 2016_16:51:42:015_Calling..RUN.CONVERSION.SELECT
_BNK/T24.FULL.UPGRADE_RUN.CONVERSION_6_12 APR 2016_16:51:42:015_SELECT F.COMPANY Selected=10 time=0secs
_BNK/T24.FULL.UPGRADE_RUN.CONVERSION_6_12 APR 2016_16:51:42:095_List starting from 0 keys processed so far 0
....
</job>
<job name = T24.AUTHORISE> 
_BNK/T24.FULL.UPGRADE_T24.AUTHORISE_6_12 APR 2016_16:51:42:145_Standard multi-thread job
_BNK/T24.FULL.UPGRADE_T24.AUTHORISE_6_12 APR 2016_16:51:42:145_Calling load routine
_BNK/T24.FULL.UPGRADE_T24.AUTHORISE_6_12 APR 2016_16:51:42:155_SELECT F.MNEMONIC.COMPANY Selected=10 time=0secs
_BNK/T24.FULL.UPGRADE_T24.AUTHORISE_6_12 APR 2016_16:51:42:165_Starting job
_BNK/T24.FULL.UPGRADE_T24.AUTHORISE_6_12 APR 2016_16:51:42:175_Allocating List File for BNK/T24.FULL.UPGRADE-T24.AUTHORISE-4
_BNK/T24.FULL.UPGRADE_T24.AUTHORISE_6_12 APR 2016_16:51:42:175_Updating the Locking with BNK/T24.FULL.UPGRADE-T24.AUTHORISE-4 and F.JOB.LIST.2
</job>

When and why to use automated services?

Since, the auto upgrade is an optional feature. Below are the scenarios and reasons that specifies why you should use this feature.

Test and Live update

While upgrading the Temenos Transact system, you ensure that the impact and integrity of the upgrade is maintained. Running each upgrade process individually and manually helps you to verify the released data and its corresponding conversions. In many scenarios, a test upgrade on a copy of Temenos Transact system is carried out with notes on how the release may impact the system. Later the live systems goes through a full upgrade process. During this full upgrade process, the live system is made offline for the shortest duration possible.

Using the auto upgrade option helps you to complete the second stage much faster, thus reducing the offline durations.

Multi-tenancy

A Temenos Transact system operator controls and maintains multiple Temenos Transact clients (Multi-Tenancy). The need for automated processing increases because the offline window becomes more critical due to impact on several Temenos Transact systems. Therefore, the auto upgrade option becomes important in this scenario with the use of external monitoring and configuration tooling. Though the same test or live upgrade procedures are performed for a single Temenos Transact system.

Non-Live systems

An upgrade on a system becomes non-critical when you use a demo System. Therefore, you can perform the auto upgrade process as a primary upgrade on the demo system. Here you can remove the scope of test upgrade.

At the user discretion

If the Temenos Transact client is satisfied with the process and aware of the implications, auto authorisation can be used as the primary upgrade method. While it uses the same internal processes to run the upgrades and conversions. The addition of the auto authorisation stage may or may not match your control procedures. You can activate or deactivate the auto processing using the value set in the SPF application.