Professional Documents
Culture Documents
In this learning unit, you will learn about upgrading from one release of T24 to another.
1. The bankers are supposed to input all the transaction, if there are any pending
transaction those also have to be input before upgrade.
1.1 This is done, since there will be file layout changes taking place during upgrade.
3. You being a system administrator should also ensure to clear all the message
queues and shut down phantoms.
3.1 If the message queues are not cleared, there is likely chance of loosing information
/ advices.
1. You will have to configure T24 in order for T24 to know, where temp.release is
located. This is very much vital for a upgrade process.
2. You will create a non-hashed file called SYSTEM.
2.1 This directory could be under jBASE or T24 home
3. When you performing an upgrade in windows, create it has a hashed file.
In the screen shot, you are seeing the task performed by the program
T24.BUILD.LIBRARIES. It deletes the existing t24bin, t24lib and copies new t24bin
and t24lib from the temp.release directory.
2 The services are managed by the T24 Service Manager. Hence, the TSM record
of TSA.SERVICE , which is the T24 service manager is configured to be started.
1. You will start TSM in interactive mode(using –DEBUG option). Consequently the
respective number of agents are required to be started in individual sessions.
3. Post this service, updates will get installed (based on the products installed) and
SPF will be updated with the list of updates that have been installed.
1. There are various conversion programs that are released as part of a new T24
release. One record for every major release is released to CONVERSION.PGMS,
with an id of the release number, e.g. R10. All the unauthorised records of
CONVERSION.PGMS are to be authorised before starting the conversion
process.
1. You will start TSM in interactive mode(using –DEBUG option). Consequently the
respective number of agents are required to be started in individual sessions.
Which records are you going to process? Are the records in INAU status or IHLD status or LIVE status?
Assume that you are going to authorise customer records, therefore the records are in INAU status. You
may now select the records by using the SELECTION field.
SELECTION – here you may specify the selection criteria to select those customer records with the status
as INAU. Therefore the condition will be ‘WITH RECORD.STATUS EQ INAU’. You may specify more than
one condition as the field SELECTION is a multi-value field. If you do not specify any condition then it
selects all the INAU records of the file.
Now that you have selected the records to be processed, we have to determine what function should be
used on these records for processing?
FUNCTION – The field FUNCTION can contain any of the following functions A ,D , H , I P , R and V
Records selected by EBS.AUTO.FUNCTION are processed in groups, the size of each group (or sample)
being determined by the field SAMPLE.SIZE. After processing each group of records the program returns
the control to the EBS.AUTO.FUNCTION screen .
SAMPLE.SIZE – In this field you specify the number of records to be processed.
If you have hundreds of records to be processed how do you fetch each record from the group? The
records can be fetched based on the ID.
INPUT.BUFFER – To fetch the next record based on ID specify the keyword ID in this field.
KEYSTORKES – To process the records the sequence of automated actions can be specified in the
KEYSTROKES field. F5 is used to commit or authorise a record. F3 is used to scroll forward to the next
2. After all the records are processed the program returns the control back to the
EBS.AUTO.FUNCTION screen.
VERSION – Your record may comprise of multiple pages and to authorise such a
record you have to see all the pages before you authorise it. If you want to process
such records using the EBS.AUTO.FUNCTION utility you can make use of the
KEYSTROKES field where you may specify the action F3 to move forward to the next
page. But that seems to be a painful task when there are multiple pages, therefore you
may use versions to authorise such records. Lets say that you have a set of FT
records to be authorised and there are multiple pages to view in each record. So how
are we going to authorise these FT records?
A simple solution is to create a version for the FUNDS.TRANSFER application with
the required fields.
VERSION – After you create the version attach the version to this field in
EBS.AUTO.FUNCTION. The format is ,VERSION TYPE(Comma followed by the
version type)