1|Page Hayyan| T24 R14

T24 Kick Start Training - JSBL 2019

Sr. Topic Page

1 Architecture 2

2 Commands 3

3 Routine Types 4

4 Program 5

5 Enquiry 7

6 Enquiry With Authorize Option 16

7 Mainline Routine 17

8 Service 19

9 Save List 24

10 BCON 27

11 VOC 37

12 Template 38

13 Template Browser Input 47

14 Version 48

15 EB.API 50
2|Page Hayyan| T24 R14

Architecture

Browser TC Server Database

Folders
T24.BP (core Applications)
CORE.BP
ATM.BP
CREDIT.BP
TR.BP
TEST.BP (dev. env. testing folder)

Company
FBNK -> Pakistan
FBHN -> Bahrain

File Types
PGM -> Program file created to entertain Mainline routine, Service, Template.
It is used to convert the logic into executable form.

Naming Conventions
 All naming conventions should be in CAPITAL letters
 Dot (.) is used to combine names (PK.M.CUS.NIC.EXT)

PK.E… Enquiry (Single/no file)

PK.M… Main Line Routine
PK.B… Service
PK.V.VAL… Version Validation
PK.V.AUTH… Version Authorization
PK.V.INP… Version Input
PK.E.CONV… Conversion Routine for Enquiry
PK.H… Template History (maintains all records, history, live & un-authorize)
PK.L… Template Live (maintains only live records)

Variable Declaration
Y.NAME = ‘’ | “” User defined variable starts with Y.
MY.ARY = ’’ | “” Array declaration
FN.CUST File name (Application) for customer start with FN.
F.CUST File location (Application) starts with F. but follow same word as per
defined in FN.
3|Page Hayyan| T24 R14

Commands
Application -> System Table
Template -> User Defined Table

jshow –c Routine To find the location specified Routine in every

folder
BASIC –I../T24_BP <folder> <Routine> To compile specified Routine
CATALOG <folder> <Routine> To create exe of specified Routine
CT <folder> <Routine> View only mode
JED <folder> <Routine> Edit mode or create / update file
ETS <enter> EX <enter> Login into the Black Browser environment
FI Save & Exit file (Routine)
EX Exit without saving file (Routine)
FS Save only (Routine)
FD Delete file (Routine)
LIST <Company>.<Application> View data
SEARCH <folder><enter> Search the specified keyword in all routines
<keyword><enter><enter>,*<enter> present in specified folder
LIST <folder>
F3 Navigate next line (Build Menu)
F2 Navigate previous line (Build Menu)
F5 Commit (Build Menu)
Debug Mode ‘S’ Next Step
Debug Mode ‘V’ Display Value
Debug Mode ‘C’ Continue
Debug Mode ‘Q’ Quit
LO Log Out (Black)
LIST F.TSA.SERVICE ‘Service’ Check if service running
LIST F.TSA.STATUS WITH CURRENT.SERVICE EQ Check service running agents
‘Service’
LIST F.LOCKING LIKE …Service… Display the service content
QSELECT F.JOB.<ServiceContent> * How much record pending in service job
telnet <localhost> <Port#> Reset TC Server
Choose [2] ‘Y’ <enter>
L <keyword> Search in file (Routine)
cp <folder>/<Routine> ../<Routine><enter> Copy file (Routine)
LIST F.DATES TODAY Check environment date
JED FBNK.<APPLICATION> ‘Column’ To clear column data from application
LIST FBNK.<APPLICATION> ONLY To check the ID of Application / Template
<Alt>+V Paste the copied text
<Ctrl>+W Delete word in Black
<Ctrl>+K Delete line in Black
<Ctrl>+V Format code in Black
DECATALOG <folder><Routine> Delete the exe file
EB.COMPILE <folder><Routine> Compile in previous version BASIC command
is unavailable
JED <folder> I_F.<APPLICATION/TEMPLATE> Display all column name + positions
SELECT <APPLICATION> WITH @<column> LIKE Select the records with condition on column
…<string value>
4|Page Hayyan| T24 R14

Routine Types
All routines are Application Version dependent.

Input Fired during input

Validation Fired during validation process
Before Authorization Fired before authorization
Authorization Fired during authorization
ID Fired when record is opened

Abbreviations
VI Version Insert
CU/CUS/CUSTOMER Customer
AC/ACCOUNT Account
ENQ/ENQUIRY Enquiry
BCON Build Control
LT Local Table / Column field
LRT Local Reference Table
EI/ENQUIRY Enquiry Insert
DD DL Define
FT/FUNDS.TRANSFER Funds Transfer
5|Page Hayyan| T24 R14

