Build Control

Release: R19 AMR

May 2019

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means, for any purpose, without the express written permission
of TEMENOS HEADQUARTERS SA.

© 2019 Temenos Headquarters SA - all rights reserved.

 Build Control

Table of Contents
Overview 3
Save Process 4
Release Process 5
Configuring Build Control 6
Pre-requisites 7
Steps for Configuring Build Control 8
Build Control Table 9
Pre-requisites 10
Steps for Configuring Build Control 15
BUILD.CONTROL 21
Using Build Control 27
Save a package 28
Release a package 29
Build Control Tool 30
Release a BCON Unit in Classic 44

2
Build Control

Overview
BUILD.CONTROL is a deployment tool that could be used to install Non-core T24
applications and to move packages developed locally, on-site, from one envir-
onment to another.
The basic idea is the same as DL.DEFINE. Save the details in one environment and
Release them in another. Typically, in any implementation, the developments and
configurations will be done in the Build environment and then moved to master and
UAT environments and hence the name 'BUILD.CONTROL'
It provides the user with the facility/ability to"
l Save programs, data libraries, local ref table definitions, standard selection
descriptors and release them in another T24 environment.
l Automatic restoration of data libraries using DL.DEFINE.
l Automatic authorization of restored data records using OFS.
l Release I-Descriptors.
l Update LOCAL.REF.TABLE with the saved definitions.
l Compile/Catalog the programs released.
The resultant package will be saved in the path given in SAVE.PATH field, along with
an Index that will be used for Release operations.

3 Overview
 Build Control

Save Process

To SAVE a BCON Unit

Overview 4
Build Control

Release Process

To RELEASE a BCON Unit

5 Overview
 Build Control

Configuring Build Control

This topic specifies the folders, Company record, Auto Id records that are necessary
to run Build Control. It also shows how to configure the Build Control Parameter
record.

Configuring Build Control 6

Build Control

Pre-requisites
This topic specifies the pre-requisites and what needs to be generally considered to
run Build Control

7 Configuring Build Control

 Build Control

Steps for Configuring Build Control

This topic specifies the folders, Company record, Auto Id records that are necessary
to run Build Control. It also shows how to configure the Build Control Parameter
record.

Configuring Build Control 8

Build Control

Build Control Table

This table is the gateway of Build Control Tool. This table is used to save and
release the BUILD.CONTROL pack.

9 Configuring Build Control

 Build Control

Pre-requisites

System Requirements
The following are the pre-requisites for installing this package.
l T24 R13 or Above
l T24 R08 or Above
l TAFC R10 or Above

General Considerations
l When transferring object code via FTP the transport method must be set to
binary.
l When transferring data libraries via FTP the transport method must be set to
ASCII and the FTP client should be configured to preserve the case names of
the source files.

Contents of the Package

The pack contains the below source codes

Source Codes
RAD.BP>BCON.ANALYSE.OFS.MSG
RAD.BP>BCON.AUTHORISE.DL.RESTORE
RAD.BP>BCON.CHECK.FIELDS
RAD.BP>BCON.CHECK.ID
RAD.BP>BCON.CHECK.RECORD
RAD.BP>BCON.COMPLEMENT.TXTINP
RAD.BP>BCON.CREATE.VERSION
RAD.BP>BCON.CROSSVAL
RAD.BP>BCON.DICT.RELEASE
RAD.BP>BCON.FIELD.DEFINITIONS
RAD.BP>BCON.GENERATE.DOC
RAD.BP>BCON.MAINTAIN.AUDIT
RAD.BP>BCON.OPEN.FLAT.FILE
RAD.BP>BCON.PARAMETER.CHECK.FIELDS
RAD.BP>BCON.PARAMETER.CHECK.RECORD

Configuring Build Control 10

Build Control

RAD.BP>BCON.PARAMETER.CROSSVAL
RAD.BP>BCON.PARAMETER.FIELD.DEFINITIONS
RAD.BP>BCON.PGM.RELEASE
RAD.BP>BCON.PRODUCT.CHECK.FIELDS
RAD.BP>BCON.PRODUCT.CHECK.RECORD
RAD.BP>BCON.PRODUCT.CROSSVAL
RAD.BP>BCON.PRODUCT.FIELD.DEFINITIONS
RAD.BP>BCON.RELEASE.AUDIT.FIELD.DEFINITIONS
RAD.BP>BCON.SAVE.AUDIT.FIELD.DEFINITIONS
RAD.BP>BCON.USER.CONCAT.FIELD.DEFINITIONS
RAD.BP>BUILD.CONTROL
RAD.BP>BUILD.CONTROL.CLOSE
RAD.BP>BUILD.CONTROL.LOAD
RAD.BP>BUILD.CONTROL.OPEN
RAD.BP>BUILD.CONTROL.PARAMETER
RAD.BP>BUILD.CONTROL.PRODUCT
RAD.BP>BUILD.CONTROL.RELEASE.AUDIT
RAD.BP>BUILD.CONTROL.RELEASE
RAD.BP>BUILD.CONTROL.RUN
RAD.BP>BUILD.CONTROL.SAVE.AUDIT
RAD.BP>BUILD.CONTROL.SAVE
RAD.BP>BUILD.CONTROL.USER.CONCAT
RAD.BP>GET.LOC.REF.CACHE
RAD.BP>IN2BCON.FILEPATH
RAD.BP>IN2US.FILEPATH
RAD.BP>MULTI.GET.LOC.REF
RAD.BP>RAD.ETXT
RAD.BP>V.BCON.AUTO.UPDATE
RAD.BP>V.RAD.FIX.THE.BATCH.ID

