Temp.release with Temenos Transact updates
This section highlights the instructions that are required when you upgrade to the GA release provided by Temenos.
What is the difference?
Upgrading to GA release requires an installation to the base of that particular GA release. Upgrading to the quarterly release ensures that the upgrade not only installs the GA release but also all the updates available till that point. Thus the upgrade takes the Client to a new GA release plus all the available updates till that point.
This temp.release package from the distribution team comes pre-packaged with a set of latest updates prepared for GA release. This saves enormous time to obtain the latest available updates and installation in bulk. Also, all these updates which are pre-installed in the GA temp.release are Regression tested and qualified.
Advantages
Upgrading to GA release has the following advantages:
- No need to manually download and install the updates available.
- Automatic process along with the upgrade.
- Upgrade project starts with the latest base.
- All known fixes are available before testing.
What are Updates?
Updates is the new release mechanism of maintaining fixes. This mechanism aims to release fixes proactively to clients at a component level. It replaces the old mechanism of Patches. This is easier to maintain and will help in encouraging the clients to take the updates on weekly basis rather than wait for Service Packs.
Previously, Service Packs used to follow the upgrade process where the entire bin and lib were replaced. But now the new mechanism removes the dependency constraints, which was a drawback in the patch mechanism.
T24.UPDATES service
After the upgrade process, if you have temp.release with new updates, then you need to run the T24.UPDATES service. If the upgrade is performed with a standard temp.release pack without updates, then you do not have to run the T24.UPDATES service.
If the following records are available in the EXCEPTION enquiry, then you need to authorise them before running the T24.UPDATES service:
- TSA.SERVICE , T24.UPDATES and its corresponding workload profile in TSA.WORKLOAD.PROFILE.
- The BATCH record, T24.UPDATES
- The STANDARD.SELECTION record, T24.UPDATE.RELEASE
The XXX/T24.UPDATES service releases the data records of Temenos Transact updates and completes the updates installation. In the batch record XXX/T24.UPDATES, you need to specify the Data field value as T24.UPDATES.
XXX is the master company mnemonic for a multi-company environment. For a single company environment, the TSA.SERVICE and BATCH record are available without the mnemonic.
SPF SYSTEM record before installing updates.
You can start the XXX/T24.UPDATES service by changing the SERVICE.CONTROL field of Temenos Transact.UPDATES service record to START.
After the completion of the XXX/T24.UPDATES service, the T24 Updates field of SPF SYSTEM record is updated with the names of all the installed updates.
You need to ensure that T24.UPDATES service is run before the conversion so that all the data items pertaining to updates are picked up.
Once a data item is successfully picked, the corresponding update is marked as completed by setting the value as C in the DATA.RELEASE field of T24.UPDATE.RELEASE.
COMO record of the T24.UPDATES service.
The temp.release pack with updates cannot be applied on the same GA release. For example, a temp.release pack with R11 updates cannot be used on a R11GA, it can be used on a release prior to R11GA.
In this topic