Program
The program is used to test the routine and code in Black. The program does not require PGM.FILE
to execute.

Sample:
Create a routine with simple functionality (calculator)

Create a program to test the above Subroutine

6|Page Hayyan| T24 R14

Run the Program

7|Page Hayyan| T24 R14

Enquiry
The enquiry is the extraction of Data into Browser. There are 2 types Single File & No File.
1. Single File Enquiry
a. Single File Enquiry (Extension using conversion routine)
Add column in enquiry from another application by defining conversion routine for each
column
2. No File Enquiry

Enquiry – Single File

Single file enquiry only has one component because it retrieves the data from single Application
which by default resides in an array.
1. Enquiry
2. Enquiry + Conversion Routine (for retrieving a column from other application)

Process-Single File:

EI,<enter>
Name<enter> (PK.E.CUST.TEST)
Page Size -> 1,49
File Name -> Application (CUSTOMER)
Field Name -> @ID
Column.1 -> 1
GB Field Lbl.1 -> Customer ID
F5

Sample:
Task is to create single file enquiry for F.FUNDS.TRANSFER application
8|Page Hayyan| T24 R14

After gathering all info related to create enquiry then go to ENQUIRY on browser mode

Enter enquiry name

9|Page Hayyan| T24 R14

LRT field (CONSUMER.NO – 25)

Account Title from <ACCOUNT>

DAO from F.USER using (R.USER)

To authorize enquiry
10 | P a g e Hayyan| T24 R14

To view created enquiry

11 | P a g e Hayyan| T24 R14

Enquiry – No File
When we need to retrieve data from multiple Applications we use No File Enquiry which contains 3
components.
1. Routine -> Main logic (Query)
2. Standard Selection -> Mapping b/w Routine Array and Enquiry + Searching Criteria
3. Enquiry -> Pointer to Routine

Process-No File:

ROUTINE

Does not require any PGM.FILE or EB.API

Make sure to define Array in routine name which contain final data

$INSERT I_ENQUIRY.COMMON should be added in every NoFile enquiry routine

Finally the array must be populated with data

12 | P a g e Hayyan| T24 R14

STANDARD SELECTION

Creating Standard Selection

Mention Array as per routine R->Routine and specify Routine Name

Adding Searching Criteria

All components need to be modified for searching criteria (Routine -> Standard Selection -> Enquiry)

To modify Standard Selection we need to add Usr Field Name.2

Y.ID mentioned in routine S-> Search and 2nd S-> Single value
13 | P a g e Hayyan| T24 R14

To modify Routine we need to use LOCATE as per mentioned below

If Y.ID is null then ELSE is executed so the search criteria is not mandatory
D.FIELDS<1> always be ‘1’ no matter how many searching criteria will be added
D.RANGE.AND.VALUE<POS> also remains same every time

To modify Enquiry we need following additions

Selection Flds.1 as per mentioned in Routine (Y.ID)
Txn Id is the Label to display in Enquiry
Sel Fld Oper.1 is the Operand (EQ->Equal)
14 | P a g e Hayyan| T24 R14

ENQUIRY

File Name -> Standard Selection, Fixed Selection.1 -> MY.ARRAY as per Routine’s data array

Make data available for all columns

Operation always same and mention actual data Array (MY.ARRAY)

Conversion defines the actual positioning of data in MY.ARRAY, ^->Separator in Routine
1-> start value in data Array 2nd 1-> ending value in data Array
15 | P a g e Hayyan| T24 R14

Field Name is the actual data variable as per Routine

RESULT

Optional Search Criteria

If Txn Id search criteria is null

16 | P a g e Hayyan| T24 R14

Enquiry With Authorize Option

To add a button / hyperlink in an Enquiry with $NAU records following steps will be performed:

1. Go to Enquiry

2. Update Enquiry Name = Version name

A -> Authorize
@ID -> field to authorize
3. Update Label Field
@ID -> to get field on hyperlink / button click
1 -> to get single record for each hyperlink / button click

Result
17 | P a g e Hayyan| T24 R14

Mainline Routine
Mainline routine is for extraction of Data from File to Database or from Database to File. Single
Threaded / Agent.

Steps:
1. Create the file
2. Program the file
3. Compile & Catalog the file
4. Create PGM.FILE in order to execute
5. Run the Program (Main Line Routine)

SAMPLE:
1) Create the file

2) Program the file

3) Compile

Catalog
18 | P a g e Hayyan| T24 R14