Insert Files
RAD.BP>I_F.BUILD.CONTROL
RAD.BP>I_F.BUILD.CONTROL.PARAMETER

11 Configuring Build Control

 Build Control

RAD.BP>I_F.BUILD.CONTROL.PRODUCT
RAD.BP>I_F.BUILD.CONTROL.RELEASE.AUDIT
RAD.BP>I_F.BUILD.CONTROL.SAVE.AUDIT
RAD.BP>I_F.BUILD.CONTROL.USER.CONCAT
RAD.BP>I_LREF.COMMON
RAD.BP>I_RAPID.APP.DEV.COMMON
RAD.BP>I_RAPID.APP.DEV.EQUATE

Data Records
EB.API>V.BCON.AUTO.UPDATE
EB.API>V.RAD.FIX.THE.BATCH.ID
EB.ERROR>EB-BCON.BP.NOT.DEIN.BCON.PARAM
EB.ERROR>EB-BCON.CANNOT.VERIFY.NEW.RECORD
EB.ERROR>EB-BCON.CANT.REL.PGM.IN.BROWSER
EB.ERROR>EB-BCON.DATA.FILE.MISSING
EB.ERROR>EB-BCON.DEL.OTHER.MULT.VALUES.FIRST
EB.ERROR>EB-BCON.FILE.NOT.DEIN.BCON.PROD
EB.ERROR>EB-BCON.FILE.NOT.TYPE.UD.19
EB.ERROR>EB-BCON.FILE.SHOULD.BE.OTYPE
EB.ERROR>EB-BCON.FUNC.NOT.ALLWD.FOR.HELD.REC
EB.ERROR>EB-BCON.INP.FILE.NAME
EB.ERROR>EB-BCON.INP.SUFFIX
EB.ERROR>EB-BCON.INVALID.COMPANY
EB.ERROR>EB-BCON.MISSING.PROD
EB.ERROR>EB-BCON.OFS.SRC.TYPE.MUST.BE.GLOBUS
EB.ERROR>EB-BCON.PATH.NOT.PART.OENV
EB.ERROR>EB-BCON.PROGRAM.BP.INPUT.MISSING
EB.ERROR>EB-BCON.REC.MISS.FILE
EB.ERROR>EB-BCON.RELEASE.DATA.NOT.FOUND
EB.ERROR>EB-BCON.UNABLE.TO.GET.ENV
ENQUIRY>BUILD.CONTROL.DL.DEFINE
ENQUIRY>BUILD.CONTROL.PACKAGE
ENQUIRY>BUILD.CONTROL.RESULTS

Configuring Build Control 12

Build Control

FILE.CONTROL>BUILD.CONTROL
FILE.CONTROL>BUILD.CONTROL.PARAMETER
FILE.CONTROL>BUILD.CONTROL.PRODUCT
FILE.CONTROL>BUILD.CONTROL.RELEASE.AUDIT
FILE.CONTROL>BUILD.CONTROL.SAVE.AUDIT
OFS.SOURCE>BUILD.CONTROL
PGM.FILE>BUILD.CONTROL
PGM.FILE>BUILD.CONTROL.PARAMETER
PGM.FILE>BUILD.CONTROL.PRODUCT
PGM.FILE>BUILD.CONTROL.RELEASE.AUDIT
PGM.FILE>BUILD.CONTROL.SAVE.AUDIT
PGM.FILE>V.RAD.FIX.THE.BATCH.ID
STANDARD.SELECTION>BUILD.CONTROL
STANDARD.SELECTION>BUILD.CONTROL.PARAMETER
STANDARD.SELECTION>BUILD.CONTROL.PRODUCT
STANDARD.SELECTION>BUILD.CONTROL.RELEASE.AUDIT
STANDARD.SELECTION>BUILD.CONTROL.SAVE.AUDIT
VERSION>BATCH,RAD
VERSION>BUILD.CONTROL,CLOSE
VERSION>BUILD.CONTROL,DICT
VERSION>BUILD.CONTROL,DL.DEFINE
VERSION>BUILD.CONTROL,FLAT.FILES
VERSION>BUILD.CONTROL,LOCAL.REF
VERSION>BUILD.CONTROL,MAIN
VERSION>BUILD.CONTROL,NEW.SS
VERSION>BUILD.CONTROL,PROGRAMS
VERSION>BUILD.CONTROL,RELEASE
VERSION>BUILD.CONTROL,RELEASE.INSTR
VERSION>BUILD.CONTROL,RESULTS
VERSION>BUILD.CONTROL,SAVE
VERSION>BUILD.CONTROL.PARAMETER,AUTO.ID.DETAILS
VERSION>BUILD.CONTROL.PARAMETER,MAIN
VERSION>BUILD.CONTROL.PARAMETER,PACK.DETAILS

