6/6/2019 Temenos T24

PGM.FILE
This file is an inventory of all T24 programs or processes that can be run from the action line, run from within the
'BATCH.CONTROL' environment, or used in the execution of report programs written using the T24 report
generator.
Whenever an application or batch job is selected, the PGM.FILE table is read to firstly see if the program or process
exists, and secondly to see what its characteristics are. If there is no entry on the PGM.FILE table then it cannot be
executed from within the T24 environment. If there is an entry then the system reviews its characteristics to ascertain:
i)What type of process is it? e.g. - is it only to be executed from the batch system? - does it maintain history?
(ii)What is the screen title?
(iii)Are there any special characteristics. e.g. - should the "!" function be disabled?
iv)If it is a batch job what is the actual program that is to be run?
This table can also hold the names of all subroutines within T24 (i.e. programs that are used but cannot be accessed
from the action line), and routines that are referenced by the report generator.
However it is not recommended that this file should contain all subroutines and hence be a complete inventory of all T24
software because
(i) there are better ways of maintaining an inventory of programs;
(ii) the size of the file, which is continually being referred to, would be larger than it need be.
Only the subroutines likely to be used by any report generator record should be loaded into this file.
ACTIVATION.FILE ACTIVATION.FILE
ADDITIONAL.INFO This field denotes whether underlying batch job uses Activation Files. Jobs that work on
APPL.FOR.SUBR Activation file do repeated selects on a file and process transactions. These jobs are set to run
BATCH.JOB AUTO throughout the day. Allowed only for batch jobs
BATCH.LIST.MAXIMUM
ADDITIONAL.INFO
BULK.NO
BYPASS.SEL Defines any special attributes or characteristics that a program or batch process must have. The
DESCRIPTION current values are:
JOB.RATING R (re-runable batch job)
K.TYPE .IDA (add/subtract 1 for the next record)
MT.KEY.COMPONENT
MT.KEY.FILE (During COB/Service,PURGE.HOLD.RPTS and PURGE.HELD.OUTPUT will select the whole
.ALL
PRODUCT HOLD.CONTROL records instead of doing select for every single company )
PROGRAM .NO! (no level down processing)
REC.VERIFY .NOD (no date record required)
RUN.INFO NOH (no hold facility after 1st input)
SCREEN.TITLE .NOU (no user checking)
SUB.PRODUCT
TYPE .PHN (phantom task allowed)
T24 Common HelpText .REF (non standard key display position)
Fields .PAR (parameter info for report records)
.GUI (application can run under GUI)
.NOG (application cannot be run under GUI)
.GAC (application uses GAC files. Refer to the GAC user guide)
.NOFS (application cannot be run in OFS. Refer to the OFS user guide)
.BDA (application may be run in a branch database)
.UNP (application will be taken for generic unauth processing)
.OEU (OFS flag for generic unauth processing)
.NUH (INAU records will not be put on HOLD by unauth processing)
.BLK (application may be run in bulk mode)
.HLD (New records of the specified application will be released in HOLD status during upgrade)
.INFORM To notify TEC whenever a record is updated in the Application(Creating records)
.CRITICAL (Stops the execution of a job immediately when an error is encountered)
.NUC (Not to use cache for transaction processing)
.NTX (No transaction management)
.KEY (Keys in activation file will be used instead of activation file content)
.NOL (Locking information not reported to user)
.BLB (Enables binary large object file creation)
.NBK (No Bulk mode processing)
.PREVIEW (Enabling preview of delivery messages)
.NJT (No JOB.TIMES record will be updated for the job with .NJT(No Job Times) )
(Fields will be validated in the sequence as defined in the template and not as defined in
.TOE
the Version)
R: the batch job can be re-run without restoring the data files if the process is interrupted.

192.168.1.56:9095/BrowserWeb/servlet/HelpServlet?command=view&language=GB&user=PAWAN1&product=EB&application=PGM.FILE&field=… 1/5
6/6/2019 Temenos T24