4) Create PGM.FILE

5) Run the Program in ETS mode

19 | P a g e Hayyan| T24 R14

T24 Service
Service is the routine file which has multiple Agents.
There are 4 routine files and 4 system files which are needed to create a service.

4 Routine Files
I_PK.B.FT.SBP.EXT.COMMON Global variable declaration / db variables
PK.B.FT.SBP.EXT.LOAD Variable Initialization
PK.B.FT.SBP.EXT.SELECT Getting data from File / Application
PK.B.FT.SBP.EXT Main Logic routine file

COMMON:

LOAD:
20 | P a g e Hayyan| T24 R14

SELECT:

MAIN:
21 | P a g e Hayyan| T24 R14

4 System Files
PGM.FILE Type of file ‘B’
BATCH Environment foreground / background, Frequency
TSA.WORKLOAD.PROFILE Number of Agents assigned
TSA.SERVICE Define Service related information

PGM.FILE:
Type = B (batch), M (mainline)
Product = EB
22 | P a g e Hayyan| T24 R14

BATCH:
Batch.Environment = F (foreground), Job.Name = PGM.FILE NAME
Frequency = D (Daily)

TSA.WORKLOAD.PROFILE:

Agents.Required = 1 (1-25)
23 | P a g e Hayyan| T24 R14

TSA.SERVICE:

User = ITO.OFS.USER01 (t24dev OFS User)

Service.Control = Stop/Start
24 | P a g e Hayyan| T24 R14

Run Service
TSM and TSA.Service both should be started in order to run a service.

Running without Debug / Fantom mode

1. Don’t need to clear Status
2. Don’t need to clear Job list
3. Don’t need to stop TSM
4. Start TSA.SERVICE
5. START.TSM

Running with Debug mode

1. Stop TSM

F5 Commit
25 | P a g e Hayyan| T24 R14

2. Clear Job list

This will clear 7th job list

To find job list

3. Clear Status

4. Start TSM
26 | P a g e Hayyan| T24 R14

5. Start TSA.SERVICE

6. START.TSM –DEBUG

Service Details
27 | P a g e Hayyan| T24 R14

Save List
Contains (Routines [&,/] Data for DL) to create a single list for BCON generation. Routines are logic
and DL is record list data definitions (all items other than routines).

a. Routines -> Routine SAVEDLISTS will directly mentioned in BCON generation

JED &SAVEDLISTS& RTN.MANTIS.DATE<enter>
Routine name <ESC>
FI

b. Record List (DL) -> Using DL SAVEDLISTS we create DL.DEFINE then DL.DEFINE will be
mentioned/part of in BCON generation not directly DL SAVEDLISTS.
JED &SAVEDLISTS& DL.MANTIS.DATE<enter>
Items include other than routine
(PGM.File/Version/LT/Enquiry/Standard.Selection/File.Control etc.) <enter>
PGM.FILE>Routine name<ESC>
FI

PGM.FILE PGM.FILE>ROUTINE
VERSION VERSION>APPLICATION,VERSION
LT
SS
BATCH
TSA.WORKLOAD.PROFILE
TSA.SERVICE
EB.API

DL.MANTIS.DATE for SERVICE

PGM.FILE>(Only main Service ROUTINE)
BATCH,TSA.WORKLOAD.PROFILE,TSA.SERVICE>(Only main Service Routine file)
28 | P a g e Hayyan| T24 R14

Process-DL.DEFINE:

DD,<enter>
I<enter> (Input)
Name: MANTIS.DATE
Select Lists: Now mention SAVEDLISTS name
F5->Commit
29 | P a g e Hayyan| T24 R14

6. SELECT.LIST (enter DL.MANTIS.YYYYMMDD), (9) PGM.FILE (10) Routine name should populate

F5 to COMMIT (FINSHED DL.DEFINE)

30 | P a g e Hayyan| T24 R14

BCON (Build Control)

The build control is a T24 package which contains all the components (Routines [&,/] DL) ready to
deploy on UAT/Production server. Below are the steps to create BCON.

1. Generate BCON (Process to specify the components for BCON generation)

2. Verify BCON (Verification step to finally verify the BCON components before check in)
3. Check-In BCON (Checked in to the specified server)

Generate BCON
(Once generated for further changes add .01+ onwards at the end of BCON filename instead of
delete and regenerate)

Process-Both Routine + DL: (needs to have DL.DEFINE for DL)