13 Configuring Build Control

 Build Control

VERSION>BUILD.CONTROL.PARAMETER,PATH.DETAILS
VERSION>BUILD.CONTROL.PARAMETER,RELEASE.DETAILS
VERSION>BUILD.CONTROL.PRODUCT,MAIN
VERSION>BUILD.CONTROL.PRODUCT,PACK.DETAILS
VERSION>DE.TRANSLATION,RAD
VERSION>TSA.SERVICE,RAD
VERSION>VERSION,RAD

Configuring Build Control 14

Build Control

Steps for Configuring Build Control

This topic specifies the folders, Company record, Auto Id records that are necessary
to run Build Control. It also shows how to configure the Build Control Parameter
record.

Pre-Installation steps
NA
l FTP the GR0800004lib.tar.Z to RUN directory in binary mode.
l Uncompress GR080000lib.tar.Z using the below command from the shell
prompt of the FTP path.
uncompress –c GR0800004lib.tar.Z | tar –xvf
l The above command will create a directory GR0800004lib under “bnk.run”
which contains all the object codes of BUILD.CONTROL.
l Add the GR0800004lib in the JBCOBJECTLIST of the .profile as like below.
JBCOBJECTLIST=$HOME/vdflib:$HOME/GR0800004lib
l Similarly uncompress the GR0800004Ins.tar.Z to RUN directory in binary
mode.
l Uncompress GR0800004Ins.tar.Z using the below command.
uncompress –c GR0800004Ins.tar.Z | tar –xvf
l The above operation will create a directory RAD.BP under “bnk.run”.
l Follow the Directory Creation step before installing the DL pack.

Installation steps for DL pack

NA
l If the package has been delivered as a DL Unit, then
l FTP the TMNS000-BUILD.CONTROL.tar.Z / tar.gz / zip to the directory
“../F.DL.DATA/DL.RESTORE” in binary mode.
l Uncompress TMNS000-BUILD.CONTROL.tar.Z/ tar.gz / zip using the below
command from the shell prompt of the FTP path.
l uncompress –c TMNS000-BUILD.CONTROL.tar.Z | tar -xvf- | (or) gunzip –c
TMNS000-BUILD.CONTROL.tar.gz | tar -xvf -
l Now login to the T24 session and open a new record SYSTEM in the table
DL.PARAMETER.
l Entry the DL pack name TMNS000-BUILD.CONTROL in the field
RESTORE.UNITS as shown below.

15 Configuring Build Control

 Build Control

l Commit and Verify (V) the same record.

l Then Verify (V) the record TMNS000-BUILD.CONTROL in DL.DEINE table as
shown below.

l The above operation will create the data records in IHLD status.
l Authorise the records manually which are in IHLD.

Creating the directories

Note: User is advised to ignore this step if the following directories

exists in your area.

For TAFC Environment

Create the below directories
l Ensure a directory F.BCON.DATA exists under “../bnk” path. If not available,
use the below command.
Jsh-> CREATE.FILE F.BCON.DATA TYPE=UD

Configuring Build Control 16

Build Control

l • Ensure two directories SAVE and RELEASE under “../bnk/F.BCON.DATA”

path. If not available create directories using below command.
Jsh-> CREATE.FILE SAVE TYPE=UD
Jsh-> CREATE.FILE RELEASE TYPE=UD
l Ensure two directories BCON.OFS.LOG and BCON.OFS.IN under “../bnk.in-
terface” path. If not available create directories using below command.
Jsh-> CREATE.FILE BCON.OFS.LOG TYPE=UD
Jsh-> CREATE.FILE BCON.OFS.IN TYPE=UD

For TAFJ Environment

Enter into DBTools & Create the below directories.
l Ensure a directory F.BCON.DATA exists under the current directory path. If
not available, create directory using the below command.
JQL-> CREATE-FILE F.BCON.DATA TYPE=UD
l Ensure two directories SAVE and RELEASE under F.BCON.DATA directory
path. If not available, create directory using the below command.
JQL-> CREATE-FILE F.BCON.DATA/SAVE TYPE=UD
JQL-> CREATE-FILE F.BCON.DATA/RELEASE TYPE=UD
l Ensure two directories BCON.OFS.LOG and BCON.OFS.IN under bnk.interface
directory. If not available, create directory using the below command.
JQL-> CREATE-FILE bnk.interface/BCON.OFS.LOG TYPE=UD
JQL-> CREATE-FILE bnk.interface/BCON.OFS.IN TYPE=UD

Setting up Company Record

In company record, add ‘BUILD.CONTROL’ as a new multi value into the field
PGM.AUTO.ID as shown below.