.IDA key generation will be automatic by adding (or subtracting) the number on to the previous
key to obtain the next (or last) key. Similar automatic key operation can be achieved through the
company record.
.NO! the ! or level down function is disabled for the program.
.NOD the program can run even when the DATES record is not established e.g. DATES program
itself.
.NOH the HOLD facility is disabled except for the first in put.
.NOU the user profile (ie. SMS) is not checked when this program is run.
.PHN the program is able to submit phantom tasks.
.REF the key to the records that the program is accessing will display in the top line on the right
of the screen instead of the normal position.
.PAR (arg 1, arg 2), where arg = argument. If a PGM.FILE record is a type 'R' then this field defines
the arguments to be used in the call to the T24 routine shown in field four. The names for the
arguments must be valid T24 keywords for which there are IN2... subroutines. For example
.PAR(AMT, CCY, *,, AMT,*,*) means that the routine in field four is to be called with seven
arguments. The first must be an amount field and will be checked by the IN2AMT routine; the
second must be a currency field and will be checked by the IN2CCY routine; the third argument is
not to be used; the fourth will be checked by the standard IN2 routine; the fifth will be checked
by IN2AMT; and the sixth and seventh are not to be used. It should be noted that any IN2 routine
that is required in the above example must be loaded as a 'S'ubroutines on PGM.FILE.
Except when .PAR is used, each program can have more than one of these additional
characteristics, if required. This is achieved by typing the values one after another as follows:
.NOD.NOU.REF
The values that are assigned should generally not be changed.
.UNP.OEU
The unauthorised records of this application will be processed by generic unauth processing. That
is will be processed by the batch job UNAUTH.PROCESSING. The INAU records will be deleted and
put on hold through OFS. When .UNP is specified .OEU should also be specified. Only then records
will be taken for unauth processing.
.NUH
The INAU records will be deleted through OFS but will not be put on HOLD by generic unauth
processing. Has significance only with .UNP and .OEU together.
.NTX
For record routines, do not call EB.TRANS if .NTX
.BLK
application runs in bulk mode when this is set
.HLD
New records of the specified application will be released in HOLD status after upgading from
lower release to higher release.Existing records will remain the same
.CRITICAL
Set .CRITICAL to a job when its expected to stop its execution as and when an error is
encountered. COB will not be continued till the error is rectified. PROCESS.STATUS and
JOB.STATUS will be set to ‘3’ in the BATCH file
.NUC
Caching mechanism is enabled by default for Batch processing. When there is a specific need to
not use cache, .NUC can be used. Every Read/Write operation will then happen directly from/to
the disk immediately and cache will not be maintained. It is however advisable to use cache to
improve COB performance.
.NTX
Transaction Management takes full control of all file updates happening at each transaction level
during online/cob. When there is a need for a job to run without transaction management, .NTX
option can be preferred. In such case, the updates to the disk will happen immediately.
.KEY
Generally, While preparing list of keys for activation file based job, contract Ids are selected from
the record content in Activation File. By enabling .KEY option, List is build based on the keys in
Activation file.
.NOL
When .NOL is set for a job, REPORT.LOCKS in VERSION will be reset to ‘NO’ thereby not reporting
any warning messages when waiting for record locks.
.BLB
Files are generally created based on database type (either XMLORACLE or J4/JR). But in oracle

192.168.1.56:9095/BrowserWeb/servlet/HelpServlet?command=view&language=GB&user=PAWAN1&product=EB&application=PGM.FILE&field=… 2/5
6/6/2019 Temenos T24

environment when .BLB is set, files will be created of type BLOB and not XML.
.NBK
There are two modes of processing a transaction online – bulk mode and standard mode. In bulk
mode, single or multiple OFS requests are processed under transaction boundary as a single
database transaction. When '.NBK' is set, transaction is processed in standard mode with the
updates happening to disk during commit stage
.PREVIEW
This option enables preview icon in desktop and browser tool. When transaction details are keyed
in completely, a facility to preview all delivery messages is enabled.
APPL.FOR.SUBR
This is a multi valued field. Standard T24 alphanumeric field.
Validation Rules:
A maximum of 35 characters may be entered.
Must be the key to a valid entry on the PGM.FILE file.
BATCH.JOB
Identifies the Batch job(s) when the program has been identified as type 'B' in field
1; or the routine to be called in the Report program produced by the report generator when the
record has been identified as type 'R'.
For a Batch job, this field contains the actual process name(s) that this batch job is to execute.
The values can either be program (typically subroutine) names, in which case they will be
prefixed by the @ sign; or they can be "voc" paragraphs such as JOURNAL.LIST.
For a multi-threaded batch job, the value can be either null or @BATCH.JOB.CONTROL.
If this field contains any value other than @BATCH.JOB.CONTROL , then, it indicates that the job
is single-threaded.
The routine or VOC paragraph entered should be valid.
For a report program, this field must contain the subroutine that is to be called (prefixed by the
@ sign). eg. @ MIDDLE.RATE.CONV.CHECK.
Validation Rules:
:
1)up to 32 alphanumeric characters Multivalue field
BATCH.LIST.MAXIMUM
Field BATCH.LIST.MAXIMUM is to hold the maximum number of contract id's in the multi-thread
batch list for the job. The default is 1 - to avoid any possible lock contentions but this will be
modified for each batch job as there are performance implications. The optimum is probably 20.
Validation Rules:
Standard T24 numeric field.
A maximum of 5 characters may be entered.
BULK.NO
Specifies the number of records that can be selected in bulk by a Job
Validation rules:
1)1-3 numeric
2)No of contracts to be bulked cannot exceed 200
BYPASS.SEL
Specifies whether selection criterira made on the .SELECT routine of batch job need to be
bypassed or not.
When updated with 'Y',system will select all the records from the file and send it to record
routine.when updated with 'N',System will follow normal procedure of using the criteria in the
.SELECT routine.
Validation rules:
1.Can be Y/N
2.This field can be updated with Y only if REC.VERIFY is set to "Y"
DESCRIPTION
This is a multi valued field. Standard T24 alphanumeric field.
Validation Rules:
A maximum of 35 characters may be entered
JOB.RATING
Help Text for this field is unavailable. Please refer to the T24 User Guides for further information.
K.TYPE
Help Text for this field is unavailable. Please refer to the T24 User Guides for further information.
MT.KEY.COMPONENT
This field is used to return a key for the file MT.KEY.FILE. This field is only used when