I<enter>
Enter name without ‘RTN’ (Mantis ID. Date ex: 20831.20190830)
(if for any reason creating another BCON for same Mantis ID on same day we add .01 .02 etc.
after date)
Enter Package name in 1. & 2.
3. ACTION> ‘S’ (Save, R->Release)
(F3 to navigate next line F2 to previous line)
7. Folder of Routine (mostly CORE.BP)
(for adding multiple folders of routine <shift> + ‘<’ it will create 7.2)
(to remove added folder location ‘-‘<enter>)
8. SL-RTN(Mantis.Date)
80. Y (clear process log)
F5 to commit

Requires Routine + DL.DEFINE for PGM file:

1. Create SAVEDLISTS (RTN.MANTIS.YYYYMMDD) + (DL.MANTIS.YYYYMMDD)

31 | P a g e Hayyan| T24 R14

2. Create DL.DEFINE

F5 to COMMIT (FINSHED DL.DEFINE)

32 | P a g e Hayyan| T24 R14

3. Create BCON

F5 to COMMIT BCON
33 | P a g e Hayyan| T24 R14

Verify BCON
(Can be re-verified multiple times)
Process-Verify:

ACTION> V<enter>
ID (JSBL …) <enter>
F5 to commit
F3 <enter> to check records
(if for any reasons routines missing then re-verify the BCON)
34 | P a g e Hayyan| T24 R14

CHECK-IN BCON
(Check-In process could not be reverted)
Process-Check In:

New connection Telnet IP

Enter Login: Pwd:
I <enter>
Server IP <enter>
t24dev <enter>
(Environment)
Enter BCON FILE (JSBL…)<enter>
Y<enter>
Pwd:<enter>
35 | P a g e Hayyan| T24 R14
36 | P a g e Hayyan| T24 R14

VOC
Shortcut login for ETS environment
JED VOC <VOC_NAME>

Now log in from black to ETS as per below instruction

37 | P a g e Hayyan| T24 R14

TEMPLATE

1. LIVE
2. HISTORY

STEPS:
1. Create Routine by copying of existing template and JED to update fields as per requirement
2. PGM.FILE
3. FILE.CONTROL
4. CREATE.FILES (classifications [FIN, for Financial|CUS, for Customer|INT, for International]
5. STANDARD SELECTION
6. FILE.LAYOUT from jShell (FILE DEFINITIONS)

System Files:
PGM.FILE DL Type: L-Live, H-History
FILE.CONTROL DL Classification: CUS,INT,FIN 8:Y 9:N
CREATE.FILES
STANDARD DL 28 Rebuild: Y
SELECTION
FILE.LAYOUT RTN cp to desired folder

LIVE
Could not be amended. Can be used for logging purpose.

Create Routine by copying of existing template and JED to update fields as per requirement
38 | P a g e Hayyan| T24 R14

PGM.FILE:

FILE.CONTROL:
39 | P a g e Hayyan| T24 R14

CREATE.FILES:

LIST NAME (BLANK)

40 | P a g e Hayyan| T24 R14
41 | P a g e Hayyan| T24 R14
42 | P a g e Hayyan| T24 R14

STANDARD SELECTION:
43 | P a g e Hayyan| T24 R14

FILE.LAYOUT:
44 | P a g e Hayyan| T24 R14

HISTORY
Can be amended.
Create Routine by copying of existing template and JED to update fields as per requirement

PGM.FILE
45 | P a g e Hayyan| T24 R14

FILE.CONTROL
Same as ‘LIVE’

CREATE.FILES
Repeat all steps as mentioned in ‘Live’.
On line 3.1 Suffix [press] < to add. To remove [press] -
3.1 SUFFIXES $NAU
3.2 SUFFIXES $HIS

STANDARD SELECTION
Same as in ‘LIVE’.

FILE.LAYOUT from jsh (FILE DEFINITIONS)

Same as in ‘LIVE’.
46 | P a g e Hayyan| T24 R14

TEMPLATE BROWSER INPUT

Using this method enables the data insertion in template from browser.
Id Start -> Starts with (FT162717WHQJ)

Pgm Autom Id -> Template name

M-> Specify to insert auto generated Id

RESULT
47 | P a g e Hayyan| T24 R14

VERSION
Version always belongs to some Application or Template

Ex: CUSTOMER,PK.CUST.INFO.TEST
48 | P a g e Hayyan| T24 R14

For multi-value fields we use ‘-1’

DL
VERSION>VERSION_NAME

To authorize the deal in Black we require Override field to be added in version as last field.
49 | P a g e Hayyan| T24 R14

EB.API
For all version routines we create EB.API instead of PGM.FILE