17 Configuring Build Control

 Build Control

Creating AUTO.ID.START record

Create the AUTO.ID.START record for BUILD.CONTROL as shown below.

Where, first line is ID.START is TODAY’s date in YYYYMMDD format.

Set the Build Control Parameter Record

Set the BUILD.CONTROL.PARAMETER table for all the applicable companies as
shown below. The ID to this table is the COMPANY ID.
Most of the fields are automatically defaulted once the ID for this record is
entered. The user can however amend these fields based on the local requirements.

Configuring Build Control 18

Build Control

Note For TAFJ users: Provide the valid BP name to the fields
PROGRAM.BP and RELEASE.BP. If RAD.BP is not exists since these fields
are not used by TAFJ. And also provide the above directory path which
are created for the TAFJ to the fields BCON.SAVE.PATH and
BCON.RELEASE.PATH.

19 Configuring Build Control

 Build Control

Note: While authorising the record, system will default the field auth pri-
ority. If any of the table is not used, user can remove it from the list.

Configuring Build Control 20

Build Control

BUILD.CONTROL
Note: In a TAFJ environment, the sources should not be packaged within
a BUILD.CONTROL application. The sources must be controlled only via
the JAR files and the IDE should be used for the sources. Therefore, the
functionality of the fields 7 to 12 are now outdated and will no longer be
supported for usage on TAFJ platform.

This table is the gateway of Build Control Tool. This table is used to save and
release the BUILD.CONTROL pack.
Field descriptions are as follows:

Fie- Field Name Ty- Description

ld pe
No
@I- @ID A*- ID of the record which needs to be saved or released.
D 35 (If it is release, ID should be exist in the release path
specified below)
1 XX.LL.DESCRIP- Description of the record
TION A*-
30
2 MNEMONIC A*- Mnemonic for the record key.
30
3 ACTION A*- It Could be one of SAVE, RELEASE, DL.RESTORE,
15 AUTH.DL.RESTORE or PGM.RELEASE
4 BCON.PRODU- A*- ID of the BUILD.CONTROL.PRODUCT can be given
CT 16 here. It is not a mandatory field.
5 SAVE.PATH A*- Path where the resultant BCON package will be saved.
50 Mandatory Input when ACTION is SAVE
6 RELEASE.PATH Path where the resultant BCON package will be
A*- Released. Mandatory Input when ACTION is not a
50 SAVE.
7 PROGRAM.BP A*- If programs are to be saved, this will be the BP from
35 which BUILD.CONTROL is expected to get the pro-
grams. This could either be the source codes or in
case of releasing to client, then the $ files can be selec-
ted and saved.

21 Configuring Build Control

 Build Control

8 XX.SELECT.CM- A*- Criteria for selecting the programs from

D 4 PROGRAM.BP. If it is a Saved list name, then this field
should be given as „SL-SL.NAME‟.
Ex: SL-TEST ( Here TEST is a Saved List)

9 MV.RESERVED- Reserved for Future.

.9 A*-
35
10 RELEASE.BP BP where the programs should be released in the
A*- release environment.
3
11 JBCDEV.LIB A*- Value of JBCDEV_LIB to be set when Compiling or cata-
35 loging the programs in the Release environment.
12 JBCDEV.BIN A*- Value of JBCDEV_BIN to be set when Compiling or
35 cataloging the programs in the Release environment.
13 OBJ.NAME A*- "If the lib itself is being created by BUILD.CONTROL,
5 then this is the name to beadded in the jLibDefinition
inside that new lib."
14 DEPENDENCY A*- ID to another BUILD.CONTROL unit on which the
35 installation of this BUILD.CONTROL unit is dependent
on. This is only for information and basic validation
purposes.
15 OUR.REFEREN- A*- Reference of Saved Path (Free text)
CE 35
16 THEIR.REFERE- A*- Reference of release path (Free text)
NCE 35
17 ISSUE.DESC A*- Description of Release notes if any.
35
18 OFS.SOURCE.I- A*- ID to OFS.SOURCE (SOURCE.TYPE must be GLOBUS),
D 15 to authorize the restored data records.
19 XX<DL.DEFINE A*- DL DEFINE ID to be saved.
15
20 XX.FROM.CO- A*- If the records in the DL.DEFINE are from a company
MPANY 15 specific file, then the company from which the
DL.DEFINE specified in Field 19 must be saved.
21 XX>TO.COMPA- A*- If the records in the DL.DEFINE are from a company
NY 15 specific file, then the company to which the DL.DEFINE
should be released.

Configuring Build Control 22

Build Control

22 XX<LOCAL.REF- A*- ID of Local Ref Table. Associated with the sub valued
.TABLE 15 field LOCAL.TABLE.
23 XX- A*- ID to LOCAL.TABLE. Associated with the sub valued
XX<LOCAL.TAB- 15 field TABLE.ASSOC. This field, along with TABLE ASSOC
LE records the Local Ref definition for the application spe-
cified in LOCAL.REF.TABLE field. When released, this
definition will be updated in the Local Ref table for
that application and authorized using OFS.
24 XX>XX>TABLE.- A*- Sub valued field associated with LOCAL.TABLE
ASSOC 15
25 XX<SS.APPL.NA- A*- ID to STANDARD.SELECTION. Associated with the
ME 15 fields till SS.RESVD.41. Used to store
I -descriptor details.