192.168.1.56:9095/BrowserWeb/servlet/HelpServlet?command=view&language=GB&user=PAWAN1&product=EB&application=PGM.FILE&field=… 3/5
6/6/2019 Temenos T24

MT.KEY.FILE has an entry.

Two parameters may be entered here, separated by a comma.
There are two formats available:
1) Parameter 1 can be a character for a field delimiter, with the second parameter being the field
number.
eg. *,1 - This will retrieve AAA in a multithreaded batch list key formatted AAA*BBB*CCC
2) Parameter 1 can be numeric for the character start position, with the second parameter being
the number of characters to return
eg. 5,3 - This will retrieve BBB in a multithreaded batch list key formatted AAA*BBB*CCC
A maximum of 35 characters may be entered.
MT.KEY.FILE
This is the file to read when MT.KEY.COMPONENT has an entry. The key returned from
MT.KEY.COMPONENT is used to read from this file. If the company (CO.CODE) contained in the
record returned is different from the current company, the records company is loaded.
A maximum of 35 characters may be entered.
PRODUCT
Standard T24 alphanumeric field
Validation Rules:
:
1)Mandatory input
2)A maximum of 2 characters may be entered.
PROGRAM
Identifies the name of the Program (application), Batch job, or routine used in the report
generator for which a record is being created.
Validation Rules:
1)Up to 35 alphanumeric characters
2)Mandatory Input
REC.VERIFY
This field will be updated by system with Y/N based the verification mechanism of the Job.
For a multithreaded job,if the record routine has got the mechanism to eliminate unnecessary
keys,then it returns -1(processing) or -2(eliminating).That is, when the record routine has the
intelligence to respond with a value back on the argument that it takes in, then this field is
updated with Y.
If the record routine does not follow the above concept,this field is updated with an N.
Validation rules:
1)System Updated field
2)Options are Y/N
RUN.INFO
Updated with the results of Conversion programs.
SCREEN.TITLE
Identifies the program title which will be displayed as a header when the corresponding
application (ID) is invoked in the action line.
Only used by on-line applications although can be entered for any type of record for reference
purposes.
Validation Rules:
:
1)1 to 32 alphanumeric characters Multivalue field Multilanguage Mandatory Input
SUB.PRODUCT
Standard T24 alphanumeric field.
Validation Rules:
:
A maximum of 20 characters may be entered.
TYPE
Identifies the type applicable to the program referenced by the ID.
Type :
H - A program that has this type maintains three files - the unauthorised, live and history files.
The unauthorised file is updated at Input; the live file at authorisation; and the history file
whenever there is an authorised change to a record. e.g MM.MONEY.MARKET.
U - A program similar to type 'H' except that history is not maintained. e.g. ABBREVIATION
L - A program that displays the data of a live file but does not allow updates. Updates to these
files would be controlled by the System automatically. e.g. STMT.ENTRY
T - A program that displays data in a table file (such as a list of keys) but does not allow update.
192.168.1.56:9095/BrowserWeb/servlet/HelpServlet?command=view&language=GB&user=PAWAN1&product=EB&application=PGM.FILE&field=… 4/5
6/6/2019 Temenos T24

e.g. LMM.CUSTOMER
W - A program that permits updates to a work or temporary file. A typical example would be the
REPGEN.OUTPUT program where print or display parameters for a report can be loaded.
B - A Batch job that can only be accessed during the 'off-line' processing in BATCH.CONTROL.
M - Main-line program that can be run from the action line but has no file directly associated with
it.
A - Access to T24 environment program. There is only one such program, called "EX" and it is this
program that is automatically initiated when a user logs into "INFORMATION" and enters the T24
environment.
S - Subroutine. A program used in the T24 system but one that is executed automatically
whenever required. It cannot be entered by the user either at the action line or from within the
Batch Control system. It is recommended that these are loaded only when they are needed by the
report generator. e.g. IN2... routines.
R - Report Generator routine. Report programs written via the report generator can use T24
subroutines. These type 'R' records define the routines to be used and the validation on the
arguments that are present in the calls.
Validation Rules:
The following values will be accepted:
H = History, Unauthorised + Live file
U = Unauthorised + Live file
L = Live only
T = Table
W = Workfile
B = Batch job
M = Main Line program (no file)
A = Access to T24 Environment
S = Subroutine
R = Report Generator routine.
T24 Common HelpText Fields

192.168.1.56:9095/BrowserWeb/servlet/HelpServlet?command=view&language=GB&user=PAWAN1&product=EB&application=PGM.FILE&field=… 5/5