26 XX.USR.FIELD.- A*- User Field name, where the I- Descriptor needs to be

NAME 15 updated.
27 XX.USR.TYPE A*- Type of the Descriptor
15
28 XX.USR.FIELD.- A*- Definition of I- Descriptor.
NO 50 Ex:SUBR
('SS.US.GET.FIELD.DETAILS',@ID,'US.PH.TYPE','US.PH.N-
UM','HOME.PHONE')

29 USR.VAL.PROG A*- Validation of above I- Descriptor.

35
30 USR.CONVERSI- A*- Conversion if any.
ON 35
31 USR.DISPLAY.F- A*- Format of the above I- Descriptor Field. ( It will auto
MT 5 populate based on the field definition)
32 USR.ALT.INDEX A*- Field Alternate Index if any.
10
33 USR.IDX.FILE A*- Index Field if any.
10
34 USR.INDEX.NU- A*- For future Use.
LLS 10
35 USR.SINGLE.M- A*- Field is Single (S) or Multi (M).
ULT 2
36 USR.LANG.FIEL- A*- Language of the field.
D 2

23 Configuring Build Control

 Build Control

37 USR.CNV.TYPE A*- User Field conversion type.

10
38 USR.REL.FILE A*- Relational file if any.
10
3- SS.RESVD Reserved fields.
9-
42
43 BUILD.NEW.DI- A*- New DICT tables created.
CT 30
4- WS.FILE.NAME For Future Use.
4-
68
69 FILE.VOC.ID. A*- VOC Name, if any new VOC to be created.
30
70 FILES.TO.CREA- A*- File name to be created using the above VOC name.
TE 30
71 SHELL.CMD Any special Shell Command to be invoked at the end
of SAVE or RELEASE actions.
72 RELEASE.ORDE- A*- If there is any order in Release, we can give the order
R 50 by multi value this.
Ex: RELEASE.ORDER.1….CUSTOMER
RELEASE.ORDER.2….ACCOUNT

73 AUTH.SPL.INST- A*- Special instructions while authorizing – what should be

R 15 done if a Live record already exists. Allowed values –
OVERWRITE, LATEST or IGNORE
74 CREATE.LIB A*- If the lib specified in JBCDEV.LIB does not exist, then if
15 this field is set to Y, the lib will be automatically cre-
ated.
75 CREATE.BIN A*- If the bin specified in JBCDEV.BIN does not exist, then
15 if this field is set to Y, the bin will be automatically cre-
ated.
76 CREATE.REL.B- A*- If RELEASE.BP doesn‟t exist, then if this field is Y, it
P 15 will be created.

Configuring Build Control 24

Build Control

77 DL.SAVE.PATH A*- Path where DL.DEFINE will save Data Libraries. When
15 Saving, BUILD.CONTROL will call DL.DEFINE to save
each of the data libraries specified in the field
DL.DEFINE and then move those folders to the path
specified in SAVE.PATH. So, this path tells
BUILD.CONTROL, where to look for the Saved data lib-
raries.
78 DL.RESTORE.P- A*- Path where DL.DEFINE has to release Data Libraries.
ATH 15 When releasing, BUILD.CONTROL will call
DL.PARAMETER and subsequently DL.DEFINE to
release & restore the data libraries. So, this path tells
BUILD.CONTROL, where to copy the data libraries to
be released, before calling DL.PARAMETER
79 PROGRAM.OS A*- Operating System of the environment where this pack-
15 age was saved.
80 CLR.PROCESS.- A*- If set to Y and committed, the details in the fields
LOG 15 ACTIVITY, PROCESS.INFO will be cleared.
81 XX<ACTIVITY A*- Multi valued field associated with PROCESS.INFO.
15 Updated during verification process, with the progress
of action specified – either SAVE or RELEASE.
82 XX>PROCESS.I- A*- Progress information.
NFO 50
83 PROCESS.ERR- A*- Progress Error Information
OR 50
84 XX<SAVED.DAT- A*- Date and Time when the BCON saved.
E 50
85 XX. A*- T24 Release of Saved environment.
SAVED.VERSIO- 50
N
86 XX>SAVED.USE- A*- T24 User who saved the Pack.
R 50
87 XX< A*- Date and Time when the BCON released.
RELEASE.DATE 50
88 XX- A*- T24 Release of Released environment.
RELEASE.VERSI- 50
ON
89 XX> A*- T24 User who Released the Pack.
RELEASE.USER 50

25 Configuring Build Control

 Build Control

90 REL.STAGE A*- Release stages.

50 Ex: REL.FILES.TO.CREATE REL.DL.DEFINE
REL.PROGRAM

91 VIEW.REPORT A*- If Y is entered in this field, the user has the option to
25 enter a Flat file name and a record in that file, to be
opened as a Report.
9- RESERVED A*- Reserved Fields.
2- 25
10-
3

Configuring Build Control 26

Build Control

Using Build Control

Using Build Control shows you how to Save or Release a Build Control package

27 Using Build Control

 Build Control

Save a package

Using Build Control 28

Build Control

Release a package
It also shows you how to release a package in the classic mode

29 Using Build Control

 Build Control

Build Control Tool

The version “BUILD.CONTROL, MAIN” can be used for all the actions –
SAVE/RELEASE/DL.RESTORE/AUTH.DL.RESTORE/PGM.RELEASE. Using this version
we can save and release a BCON pack.

To save a BCON pack

The Build Control system creates a package that includes Programs/Object Codes,
DL.DEFINE units, Local Ref definitions, I-Desc Definitions, Flat File details, new
tables to be released etc. Each of these components is saved in a layered approach
and the priority of these layers is as given below.
Steps to save a new Build Control Unit have been explained below.

Main Screen
1. Enter BUILD.CONTROL, MAIN at the Command Prompt.
2. Enter the ID that you would like to give to your Build Control Package (Having
a date component will help).
3. This will open up a set of associated versions as shown below.

4. Enter the Action –

SAVE/RELEASE/HOLD/PGM.RELEASE/DL.RESTORE/DL.AUTH
5. Give a brief description on this package/in case of patch – what is the patch
for
6. Mnemonic – Mnemonic code of the pack

Using Build Control 30

Build Control

To save a Package
Use this screen to define the path where
l BUILD.CONTROL Units will be saved
l DL.DEFINE will save the data (as in ../F.DL.DATA)

What Happens
l While SAVE – A new folder with the name same as the Record ID, is created
under this path and the build control unit is saved in this path (similar in func-
tion to DL.DEFINE Unit)

Programs
Use this screen to define
l SAVE.BP where the programs/object codes ($ Files) reside,
l Selection criteria (Saved Lists should be prefixed with „SL-„ or this can be a
jQL
l statement)

31 Using Build Control

 Build Control

l RELEASE.BP where the programs/object codes ($ Files) need to be restored in

the destination environment.
l JBCDEV_LIB & JBCDEV_BIN to be set when Compiling/Cataloguing in the des-
tination environment. Leaving these fields blank will result in the default
JBCDEV_LIB and JBCDEV_BIN, as defined in REMOTE.CMD or .profile, being
used. If the above JBCDEV_LIB & JBCDEV_BIN are not defined in
$JBCOBJECTLIST, system will throw error.

What Happens
l While SAVE – A new folder with the name same as the PROGRAM.BP is cre-
ated under Build Control Unit Save path and the Saved list or the Select Com-
mand is used to select the PROGRAM.BP and the records are copied to the
Build Control path‟s BP folder.
l While RELEASE – The Release BP, if it doesn‟t already exist, is created in the
destination environment and the contents of the BP in Build Control unit are
copied to the Release BP. After setting JBCDEV_LIB and JBCDEV_BIN to
required values, the copied files – depending on whether they are source or
object codes, are either Compiled using EB.COMPILE or Catalogued using
CATALOG command.

DL DEFINE Units
Use this screen to
l Define the DL.DEFINE units that need to be saved as part of this package.
l Define the company from which the records defined in DL.DEFINE need to be
saved, in case there are FIN type file records.

Using Build Control 32

Build Control

What Happens
l While SAVE – The DL.DEFINE units are saved by invoking DL.DEFINE.RUN and
the resultant DL.DEFINE units are copied into Build Control save path.
l While RELEASE – The DL.DEFINE Units will be copied to
../F.DL.DATA/DL.RESTORE and DL.PARAMETER.RUN and DL.DEFINE.RUN will
be invoked to release and restore the DL DEFINE records.

Dict Items
Use this screen to
l Define any Dictionary items – I-Descriptor definitions that need to be saved
as part of the package. (Only enter the Standard Selection ID and the I-Desc
Name. The properties will automatically be defaulted from
STANDARD.SELECTION. Every time the Build Control is saved, these prop-
erties are refreshed automatically from STANDARD.SELECTION.)

What Happens
l SAVE – The properties – like TYPE, FIELD NO, VAL PROG and all other Stand-
ard Selection fields are saved in their corresponding fields in R.NEW of
BUILD.CONTROL.
l RELEASE – I-Descriptor name is checked in STANDARD.SELECTION and
updated with the details from R.NEW; the STANDARD.SELECTION record is
locked, updated and written to $NAU. OFS.GLOBUS.MANAGER is used to
authorise this STANDARD.SELECTION record and thereby rebuilding dic-
tionary.

33 Using Build Control

 Build Control

LOCAL.REF
Use this screen to define the
l Local ref definitions for all the T24 applications that need to be part of this
package. (This Local tables should be presented in LOCAL.TABLE)

What Happens
l While SAVE – Nothing. The definitions are validated.
l While RELEASE – based on the definitions and after ensuring that the Local
ref fields are available in LOCAL.TABLE, the corresponding LOCAL.REF.TABLE
record is updated with this definition. If the Local Ref is already attached to
the application, then the Association is overwritten with this definition.

New Tables to be released

Use this screen to define
l New tables that are being released as part of this package, for which Stand-
ard Selection record needs to be rebuilt.

What Happens
l While SAVE – Nothing.
l While RELEASE – A new record is locked and created in
STANDARD.SELECTION, $NAU file, on IHLD status. OFS GLOBUS MANAGER is
used to authorise that record.
l Instead of saving the STANDARD.SELECTION record for new tables as part of
the DL.DEFINE, specify the name of the table here. This proves to be helpful
when a new table is being released and an I-Descriptor also needs to be

Using Build Control 34

Build Control

attached to that STANDARD.SELECTION. Since the Authorisation of restored

DL.DEFINE records happen after the activity of restoring I-Desc definitions,
there will be a run time error. However, by specifying the table here, the
STANDARD.SELECTION is rebuilt even before I-Desc activity is done and hence
restoring I-Desc definitions will be successful.

Flat Files
Use this screen to define
l The path of flat files (Unix/NT directories – TYPE UD Files) that need to be cre-
ated when restoring this package.

What Happens
l While SAVE – Nothing
l While RELEASE – The path, folders are created and a VOC pointer is created
with ID as the last part as the ID
l In the above case, a folder in the path ../bnk.interface/git/GIT.INWARD will
be created and a VOC pointer will be created with ID as GIT.INWARD.

Commit and Verify the BCON pack

l Once we done the above Build control definitions Commit the record and
verify the same.
l After the Verify command, we can see the Data record components and
Source/Object codes which are packed up in this BCON unit. This consolidated
pack will be stored under the path ../F.BCON.DATA/SAVE with the same
BCON name saved.
l Use the below enquiry and Associated version to see the data components.

View Process Info

Use this screen to see
l Once the Save operation is complete, the system will automatically display
the results in the form of a standard T24 Enquiry, as shown below.

35 Using Build Control

 Build Control

Package Checklist
Use the enquiry BUILD.CONTROL.PACKAGE to review the contents of the package.
l Shown below is a screen shot of this enquiry, running on a package called
TMNS000- GPAC.GITI.R12.

Enquiry shows the list of Data records which are saved in the pack.

Using Build Control 36

Build Control

Build Control Saved Unit

When you save the Build Control unit, whole package will be created under the
path ../F.BCON.DATA/SAVE as shown below.

37 Using Build Control

 Build Control

Contents of a Build Control Unit

Shown below is the Content of the Build Control Unit TMNS000-GPAC.GITI.R12
l GIT.BP – Program BP
l SAVEDLISTS – If a Saved list had been used instead of a Select Command, then
that Saved list will also be saved, under a folder SAVEDLISTS
l TMNS000-GPAC.GITI.R12.2 and TMNS000-GPAC.GITI.R12.1 – The DL DEFINE
pack.
l BCON_TMNS000-GPAC.GITI.R12 – Index (Copy of R.NEW to be used during
RELEASE Operations)

l GIT.BP - This is the BP defined as PROGRAM.BP, from which programs were

selected.

l SAVEDLISTS - If a Saved list had been mentioned in SELECT.CMD field, then

that Saved list will be copied under this folder. During RELEASE Operation,
this will be copied over to &SAVEDLISTS& in the destination environment.

Using Build Control 38

Build Control

l TMNS000-GPAC.GITI.R12.2 and TMNS000-GPAC.GITI.R12.1 -This is the

DL.DEFINE to be saved part of the package. During RELEASE Operation, this
will be copied over to DL.DEFINE restore path (typically
../F.DL.DATA/DL.RESTORE) and restored/released using DL.PARAMETER.RUN
and DL.DEFINE.RUN.

To Release a Build control Package

We should use the same version BUILD.CONTROL, MAIN to release a
BUILD.CONNTROL unit.

Main Screen
1. To release the pack, copy the BUILD.CONTROL unit to F.BCON.DATA/RELEASE
directory as shown below. For Example: TMNS000-GPAC.SADB.
If the BUILD.CONTROL unit contains the Object code, we should transfer the
BCON unit in Binary mode (UNIX server). If it is a NT server, the mode of
transfer does not matter.

2. Launch the main version BUILD.CONTROL, MAIN in browser.

3. Open a new record with ID as TMNS000-GPAC.SADB (should be same as the
BCON Unit name)
4. In the ACTION field enter RELEASE.

39 Using Build Control

 Build Control

To Release a package
Use this screen to define
1. Enter the BCON release path in the field „Release Package is Available
under‟. This release path should be same, where the BUILD.CONTROL Unit
has been copied over.

2. The system will default the path where the DL Units need to be copied (as in
../F.DL.DATA/DL.RESTORE or../DL.RESTORE) which may not be the same in
both Save and Release environments. Manually change the value if the sys-
tem raises an error.
3. At field input level, if the path is correct, then the system will load the remain-
ing fields based on the index file BCON_TMNS000-GPAC.SADB stored under
the release path.
4. Once validated the record, system will automatically populate the remaining
fields based on the Index file BCON_TMNS000-GPAC.SADB as shown below.

Using Build Control 40

Build Control

41 Using Build Control

 Build Control

5. In the Release tab, in the field „OFS Source to be used for Authorising‟ enter
the ID of the OFS.SOURCE to be used for authorising the records. At this field
input, the system will default Authorisation Priority. The user can amend this
priority as applicable.

6. Now commit the record.

7. Open the same record and Verify it (V function).

8. The package will be installed.

Note: It is strongly recommended to use the classic screen to release

the BCON unit which holds the Object codes and Data records. Follow
the below steps to release the unit in classic mode.

PGM.RELEASE
l With this action, BUILD.CONTROL releases all programs that are part of the
DL Units specified in the multi-valued field DL.DEFINE.
l Saving and Releasing Programs, works exactly the same way as RELEASE. To
release a program, the ACTION could be set to PGM.RELEASE or RELEASE.
l If the field RELEASE.BP is NULL, then programs will not be Com-
piled/Catalogued.

Note: If the user chooses to release using PGM.RELEASE, then, the

Action must first be set to DL.RESTORE and Verified first (so that the pro-
grams are restored). Subsequently, the Action can be set to
PGM.RELEASE and Verified.

Using Build Control 42

Build Control

DL.RESTORE
l With this action, BUILD.CONTROL restores all the data records part of the DL
Units specified in the multi-valued field DL.DEFINE.
l Since the sample BUILD.CONTROL unit TMNS000-BCON.REL.SAMPLE also con-
tains data records, it can be used for testing DL.RESTORE alone.
l When the ACTION is set to RELEASE, BUILD.CONTROL automatically copies
the DL Units from F.BCON.DATA/RELEASE to the DL Restore path (as in,
F.DL.DATA/DL.RESTORE), and then uses DL.PARAMETER & DL.DEFINE to
release & restore those records.
l However, when the Action is set to DL.RESTORE, the system assumes that the
required DL Units are already present in the DL Restore path (as in
F.DL.DATA/DL.RESTORE or ../DL.RESTORE). The user has to move the DL Units
manually under the DL Restore path before setting the Action to DL.RESTORE

AUTH.DL.RESTORE
l With this action, BUILD.CONTROL authorises all the data records part of DL
Units specified in the multi-valued field DL.DEFINE
l Since the sample BUILD.CONTROL unit TMNS000-BCON.REL.SAMPLE also con-
tains data records, it can be used for testing AUTH.DL.RESTORE alone.
l This will enable Authorisation of Restored records. However, when Action is
set to AUTH.DL.RESTORE, the system assumes that the records have already
been restored and will only attempt to authorise them.

Note: If the user chooses to authorise using AUTH.DL.RESTORE, then,

the Action must first be set to DL.RESTORE and Verified (so that the pro-
grams/records are restored). Subsequently, the Action can be set to
AUTH.DL.RESTORE and Verified.

43 Using Build Control

 Build Control

Release a BCON Unit in Classic

l To release the pack, copy the BUILD.CONTROL unit to F.BCON.DATA/RELEASE
directory as shown below. For Example: TMNS000-GPAC.SADB.
l If the BUILD.CONTROL unit contains the Object code, we should transfer the
BCON unit in Binary mode (UNIX server). If it a NT server, we do not care
about the mode of transfer.

l Login to the T24 user in classic mode

l Go to the application BUILD.CONTROL in INPUT mode. Now the system will
show the below screen.

l Give the Description, Mnemonic, Action and Release path as shown below.

Using Build Control 44

Build Control

l Now the system will ask to reload the package. Press „Y‟ and enter. Now the
system should be reloaded the BUILD.CONTROL unit based on the index file.

l Enter the OFS.SOURCE.ID as „BUILD.CONTROL‟ and enter.

45 Using Build Control

 Build Control

l Remaining fields will be auto populated based on the index file.

Using Build Control 46

Build Control

47 Using Build Control

 Build Control

l Now commit the deal and Verify (V) the same.

l Now the system will restore the records and object codes which are packed in
the BCON unit.
l Once the Restoration processed successfully, system will ask for a sign out.
Now sign out the JBase session and re login to the new session.

Using Build Control 48

Build Control

l Verify the same BCON unit record in the new session as shown below.

l Now the Data records will be authorised automatically using the Build control
tool.
l Then check the session, whether all the data records are authorised suc-
cessfully.

49 Using Build Control

 Build Control

Using Build Control 50

Build Control

l If any of the record is not authorised successfully, then authorise it manually.

Note: If any BATCH record needs to be RELEASED for multiple com-

panies (Ex: MF1, EU1 etc), we should “SAVE” the BATCH.NEW.COMPANY
record along with the BATCH Record from the Source environment.

Screenshot of BATCH.NEW.COMPANY record where the BCON saved

51 Using Build Control